I am unable to login to src.fedoraproject.org. When I try, I get redirected back without being logged in. Doing the same with pagure.io works fine.
It'd be nice to have this fixed reasonably soon, as I can't do anything while logins are failing.
Can you try again now? I restarted some things...
For completeness:
Still doesn't work.
For completeness: You are using login not email address?
Yes.
You are appending otp to password?
I have no OTP configured.
Can you try removing ~/.fedora/openidbaseclient-sessions.cache and see if that helps any?
I do not have that file. This affects me on all my computers and my phone. I first experienced this on my Mac.
The logs show auth successfull... I'm at a loss what could be going on here. ;(
@abompard or @pingou any ideas?
Figured out the problem. It's because src.fedoraproject.org doesn't have https://pagure.io/pagure/c/512f23f5cd1f965276969747792edeb1215cba68
I've submitted an update to fix this: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-2581a5528a
So did you change something in your ssh keys recently?
Yeah, I added a second SSH key. I just deleted it and I'm able to login again.
@ngompa Is the new version deployed?
Metadata Update from @zlopez: - Issue priority set to: Waiting on Reporter (was: Needs Review) - Issue tagged with: dev, low-gain, low-trouble
@zlopez I dunno, I don't have the capability to do that. All I can do is package things.
@pingou Do you know how the src.fp.o is deployed?
how is via ansible just like all our apps :) If it was updated, no idea. Considering that a number of us having been AFK over the last few weeks, I am not sure if it has been.
Last update to system was on Dec 24
# dnf history info 127 Transaction ID : 127 Begin time : Fri 24 Dec 2021 07:00:10 GMT Begin rpmdb : 749:d542485928b3f93686af6b6a1af0117a9c59c310 End time : Fri 24 Dec 2021 07:00:59 GMT (49 seconds) End rpmdb : 749:2ad236c59b2d32deee65f90de34454c64d1d381c User : System <unset> Return-Code : Success Releasever : 8 Command Line : Comment : Packages Altered: Install kernel-core-4.18.0-348.7.1.el8_5.x86_64 @rhel8-BaseOS Install kernel-4.18.0-348.7.1.el8_5.x86_64 @rhel8-BaseOS Install kernel-modules-4.18.0-348.7.1.el8_5.x86_64 @rhel8-BaseOS Upgrade openssl-1:1.1.1k-5.el8_5.x86_64 @rhel8-BaseOS Upgraded openssl-1:1.1.1k-4.el8.x86_64 @@System Upgrade kernel-tools-libs-4.18.0-348.7.1.el8_5.x86_64 @rhel8-BaseOS Upgraded kernel-tools-libs-4.18.0-348.2.1.el8_5.x86_64 @@System Upgrade kernel-tools-4.18.0-348.7.1.el8_5.x86_64 @rhel8-BaseOS Upgraded kernel-tools-4.18.0-348.2.1.el8_5.x86_64 @@System Upgrade python3-perf-4.18.0-348.7.1.el8_5.x86_64 @rhel8-BaseOS Upgraded python3-perf-4.18.0-348.2.1.el8_5.x86_64 @@System Upgrade openssl-libs-1:1.1.1k-5.el8_5.x86_64 @rhel8-BaseOS Upgraded openssl-libs-1:1.1.1k-4.el8.x86_64 @@System Upgrade qemu-guest-agent-15:4.2.0-59.module+el8.5.0+13495+8166cdf8.1.x86_64 @rhel8-AppStream Upgraded qemu-guest-agent-15:4.2.0-59.module+el8.5.0+12817+cb650d43.x86_64 @@System Reason Change NetworkManager-1:1.32.10-4.el8.x86_64 @rhel8-BaseOS Removed kernel-4.18.0-305.25.1.el8_4.x86_64 @@System Removed kernel-core-4.18.0-305.25.1.el8_4.x86_64 @@System Removed kernel-modules-4.18.0-305.25.1.el8_4.x86_64 @@System
Current version of pagure on the system is pagure-5.13.3-1.el8.infra.noarch
pagure-5.13.3-1.el8.infra.noarch
I don't see anything obvious in the httpd logs on pkgs01 saying ngompa is denied access. I think we are going to need to pick out the workflow of actions and websites to figure out which system may be 'stuck'.
I've applied the upgrade to 5.13.3-2.el8
Thanks!
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.