Bug 1259681 - bodhi -m fails to list updates
Summary: bodhi -m fails to list updates
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: bodhi
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Randy Barlow
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1266692 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-03 10:55 UTC by Stef Walter
Modified: 2017-08-08 12:12 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 12:12:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Stef Walter 2015-09-03 10:55:26 UTC
Description of problem:

bodhi -m fails to list updates

[stef@falcon tools]$ bodhi -m
Password for stef: 
ServerError(https://admin.fedoraproject.org/updates/list, 404, Not Found)
Traceback (most recent call last):
  File "/usr/bin/bodhi", line 407, in main
    data = bodhi.query(mine=opts.mine)
  File "/usr/lib/python2.7/site-packages/fedora/client/bodhi.py", line 148, in query
    return self.send_request('list', req_params=params, auth=auth)
  File "/usr/lib/python2.7/site-packages/fedora/client/baseclient.py", line 379, in send_request
    auth_params=auth_params, retries=retries, timeout=timeout)
  File "/usr/lib/python2.7/site-packages/fedora/client/proxyclient.py", line 505, in send_request
    raise ServerError(url, http_status, msg)
ServerError: ServerError(https://admin.fedoraproject.org/updates/list, 404, Not Found)

Version-Release number of selected component (if applicable):

bodhi-client-0.9.12.2-3.fc22

How reproducible:

Every time

Steps to Reproduce:
1. bodhi -m
2. Type password

Actual results:

ServerError

Expected results:

A list

Comment 1 Gerd Pokorra 2015-09-27 19:01:26 UTC
Currently the command line for bodhi with version 2 is broken (F22). For setting buildroots and submitting updates the web UI needed to be used
https://bodhi.fedoraproject.org/

Comment 2 Gerd Pokorra 2015-12-15 00:40:23 UTC
*** Bug 1266692 has been marked as a duplicate of this bug. ***

Comment 3 Jonathan Wakely 2016-05-20 15:56:16 UTC
This makes it impossible to automate rebuilds of large number of packages with automatic dependency resolution, because I can no longer script the creation of buildroot overrides. I now have to manually intervene, creating one set of packages, then waiting for that step to finish, then manually creating overrides, then starting the next set of rebuilds. When there are several levels of dependency this makes the process quite painful and slow.

Comment 4 Jonathan Wakely 2016-05-20 16:06:20 UTC
This seems to be https://github.com/fedora-infra/bodhi/issues/810

Comment 5 Fedora End Of Life 2016-07-19 17:46:06 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 Jonathan Wakely 2016-07-19 17:52:40 UTC
In F23 'bodhi -m' prints updates now, but ends with:

Traceback (most recent call last):
  File "/usr/bin/bodhi", line 537, in <module>
    main()
  File "/usr/bin/bodhi", line 411, in main
    log.info(data['title'])
KeyError: 'title'


However the error from Bug 1266692 (closed as a dup of this one) still gives the same output in F23, as does 'bodhi -O'



$ bodhi -O 
No handlers could be found for logger "fedora.client.bodhi"
Traceback (most recent call last):
  File "/usr/bin/bodhi", line 537, in <module>
    main()
  File "/usr/bin/bodhi", line 451, in main
    }, auth=True)
  File "/usr/lib/python2.7/site-packages/fedora/client/openidbaseclient.py", line 240, in send_request
    output = func(method, **kwargs)
  File "/usr/lib/python2.7/site-packages/fedora/client/openidbaseclient.py", line 78, in _decorator
    output = func(request, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/fedora/client/openidbaseclient.py", line 195, in _authed_post
    response = self._session.post(url, params=params, data=data, **kwargs)
  File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 518, in post
    return self.request('POST', url, data=data, json=json, **kwargs)
TypeError: request() got an unexpected keyword argument 'req_params'


It's still not possible to use bodhi to automate creation of the overrides needed for large rebuilds involving many packages and long dependency chains.

Comment 7 Randy Barlow 2016-10-17 21:27:03 UTC
Hello!

I have recently become the primary caretaker of Bodhi and I've inherited a number of issues related to bodhi 0.9. I wanted to be forthcoming with you that it will be difficult for me to fix issues with bodhi 0.9 while also pressing forward with bodhi 2, especially since I do not have any familiarity with the bodhi 0.9 codebase. I'm happy to keep this bug open to track the problem, but I would also encourage you to please test the bodhi 2 client (currently available in Rawhide and Copr[0]). Unfortunately, the bodhi 2 client is not backwards compatible with bodhi 0.9, so at this time I only plan for bodhi 2 to be released with Fedora 26 and EPEL 7 (with special permission from the EPEL SC).

Here are some options you could pursue for this issue:

0) Write a patch for me that can be applied with the spec file. If you are willing to take the time to learn the bodhi 0.9 code, write a patch, and test it, I am willing to accept patches to be applied during build.
1) Use Rawhide.
2) Install bodhi 2 from my Copr[0].

I apologize as I understand that this is probably disappointing news for you to hear, but I thought it would be better to be forthcoming than to let the bug languish. I appreciate your understanding!


[0] https://copr.fedorainfracloud.org/coprs/bowlofeggs/bodhi/

Comment 8 Gerd Pokorra 2016-10-19 09:12:35 UTC
I would like to test the bodhi2 client at my Fedora 24 production system.

I add the repo file:

ls /etc/yum.repos.d/bowlofeggs-bodhi-fedora-24.repo 
/etc/yum.repos.d/bowlofeggs-bodhi-fedora-24.repo

Now I see this packages: 

> dnf search bodhi
Last metadata expiration check: 0:46:23 ago on Wed Oct 19 10:21:48 2016.
============================= N/S Matched: bodhi ==============================
bodhi.src : A modular framework that facilitates publishing software updates
bodhi-client.noarch : Bodhi Client
bodhi-docs.noarch : Bodhi documentation
abrt-plugin-bodhi.x86_64 : abrt's bodhi plugin
python2-bodhi.noarch : Common files shared by bodhi-client and bodhi-server
bodhi-server.noarch : A modular framework that facilitates publishing software
                    : updates


What do I need to do next to test the bodhi2 client?

Comment 9 Jonathan Wakely 2016-10-19 09:18:22 UTC
dnf copr enable bowlofeggs/bodhi 
dnf update bodhi-client

Comment 10 Gerd Pokorra 2016-10-24 08:20:54 UTC
I added already some information from this ticket about the Bodhi 2 CLI to the wiki page http://fedoraproject.org/wiki/Bodhi

in the chapter

http://fedoraproject.org/wiki/Bodhi#Using_the_bodhi_command-line_client

Comment 11 Randy Barlow 2016-10-24 22:13:47 UTC
Thank you for documenting that Gerd, that was very helpful of you! I made some small modifications to note that Rawhide (F26) has Bodhi 2.

Comment 12 Fedora End Of Life 2016-11-24 12:26:48 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 Fedora End Of Life 2017-07-25 19:14:21 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 14 Fedora End Of Life 2017-08-08 12:12:17 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.