Resolve account issues or point out my error in logging onto system.
Log in at https://accounts.fedoraproject.org - Successful
Log into bugzilla.redhat.com with FAS account - Fail "400 - Bad Request - Invalid transaction id"
submit linux 6.9.1 kernel test 'authenticated' (./runtests.sh) - Fail - Traceback (most recent call last): File "/data/packages/kernel-tests/./fedora_submit.py", line 43, in <module> submitclient.login( File "/usr/lib/python3.12/site-packages/fedora/client/openidbaseclient.py", line 303, in login response = openid_login( ^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/fedora/client/openidproxyclient.py", line 138, in openid_login raise AuthError(output['message'])
How are you trying to login there?
Via the "Fedora Account system" button? Or via username / password?
I do see that you have an account there, so normally I would expect either way to work
As for the traceback, you need to update that script... 'git pull' or check out a new copy.
Thank you for your time. I did a git pull for a new kernel-tests directory and got the same error on trying to use authentication. This happened on two different computers fully updated on fc40. sha256sum: 6ef83433712ebf24a4c5020b0125a6526c69394281cef6d477b998584904d766 /data/packages/kernel-tests/./fedora_submit.py c78fdc7c3c61c277347b5c0a671637fc7858a3986f04f905893bb256be2556a8 /usr/lib/python3.12/site-packages/fedora/client/openidbaseclient.py 8385af871ec0a6de457040e3216ba712072f20147e005065376ff0ecdbf06325 /usr/lib/python3.12/site-packages/fedora/client/openidproxyclient.py 702b6d4eada284a438dbbf8e8a3091534672c883044c1dd6d2b20ccbb161e2e0 /data/packages/kernel-tests/runtests.sh
Logging in to bugzilla.redhat.com -> 'Login'->Fedora Account System:
"https://bugzilla.redhat.com/saml2_metadata.cgi wants to use your Fedora Account
enter your Fedora Account credentials below to authorize https://bugzilla.redhat.com/saml2_metadata.cgi" username/password entered and: "400 - Bad Request"
My password contains a special character, but has worked without problem in the past. Could that be an issue (password policy has changed?)?
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: Needs investigation
ok, this is apparently: https://pagure.io/kernel-tests/issue/50
So, please add yourself to that ticket/track it there.
Basically the auth method changed for that app...
Metadata Update from @kevin: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.