@germano reported on fedora-infra matrix that he is not able to log in to pagure.io nor copr.fedoranfracloud.org.
I was able to test that and confirm that this really doesn't work.
For COPR it returns ERR_TOO_MANY_REDIRECTS, for pagure.io and src.fp.o Strange state: failure.
ERR_TOO_MANY_REDIRECTS
Strange state: failure
ASAP
I did some investigation and this is what I found.
There is no error in logs on ipsilon01, ipa01or pagure02. On ipsilon01 the logs are saying that the login was successful.
ipsilon01
ipa01
pagure02
I found out that there was httpd update on ipsilon01 today at 700 UTC. I tried to revert that with dnf history rollback but it couldn't find the previous versions. So I did dnf downgrade httpd, but it ended up with broken httpd which threw error on start.
dnf history rollback
dnf downgrade httpd
httpd
I was able to solve the issue by downgrading httpd and mod_http2 on ipsilon01.
mod_http2
I filled a bug for httpd in bugzilla for the issue.
We should probably disable automatic update of httpd till the issue is solved.
Metadata Update from @zlopez: - Issue untagged with: Needs investigation - Issue tagged with: low-trouble
Metadata Update from @zlopez: - Issue assigned to zlopez
Thank you very much @zlopez for investigating the issue.
I still cannot log in from Copr and Pagure. Is it possible it automatically upgraded again?
Yes, it did. It's a security update, so dnf-automatic re-applied it. ;(
I have now updated it to the 2.4.62 version from updates-testing.
Please re-test and let us know if you still see the problem.
Thank you @kevin
Strange but still doesn't work
ok, let me go back to the previous one then and force it to not update.
ok, try now?
it works
I just logged in on Copr and here, Pagure, without any problems. Whatever is in place now seems to be working.
I can confirm that Copr works now. Thank you very much @kevin. It would probably be a good idea to dnf versionlock the downgraded packages until we have a fix for the new versions.
dnf versionlock
yeah, I added exclude=httpd* on them for now.
Hopefully we can figure out the problem soon...
Is fixed to me
Thanks
The temporary solution works for me. I had same problem and now its "fixed". Thanks
I updated the bugzilla issue with info that it doesn't work with 2.4.62 as well.
Can somebody please apply the same fix for the STG ipsilon instance too?
Done.
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee
Metadata Update from @zlopez: - Issue priority set to: Waiting on External (was: Waiting on Assignee)
Closing this as the actual problem is fixed and the httpd issue is tracked in https://pagure.io/fedora-infrastructure/issue/12092
Metadata Update from @zlopez: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.