NOTE
If your issue is for security or deals with sensitive info please mark it as private using the checkbox below.
Please check https://www.fedorastatus.org for known outages before filing a ticket about an outage.
I'm unable to log into the Webhook To Fedora Messaging service: https://webhook.fedoraproject.org/
I click sign in, get redirected to the login form, then back to the page and it just says "Please wait while we sign you in".
I tried waiting, refreshing, trying again multiple times over the past half hour, and no luck.
Could you please have a look? Thanks!
as soon as possible / no specific date
Fails for me too. I see this in the browser console:
Access to XMLHttpRequest at 'https://id.fedoraproject.org/openidc/UserInfo' from origin 'https://webhook.fedoraproject.org' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status. index-ClioSfM5.js:172 OIDC callback error Error: Network Error at M.onerror (index-ClioSfM5.js:72:38277) (anonymous) @ index-ClioSfM5.js:172 id.fedoraproject.org/openidc/UserInfo:1 Failed to load resource: net::ERR_FAILED
@abompard would you have any ideas here?
Metadata Update from @james: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: high-gain, medium-trouble
Just failed for me too.
Hm, looking at the network the requests are really strange.
For example request to https://id.fedoraproject.org/.well-known/openid-configuration goes to ipsilon01.rdu3.fedoraproject.org and following request to https://id.fedoraproject.org/openidc/Token goes to ipsilon02.rdu3.fedoraproject.org
And there is 500 when trying to reach https://id.fedoraproject.org/openidc/UserInfo.
Did something change with the production Ipsilon? I redeployed the staging and the production environments in their current state this morning (see #317 and #318), and while the former works just fine, the latter has this problem. I was also tracing the production noggin logs while reattempting the login, but I suspect that I am looking in the wrong place. @abompard, mind having me around while you're giving this a stab?
noggin
I got this in ipsilon02's logs:
Traceback (most recent call last): File "/usr/lib/python3.14/site-packages/cherrypy/_cprequest.py", line 659, in respond self._do_respond(path_info) ~~~~~~~~~~~~~~~~^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/cherrypy/_cprequest.py", line 718, in _do_respond response.body = self.handler() ~~~~~~~~~~~~^^ File "/usr/lib/python3.14/site-packages/cherrypy/lib/encoding.py", line 223, in __call__ self.body = self.oldhandler(*args, **kwargs) ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/cherrypy/_cpdispatch.py", line 54, in __call__ return self.callable(*self.args, **self.kwargs) ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/ipsilon/util/page.py", line 85, in __call__ return op(*args, **kwargs).encode('utf-8') ~~^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/ipsilon/providers/common.py", line 105, in root return op(*args, **kwargs) File "/usr/lib/python3.14/site-packages/ipsilon/providers/openidc/api.py", line 383, in GET return self._get_userinfo(*kwargs, **kwargs) ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/ipsilon/providers/openidc/api.py", line 351, in _get_userinfo self._get_apistore_key('api_token')['userinfocode']) ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/ipsilon/providers/openidc/api.py", line 54, in _get_apistore_key return cherrypy.request.apistore[self][key] ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.14/site-packages/cherrypy/__init__.py", line 230, in __getattr__ return getattr(child, name) AttributeError: 'Request' object has no attribute 'apistore'
I'll investigate.
Metadata Update from @abompard: - Issue assigned to abompard
Ah, yeah, the package has probably been updated or reinstalled, because the patches that are applied by Ansible on Ipsilon were absent. I'll re-apply them, but ideally we should just update the ipsilon package to a more recent upstream. I'll do that but package updates take a while, so patching goes first.
Whats the status here?
I was able to log in just fine, and do what I needed to do!
So the issue I raised is resolved. Thanks! :)
Metadata Update from @asamalik: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)