I 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 look

I 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.