4 ms·
Just to be clear. All we need is the output from the console not the actual backup. What I see from the result your getting is the actual backup command failin
by balameb 11y ago
Just to be clear. All we need is the output from the console not the actual backup.
What I see from the result your getting is the actual backup command failing. From my experience this might be do to how its executed through the upgrade process and we can have a closer look at what failed when running the create command.
- cheald 11y agoI sent an email, but it looks like if RVM is installed, gitlab-rake may be depending on bundler being installed in the currently-active RVM environment. It looks like RVM may be conflicting with gitlab's bundled Ruby due to RVM setting GEM_PATH and prevents bundler from being found, which causes the upgrade process to fail. Explicitly setting GEM_PATH for the gitlab_rake invocation may fix it. If bundler is available in the active RVM environment, it works fine.
- balameb 11y agoCorrect the GEM_PATH is conflicting. Thank you for the information provided and your help through our support channel. Here is the public issue for future reference: https://gitlab.com/gitlab-org/gitlab-ce/issues/13689 https://gitlab.com/gitlab-org/gitlab-ce/issues/13689.