#12294 400 - Bad Request Invalid transaction id If the error persists and if you think this is an error, contact Fedora Infra to resolve the problem.
Closed: Will Not/Can Not fix 17 days ago by zlopez. Opened 21 days ago by romulasry.

NOTE

If your issue is for security or deals with sensitive info please
mark it as private using the checkbox below.

Describe what you would like us to do: Look into it


When do you need this to be done by? (YYYY/MM/DD)

---- N/A

https://id.fedoraproject.org/openidc/Continue?ipsilon_transaction_id=aea55a98-f5d7-4931-9bbc-12be14696f81


Got the issue today while trying to connect to Bodhi.
Not sure if related, but I purged all Firefox content and tried again, and login was ok

It seems to do it every 2-3 time.

Deleted all firefox content and I am still getting this error most of the times I have tried.

Deleted all firefox content and I am still getting this error most of the times I have tried.

It's strange it happened to me once and after that I logged in without issue.

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: Needs investigation, release-monitoring

20 days ago

Metadata Update from @zlopez:
- Issue assigned to zlopez

18 days ago

I spend some time today to investigate this issue and I was able to narrow it down a little.

The authentication request is correctly forwarded to ipa01 from ipsilon01 and ipa01 is the machine that returns 400.

The problem with this issue is, that I was able to only reproduce it once and even that happened after 5-6 retries. When I found out that this is happening on ipa01 I increased the log level of httpd server as this is the service processing the request, but after enabling debug log level I wasn't able to reproduce the issue even after 20 retries.

So I'm not sure if we want to investigate this further as it's hard to reproduce. I set the log level back to default on httpd as it was generating too much output on debug.

@romulasry How often is this happening for you now?

Not very often now, thanks.

I will close it as can not fix, as it not easy to reproduce. Feel free to reopen this issue when it's start happening too often.

Metadata Update from @zlopez:
- Issue close_status updated to: Will Not/Can Not fix
- Issue status updated to: Closed (was: Open)

17 days ago

Log in to comment on this ticket.

Metadata