I planned to upgrade my GitLab server in a docker setup from 16.8-ee to 17.2-ee and I have found no relative upgrade paths for this, so I assume it is okay to upgrade to 17.2 directly. Using the gitlab’s official documentation on upgrading GitLab via docker.
Upon starting the new container, I noticed that I cannot login anymore, it shows the invalid credentials error. Upon checking gitlab-rails console, I have found out that the users were erased and the record only shows 1 user.
User.all.each { |user| puts "#{user.username}: #{user.state}"}
root: active
=> [#<User id:1 @root>]
Any ideas how to fix it?
I only reattached previously used volumes and did not create a new volume for the new container. I am also suspecting that it is not really the upgrade that disrupts the database record, it might be due to a step in upgrading that requires to remove the container before proceeding.
user26585326 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2