Date: Mon, 27 Jul 2020 18:34:29 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 248302] Upgrade to gitlab 13.2.1 breaks CI job display Message-ID: <bug-248302-7788-LJpdO1Yply@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-248302-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-248302-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D248302 --- Comment #1 from gwright@antiope.com --- An upstream bug fix in gitlab-ce 13.2.1 requires users to revalidate their email addresses. What is supposed to happen is that gitlab automatically generates an email to each user, and by responding, the user's account is reenabled. If a user attempts to log in before reenabling his/her account,= a 422 error is generated. The issue is described here: https://docs.gitlab.com/ee/user/upgrade_email_bypass.html When I upgraded from 13.1.4 to 13.2.1, my user account was locked out (generating a 422 error) but it was still possible to log into the administrator account. No email message was sent asking me to reconfirm my account, even though I used the administrator's console to run all the dela= yed tasks. In my case, the workaround that succeeded was to log into the rails console= and force reconfirmation of all users. This is what I did: {{{ root@gitlab:/usr/local/www/gitlab-ce # su -l git -c "cd /usr/local/www/gitlab-ce && rails console -e production" ---------------------------------------------------------------------------= ----- GitLab: 13.2.1 (Unknown) FOSS GitLab Shell: 13.3.0 PostgreSQL: 11.8 ---------------------------------------------------------------------------= ----- Loading production environment (Rails 6.0.3.2) irb(main):001:0> User.all.each {|u| u.confirmed_at =3D Time.now; u.save} =3D> [#<User id:1 @root>, #<User id:6 @alert-bot>, #<User id:5 @ghost>, #<U= ser id:4 @gwright>] irb(main):002:0> exit }}} The command that I entered at the prompt was `User.all.each {|u| u.confirme= d_at =3D Time.now; u.save}`. Once that ran and the prompt returned, I was able = to type `exit`. I could then log on to my non-adminstrator account. The documentation for upgrading should probably include the above link to t= he gitlab documentation, which gives instructions for what to do if you are lo= cked ou --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-248302-7788-LJpdO1Yply>