`gitlab-rake gitlab:backup:create` command does not upload to specified S3 (non AWS endpoint)
Summary
We like to backup our instance to a S3 bucket with the following command:
sudo gitlab-rake gitlab:backup:create SKIP=artifacts,lfs,registry,pages
The backup is created and on the console the following is reported:
Uploading backup archive to remote storage backup-gitlab ... done
The backup files is not copied to the S3 bucket, but stays in /var/opt/gitlab/backups/
The configuration of the S3 is correct as the backup is copied to the specified S3 bucket for the backup initiated by updates through apt-get update
.
Steps to reproduce
Run sudo gitlab-rake gitlab:backup:create SKIP=artifacts,lfs,registry,pages
on a OmniBus managed GitLab EE.
What is the current bug behavior?
The backup files is not copied to the S3 bucket, but stays locally in /var/opt/gitlab/backups/
What is the expected correct behavior?
The backup files is copied to the S3 bucket, and there should be no copy locally in /var/opt/gitlab/backups/
Relevant logs and/or screenshots
done
Dumping uploads ...
done
Dumping builds ...
done
Dumping artifacts ...
[SKIPPED]
Dumping pages ...
[SKIPPED]
Dumping lfs objects ...
[SKIPPED]
Dumping container registry images ...
[SKIPPED]
Creating backup archive: 1525965596_2018_05_10_10.7.3-ee_gitlab_backup.tar ... done
Uploading backup archive to remote storage backup-gitlab ... done
Deleting tmp directories ... done
done
done
done
done
Deleting old backups ... skipping
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Ubuntu 16.04 Proxy: no Current User: git Using RVM: no Ruby Version: 2.3.6p384 Gem Version: 2.6.13 Bundler Version:1.13.7 Rake Version: 12.3.0 Redis Version: 3.2.11 Git Version: 2.14.3 Sidekiq Version:5.0.5 Go Version: unknownGitLab information Version: 10.7.3-ee Revision: 584a495 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql DB Version: 9.6.8 URL: https://gitlab.example.com HTTP Clone URL: https://gitlab.example.com/some-group/some-project.git SSH Clone URL: git@gitlab.example.com:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: no Using Omniauth: yes Omniauth Providers: github
GitLab Shell Version: 7.1.2 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
all good ...
~bug