#10480 Ipsilon: 500 - Internal Server Error when trying to log in to bugzilla.redhat.com
Closed: Fixed with Explanation 2 years ago by kevin. Opened 2 years ago by rathann.

Describe what you would like us to do:


Ipsilon is giving me 500 Internal Server Error when trying to log in to https://bugzilla.redhat.com via "Fedora Account System" link.

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


As soon as possible.


Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: medium-gain, medium-trouble, ops

2 years ago

Same here :disappointed: Curious why it is not fixed for 8 hours :crying_cat_face:

Can you confirm it's fixed now?

No, it's still occurring.

Its working fine for me.

Did you change anything recently on your account? perhaps adding some more ssh keys?

No, I haven't added any SSH keys in the last few weeks.

The auth system is saying success...

I assume you have tried other browsers, clearning cookies?

I tried clearing cookies, yes. This is only an issue for bugzilla.redhat.com. Bodhi website works fine. Both work fine under Chromium, too.

I'm experiencing the same behavior as well; "Fedora Account System" from bugzilla returns HTTP/500 error message.
Screenshot_from_2022-01-26_17-49-26.png

UPDATE: Removing all the redhat.com cookies resolved the issue.

@rathann ok, can you clear all cookies from redhat.com and try again, and then note here exactly when the 500 appeared so I can look into the logs again?

Done. I got the error at Tue 1 Feb 14:21:49 UTC 2022.

ipsilon_transaction_id = acacb3b0-5c0d-4fea-aafe-167d4ce3b67e

ok. Can you please try again now?

@kevin I logged out of bugzilla, cleared redhat.com cookies and retried (while having an active Kerberos ticket). Error 500 is gone.

Thanks!

What was the issue?

We have a script that generates SAML data in a xml file, which ipsilon then includes.

We have 2 ipsilon servers ( 01 and 02)

The second server had (for some unknown reason) a 0 length saml2 xml file. This meant that any requests to it failed. You must have just gotten unlucky and mostly hit it. ;(

Metadata Update from @kevin:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog
Attachments 1