Hide Forgot
Description of problem: FEK fails to run with bodhi-client-6.0.0-2.fc36.noarch: Traceback (most recent call last): File "/usr/bin/fedora-easy-karma", line 881, in <module> fek = FedoraEasyKarma() File "/usr/bin/fedora-easy-karma", line 505, in __init__ bc = BodhiClient(username=self.options.fas_username, TypeError: BodhiClient.__init__() got an unexpected keyword argument 'username' Version-Release number of selected component (if applicable): bodhi-client-6.0.0-2.fc36.noarch fedora-easy-karma-0-0.49.20210526gitfa76ab7.fc36.noarch How reproducible: always
*** ConfidentialBug 2097174 has been marked as a duplicate of this bug. ***
I'm happy to help adjust the code to Bodhi Client 6.0 if you need any.
Thanks Aurelien, but I'm on it :-) Everyone, please test this scratch build and tell me if it works OK for you: https://koji.fedoraproject.org/koji/taskinfo?taskID=88287231 You'll be asked to open a web browser, log in to FAS and copy-paste a code back to terminal when you run FEK (not sure how long that token lasts, this process might need repeating in some time again).
Aurelien, will there be bodhi-client 6.0 for Fedora 35 as well? I re-wrote FEK to target bodhi-client 6.0 only to find out that it's not available in F35, not even updates-testing. Which means I'd have to have two different codepaths in FEK to support both bodhi-client 6.0 and 5.7.5 :-/
Yes, I will make a package update for F35 too. I thought I had done it but apparently not, I'll do it right away (I need to request the branch first so it make take some more time).
(In reply to Kamil Páral from comment #3) > Thanks Aurelien, but I'm on it :-) > > Everyone, please test this scratch build and tell me if it works OK for you: > https://koji.fedoraproject.org/koji/taskinfo?taskID=88287231 > > You'll be asked to open a web browser, log in to FAS and copy-paste a code > back to terminal when you run FEK (not sure how long that token lasts, this > process might need repeating in some time again). Tested and works using website token. $ sudo dnf install fedora-easy-karma-0-0.50.20220615git45d9c80.1.fc36.noarch.rpm $ fedora-easy-karma Logging into Bodhi... Authenticating... Please open your browser to: https://id.fedoraproject.org/openidc/Authorization?response_type=code&client_id=bodhi-client&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&scope=openid+email+profile+https%3A%2F%2Fid.fedoraproject.org%2Fscope%2Fgroups+https%3A%2F%2Fid.fedoraproject.org%2Fscope%2Fagreements&state=bgRafWOBuu3FlZDiqz68TiAh8ChpMB Paste here the code that you got after logging in: code=xx Login successful! Getting list of installed packages... Waiting for oraculum instance to return list of packages in updates-testing... found 299 testing updates
Bodhi 6.0 for F35 : https://bodhi.fedoraproject.org/updates/FEDORA-2022-6427738348
Scratch build works here too on F36.
works but one little error: fedora-easy-karma: error: no such option: --fas-username
Hey Kamil, if you want I can wait for your update to be ready before pushing bodhi-client to stable in F36 and F35. Would that be useful?
(In reply to jpbn from comment #9) > works but one little error: > > fedora-easy-karma: error: no such option: --fas-username As mentioned in comment 3, log in is now done via single sign on token in web browser. Running fedora-easy-karma without options lets you provide username and password on the website URL it shows in console.
(In reply to Aurelien Bompard from comment #10) > Hey Kamil, if you want I can wait for your update to be ready before pushing > bodhi-client to stable in F36 and F35. Would that be useful? Thanks, but no need. I think testers of unstable updates can handle this small inconvenience easily, and I'll submit a FEK update into Bodhi soon. But I do have a different question. It seems to me that I need to copy the FAS login token regularly. It doesn't seem to last more than a few hours. I don't know how long exactly, it will take time to figure it out. Is it expected? How long is the token expected to last? Today morning, I verified that the token is present in ~/.config/bodhi/client.json, but when I ran FEK, it cleared it in client.json and asked for the token again. Yesterday this happened to me as well at least once or twice. Perhaps switching between bodhi-client 6.0 and 5.7.5 could cause this? Or the fact that I have both prod and stg token present, and it gets confused? FEK calls this: from bodhi.client.bindings import BodhiClient bc = BodhiClient() bc.ensure_auth() If people need to copy the token every day, that would make FEK usage a bit inconvenient :-/ (In reply to jpbn from comment #9) > works but one little error: > > fedora-easy-karma: error: no such option: --fas-username Yes, that's expected, as Jens explained. FEK no longer cares about your FAS username, because you provide it into the web browser.
The token should last much longer than a day, I'll investigate that. It's possible that switching between versions caused this, since the authentification system is different. Switching between staging and prod however should not cause this issue.
FEDORA-2022-e6b7cc89a8 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e6b7cc89a8
FEDORA-2022-f08c613dbf has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f08c613dbf
FEDORA-2022-f08c613dbf has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-f08c613dbf` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-f08c613dbf See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-e6b7cc89a8 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-e6b7cc89a8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e6b7cc89a8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
(In reply to Aurelien Bompard from comment #13) > The token should last much longer than a day, I'll investigate that. It doesn't seem to be caused by switching versions. The token is marked to expire in an hour (!). I filed it here: https://github.com/fedora-infra/bodhi/issues/4581
FEDORA-2022-e6b7cc89a8 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-f08c613dbf has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.