On Tue, Dec 03, 2024 at 11:11:42AM +0000, Christopher Klooz wrote: > Kevin and I have already worked on this in a pagure ticket (I experienced it as well frequently in the past): https://pagure.io/fedora-infrastructure/issue/11962 > > I already posted this mailing list thread in the ticket to make the infra team aware that the issue is back. You might talk to Kevin in the ticket (or here if you cannot login at all) as he already has some data in the ticket that gave hints about the issue, but back then, it disappeared, so we closed the ticket as I could no longer provide further data. Maybe you can now provide what is necessary to finally solve that issue. Good luck! > > By the way, when I had this issue, it was useful to just re-try. After a few times, it usually worked. This doesn't seem to be the random sporadic issue we have had trouble pinning down. Instead, this is something specifically with saml2 auth to bugzilla via the fedora provider. ;( ie, I can duplicate it 100% of the time here. I'm looking into it... we did ugrade our identity provider instances yesterday, so it's likely somehow related to that. https://pagure.io/fedora-infrastructure/issue/12321 is tracking this. kevin
Attachment:
signature.asc
Description: PGP signature
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
