Bug 1551288 - [abrt] fedora-gooey-karma: raise_for_status(): models.py:935:raise_for_status:HTTPError: 405 Client Error: Method Not Allowed for url: https://koji.fedoraproject.org/kojihub
Summary: [abrt] fedora-gooey-karma: raise_for_status(): models.py:935:raise_for_status...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-gooey-karma
Version: 27
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora QA Tools SIG
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:ba96475322d85f09d19857e9ec5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-04 12:55 UTC by mastaiza
Modified: 2018-11-30 17:33 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-11-30 17:33:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.37 KB, text/plain)
2018-03-04 12:55 UTC, mastaiza
no flags Details
File: cgroup (289 bytes, text/plain)
2018-03-04 12:55 UTC, mastaiza
no flags Details
File: cpuinfo (1.22 KB, text/plain)
2018-03-04 12:55 UTC, mastaiza
no flags Details
File: environ (1.43 KB, text/plain)
2018-03-04 12:55 UTC, mastaiza
no flags Details
File: mountinfo (3.43 KB, text/plain)
2018-03-04 12:55 UTC, mastaiza
no flags Details
File: namespaces (129 bytes, text/plain)
2018-03-04 12:55 UTC, mastaiza
no flags Details
File: open_fds (2.42 KB, text/plain)
2018-03-04 12:55 UTC, mastaiza
no flags Details

Description mastaiza 2018-03-04 12:55:22 UTC
Version-Release number of selected component:
fedora-gooey-karma-0.1-8.fc26

Additional info:
reporter:       libreport-2.9.3
cmdline:        /usr/bin/python2 -tt /bin/fedora-gooey-karma
crash_function: raise_for_status
exception_type: HTTPError
executable:     /bin/fedora-gooey-karma
kernel:         4.15.4-300.fc27.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
models.py:935:raise_for_status:HTTPError: 405 Client Error: Method Not Allowed for url: https://koji.fedoraproject.org/kojihub

Traceback (most recent call last):
  File "/bin/../share/fedora-gooey-karma/packagesworker.py", line 59, in run
    self.load_installed(releasever)
  File "/bin/../share/fedora-gooey-karma/packagesworker.py", line 83, in load_installed
    tagged_packages = session.listTagged('f' + str(releasever) + '-updates-testing')
  File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 2015, in __call__
    return self.__func(self.__name, args, opts)
  File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 2478, in _callMethod
    return self._sendCall(handler, headers, request)
  File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 2391, in _sendCall
    return self._sendOneCall(handler, headers, request)
  File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 2437, in _sendOneCall
    r.raise_for_status()
  File "/usr/lib/python2.7/site-packages/requests/models.py", line 935, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
HTTPError: 405 Client Error: Method Not Allowed for url: https://koji.fedoraproject.org/kojihub

Local variables in innermost frame:
reason: u'Method Not Allowed'
http_error_msg: u'405 Client Error: Method Not Allowed for url: https://koji.fedoraproject.org/kojihub'
self: <Response [405]>

Comment 1 mastaiza 2018-03-04 12:55:27 UTC
Created attachment 1403767 [details]
File: backtrace

Comment 2 mastaiza 2018-03-04 12:55:29 UTC
Created attachment 1403768 [details]
File: cgroup

Comment 3 mastaiza 2018-03-04 12:55:31 UTC
Created attachment 1403769 [details]
File: cpuinfo

Comment 4 mastaiza 2018-03-04 12:55:32 UTC
Created attachment 1403770 [details]
File: environ

Comment 5 mastaiza 2018-03-04 12:55:34 UTC
Created attachment 1403771 [details]
File: mountinfo

Comment 6 mastaiza 2018-03-04 12:55:35 UTC
Created attachment 1403772 [details]
File: namespaces

Comment 7 mastaiza 2018-03-04 12:55:37 UTC
Created attachment 1403773 [details]
File: open_fds

Comment 8 Ben Cotton 2018-11-27 16:47:47 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 9 Adam Williamson 2018-11-27 19:39:04 UTC
This is quite likely still valid, but kinda filed under 'gooey karma is totally broken and has been for a while'. It got retired a while ago:

https://src.fedoraproject.org/rpms/fedora-gooey-karma/c/a6854bb95b559d32793540d71188bfffa6234271?branch=master

Comment 10 Ben Cotton 2018-11-30 17:33:49 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.