FAS login not possible

[Marius Schwarz]

Hi,

ATM FAS Login is not possible.

The ironic part is: you need to login to take part in the infrastructure 
ticket about not able to login ;)

https://pagure.io/fedora-infrastructure/issue/11949

You get this message:

"400 - Bad Request - Invalid transaction id"

when you try to login via the website or api.

Direct messages to  "[e-mail]" are also 
not possible, you need to be on the list to do that.

best regards,
Marius Schwarz

[Christopher Klooz]

Unfortunately, such errors are not a seldom phenomenon (at least in my case). You can try again, it will work at some time usually. I have seen bad request and time outs so far. Usually trying it again once or twice should be enough.

In any case, do not return with the button but refresh the login page before the next attempt. Just to ensure this is not the issue.

We had topics in discourse and such about the issue before, but I expect it is indirectly a matter of money for infra.

If you still experience the issue, you should contact [e-mail] -> they can help you in such cases, and you do not need to login 🙂 You can expect a quick and helpful response there.

Best,
Chris

On 27/05/2024 10.45, Marius Schwarz wrote:
> Hi,
>
> ATM FAS Login is not possible.
>
> The ironic part is: you need to login to take part in the infrastructure ticket about not able to login ;)
>
> https://pagure.io/fedora-infrastructure/issue/11949
>
> You get this message:
>
> "400 - Bad Request - Invalid transaction id"
>
> when you try to login via the website or api.
>
> Direct messages to  "[e-mail]" are also not possible, you need to be on the list to do that.
>
> best regards,
> Marius Schwarz
> -- 
> _______________________________________________
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Aditi Mishra]

Hey Marius, Once try by removing cache also. May be it'll work.

On 27/05/24 14:41, Christopher Klooz wrote:
> Unfortunately, such errors are not a seldom phenomenon (at least in my 
> case). You can try again, it will work at some time usually. I have 
> seen bad request and time outs so far. Usually trying it again once or 
> twice should be enough.
>
> In any case, do not return with the button but refresh the login page 
> before the next attempt. Just to ensure this is not the issue.
>
> We had topics in discourse and such about the issue before, but I 
> expect it is indirectly a matter of money for infra.
>
> If you still experience the issue, you should contact 
> [e-mail] -> they can help you in such cases, and you do 
> not need to login 🙂 You can expect a quick and helpful response there.
>
> Best,
> Chris
>
> On 27/05/2024 10.45, Marius Schwarz wrote:
> > Hi,
> >
> > ATM FAS Login is not possible.
> >
> > The ironic part is: you need to login to take part in the 
> > infrastructure ticket about not able to login ;)
> >
> > https://pagure.io/fedora-infrastructure/issue/11949
> >
> > You get this message:
> >
> > "400 - Bad Request - Invalid transaction id"
> >
> > when you try to login via the website or api.
> >
> > Direct messages to  "[e-mail]" are also 
> > not possible, you need to be on the list to do that.
> >
> > best regards,
> > Marius Schwarz
> > -- 
> > _______________________________________________
> > devel mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: 
> > https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue

[Kevin Fenzi]

On Mon, May 27, 2024 at 10:45:34AM GMT, Marius Schwarz wrote:
> Hi,
>
> ATM FAS Login is not possible.

For you, to what? anything?
> The ironic part is: you need to login to take part in the infrastructure
> ticket about not able to login ;)
>
> https://pagure.io/fedora-infrastructure/issue/11949
>
> You get this message:
>
> "400 - Bad Request - Invalid transaction id"
>
> when you try to login via the website or api.

So, that ticket is about the kernel test app:

https://kerneltest.fedoraproject.org/

It was changed a while back to use a new auth mode and the script for
submitting authenticated results is not currently working. This is
tracked in:

https://pagure.io/kernel-tests/issue/50

The workarounds include just anonymous submitting, or logging into the
web app with a browser and uploading the tests. 
Hopefully someone will look into this after the long weekend/holiday.

So, is it just that you cannot submit kernel test results?
Or can you not login to anything else?
> Direct messages to  "[e-mail]" are also not
> possible, you need to be on the list to do that.

Yes.

If you cannot auth to update/file a ticket:

https://docs.fedoraproject.org/en-US/infra/day_to_day_fedora/#_emergencyauth...

I am unaware of any recent auth issues aside this kernel app one.
Everything has been working great since we moved the ipsilon servers to
f39 on march 27th. If there are, please let us know.

kevin

[Björn Persson]

Kevin Fenzi wrote:
> I am unaware of any recent auth issues aside this kernel app one.
> Everything has been working great since we moved the ipsilon servers to
> f39 on march 27th. If there are, please let us know.

Logging in to src.fedoraproject.org or pagure.io has been flaky to me in
recent weeks. I got Gateway Timeout a few minutes ago when logging in to
src.fedoraproject.org. I tried again and then it worked. Other times
I've gotten errors when logging in, but when I tried again I was logged
in without submitting the login form a second time.

Björn Persson

[Kevin Fenzi]

On Mon, May 27, 2024 at 06:07:10PM GMT, Björn Persson wrote:
> Kevin Fenzi wrote:
> > I am unaware of any recent auth issues aside this kernel app one.
> > Everything has been working great since we moved the ipsilon servers to
> > f39 on march 27th. If there are, please let us know.
>
> Logging in to src.fedoraproject.org or pagure.io has been flaky to me in
> recent weeks. I got Gateway Timeout a few minutes ago when logging in to
> src.fedoraproject.org. I tried again and then it worked. Other times
> I've gotten errors when logging in, but when I tried again I was logged
> in without submitting the login form a second time.

It sounds like perhaps a proxy is misbehaving... if there's any way you
could enable debug console next time you login and see what proxy you
were hitting when the timeout or issue happened that might be good info
for us.

kevin

[Christopher Klooz]

On 27/05/2024 18.16, Kevin Fenzi wrote:
> On Mon, May 27, 2024 at 06:07:10PM GMT, Björn Persson wrote:
> > Kevin Fenzi wrote:
> > > I am unaware of any recent auth issues aside this kernel app one.
> > > Everything has been working great since we moved the ipsilon servers to
> > > f39 on march 27th. If there are, please let us know.
> >
> > Logging in to src.fedoraproject.org or pagure.io has been flaky to me in
> > recent weeks. I got Gateway Timeout a few minutes ago when logging in to
> > src.fedoraproject.org. I tried again and then it worked. Other times
> > I've gotten errors when logging in, but when I tried again I was logged
> > in without submitting the login form a second time.
>
> It sounds like perhaps a proxy is misbehaving... if there's any way you
> could enable debug console next time you login and see what proxy you
> were hitting when the timeout or issue happened that might be good info
> for us.

I can confirm the experiences of Björn. It occurs from time to time. It sometimes is a time out, and sometimes a bad request. I will try to collect data about it and let you know. The issue is the FAS login screen, it is not related to any service that uses its token.

[Christopher Klooz]

I forgot to mention that additionally to bad requests and time outs, sometimes it is "unauthorized" (so 401). I just had that one. Unfortunately, I forgot to enable debug before :( I hope I manage to get used to enable debug over the next days when I login :D

On 27/05/2024 20.51, Christopher Klooz wrote:
> On 27/05/2024 18.16, Kevin Fenzi wrote:
> > On Mon, May 27, 2024 at 06:07:10PM GMT, Björn Persson wrote:
> > > Kevin Fenzi wrote:
> > > > I am unaware of any recent auth issues aside this kernel app one.
> > > > Everything has been working great since we moved the ipsilon servers to
> > > > f39 on march 27th. If there are, please let us know.
> > >
> > > Logging in to src.fedoraproject.org or pagure.io has been flaky to me in
> > > recent weeks. I got Gateway Timeout a few minutes ago when logging in to
> > > src.fedoraproject.org. I tried again and then it worked. Other times
> > > I've gotten errors when logging in, but when I tried again I was logged
> > > in without submitting the login form a second time.
> >
> > It sounds like perhaps a proxy is misbehaving... if there's any way you
> > could enable debug console next time you login and see what proxy you
> > were hitting when the timeout or issue happened that might be good info
> > for us.
> I can confirm the experiences of Björn. It occurs from time to time. It sometimes is a time out, and sometimes a bad request. I will try to collect data about it and let you know. The issue is the FAS login screen, it is not related to any service that uses its token.
>
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Björn Persson]

Kevin Fenzi wrote:
> It sounds like perhaps a proxy is misbehaving... if there's any way you
> could enable debug console next time you login and see what proxy you
> were hitting when the timeout or issue happened that might be good info
> for us.

I posted some logs here:
https://pagure.io/fedora-infrastructure/issue/11962#comment-914072

In one case proxy36.fedoraproject.org is mentioned.

Björn Persson