From owner-freebsd-ports-bugs@freebsd.org Mon Jul 27 18:34:29 2020 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C433836AC44 for ; Mon, 27 Jul 2020 18:34:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4BFpPK4rxPz49y0 for ; Mon, 27 Jul 2020 18:34:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id A4EEF36AC42; Mon, 27 Jul 2020 18:34:29 +0000 (UTC) Delivered-To: ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A39F636A9B6 for ; Mon, 27 Jul 2020 18:34:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BFpPK3vyrz49dg for ; Mon, 27 Jul 2020 18:34:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 69BAB222D3 for ; Mon, 27 Jul 2020 18:34:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 06RIYTOT097310 for ; Mon, 27 Jul 2020 18:34:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 06RIYTVP097309 for ports-bugs@FreeBSD.org; Mon, 27 Jul 2020 18:34:29 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 248302] Upgrade to gitlab 13.2.1 breaks CI job display Date: Mon, 27 Jul 2020 18:34:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: gwright@antiope.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jul 2020 18:34:29 -0000 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> [#, #, #, #] 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.=