2.9 to 3.0 Upgrade Diagnostic Command Issue
Created by: ZKjellberg
Working to upgrade a GitLab instance by following the Upgrade Guide for 2.9-3.0
For the following lines:
# Check APP Status
bundle exec rake gitlab:app:status RAILS_ENV=production
I encounter an issue where it prompts me to enter git@localhost's password. (Which does not exist.)
I discovered this because the original GitLab installation instructions uses the command below to run as the user gitlab instead of the current user.
Section 6. GitLab - Check application status
sudo -u gitlab bundle exec rake gitlab:app:status RAILS_ENV=production
I suggest updating the From-2.9-to-3.0 guide to use the historical command to prevent this issue.