Cannot change backups permissions

I have set gitlab's backup location to a mounted NFS share directory.

the directory is mounted: fstab has 10.10.1.100/mnt/backups /mnt/nfs/gitlabbackup nfs defaults 0 0 The directory has 775 permission and I chown'd it to git:git

I set gitlab.rb to place the backups at the mount location with the permissions 0777 then run 'sudo gitlab-ctl reconfigure' which fails with the following

  * directory[/mnt/nfs/gitlabbackup/archives] action create

    ================================================================================
    Error executing action `create` on resource 'directory[/mnt/nfs/gitlabbackup/archives]'
    ================================================================================

    Errno::EPERM
    ------------
    Operation not permitted @ chmod_internal - /mnt/nfs/gitlabbackup/archives

    Resource Declaration:
    ---------------------
    # In /opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/recipes/gitlab-rails.rb

     41:   directory dir_name do
     42:     owner node['gitlab']['user']['username']
     43:     mode '0700'
     44:     recursive true
     45:   end
     46: end

    Compiled Resource:
    ------------------
    # Declared in /opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/recipes/gitlab-rails.rb:41:in `block in from_file'

    directory("/mnt/nfs/gitlabbackup/archives") do
      action :create
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      path "/mnt/nfs/gitlabbackup/archives"
      recursive true
      declared_type :directory
      cookbook_name "gitlab"
      recipe_name "gitlab-rails"
      owner "git"
      mode "0700"
    end


Running handlers:
[2015-09-17T14:40:17+01:00] ERROR: Running exception handlers
Running handlers complete
[2015-09-17T14:40:17+01:00] ERROR: Exception handlers complete
Chef Client failed. 1 resources updated in 7.054030176 seconds
[2015-09-17T14:40:17+01:00] FATAL: Stacktrace dumped to /opt/gitlab/embedded/cookbooks/cache/chef-stacktrace.out
[2015-09-17T14:40:17+01:00] ERROR: Found 1 errors, they are stored in the backtrace
[2015-09-17T14:40:18+01:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

It seems the reconfigure script is still trying to chmod the directory permissions to 0700 despite my changing the gitlab.rb file to specify 0777 (I tried other permissions also, reconfigure always seems to use 0700)

I'm having the same issue

I have similar issue :

================================================================================
Error executing action `create` on resource 'directory[/mnt/backups]'
================================================================================

Errno::EACCES
-------------
Permission denied @ chmod_internal - /mnt/backups

Resource Declaration:
---------------------
# In /opt/gitlab/embedded/cookbooks/cache/cookbooks/gitlab/recipes/gitlab-rails.rb

 96: directory node['gitlab']['gitlab-rails']['backup_path'] do
 97:   owner gitlab_user
 98:   mode '0700'
 99:   recursive true
100:   only_if { node['gitlab']['gitlab-rails']['manage_backup_path'] }
101: end
102: 

Added backup-restore label

My whole git-data directory was on an NFS mount, and after an update sudo gitlab-ctl reconfigure gave me the same error. I had to move everything to an internal image in order to get GitLab running again. And I don't have enough internal space for git-lfs.

I would say this is a serious regression...

I am having the same issue with trying to put backups on an NFS volume.

It seems inefficient to force the Gitlab server to have twice as much storage as it needs, so you can create the backup copy on local storage, then copy it to NFS, instead of just directly creating it on NFS.

This issue seems to have existed for a long time with no thoughts from Gitlab?

moved to gitlab#3823

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue

mentioned in merge request !14785