Describe what you would like us to do:

Investigate what's going wrong on ipsilon and have the service back in action

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

ASAP as actually I can't remotely provision instances in AWS needed for another team ( see https://pagure.io/centos-infra/issue/95)

Try again now?

Works now .. thanks !

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

4 years ago

I still cannot log in into Amazon AWS because of 500 - Internal Server Error

We have seen this in the past where fas returns incomplete information to ipsilon...

can you try clearing any cookies or stored data from id.fedoraproject.org and see if it start working?

@kevin AWS and bugzilla both use SAML which gets borke in ipsilon every now and then

Steps to debug:

Open all the web pod of ipsilon in different tags - Open the logs
Open bugzilla.redhat.com in a tab using the private browser mode
Try logging into bugzilla using the Fedora contributor button in the drop-down
Check the recent logs of the pods and find the one saying something like: DEBUG(providers/saml2/auth.py:176 Redirect.saml2login()): saml2: 'NoneType' object has no attribute 'get_login_handler' - copy the name of that pod
Go to the openshift's main node
Delete the pod using: # oc -n ipsilon delete pod <pod-name> (for example: # oc -n ipsilon delete pod ipsilon-24-8ztdd) - Openshift will automatically spawn a new one
Try login on bugzilla again - it should work (or maybe another pod is mis-behaving?)

@frostyx can you try again now?

Huh, have we reported this upstream? we should...