Description of problem: run bugzilla Version-Release number of selected component: python-bugzilla-cli-2.1.0-1.fc26 Additional info: reporter: libreport-2.9.1 cmdline: /usr/bin/python3 /usr/bin/bugzilla crash_function: main exception_type: RuntimeError executable: /usr/bin/bugzilla kernel: 4.13.11-200.fc26.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: bugzilla:1108:main:RuntimeError: Unexpected action 'None' Traceback (most recent call last): File "/usr/bin/bugzilla", line 1117, in <module> main() File "/usr/bin/bugzilla", line 1108, in main raise RuntimeError("Unexpected action '%s'" % action) RuntimeError: Unexpected action 'None' Local variables in innermost frame: buglist: [] bz: <bugzilla.rhbugzilla.RHBugzilla object at 0x7f58c26dc3c8> action: None args: [] opt: Namespace(bugzilla='https://bugzilla.redhat.com/xmlrpc.cgi', bztype='auto', cache_credentials=True, command_name=None, cookiefile=None, debug=False, ensure_logged_in=False, login=False, password=None, sslverify=True, tokenfile=None, username=None, verbose=False) parser: ArgumentParser(prog='bugzilla', usage=None, description=None, formatter_class=<class 'argparse.HelpFormatter'>, conflict_handler='error', add_help=True) unittest_bz_instance: None
Created attachment 1353194 [details] File: backtrace
Created attachment 1353195 [details] File: cgroup
Created attachment 1353196 [details] File: cpuinfo
Created attachment 1353197 [details] File: environ
Created attachment 1353198 [details] File: mountinfo
Created attachment 1353199 [details] File: namespaces
Created attachment 1353200 [details] File: open_fds
Thanks for the report, fixed upstream now. Since this is minor I'm just closing the bug, it'll be fixed with the next release and rebase commit 3d87c290682f75ffad0657f498759526184f8a11 Author: Cole Robinson <crobinso> Date: Tue Nov 21 15:44:19 2017 -0500 bin: Give consistent error with py3 if missing command (bz 1513819) There was a py3 behavior change here: https://stackoverflow.com/a/18283730 https://bugzilla.redhat.com/show_bug.cgi?id=1513819
*** Bug 1516305 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Installed `python-bugzilla` packages as advised in https://unix.stackexchange.com/questions/75820/debians-reportbug-equivalent-on-fedora-gnome and https://fedoraproject.org/wiki/Bugs_and_feature_requests#Command-line_interface to report bugs from command line, and it crashed. ➜ ~ bugzilla Traceback (most recent call last): File "/usr/bin/bugzilla", line 1117, in <module> main() File "/usr/bin/bugzilla", line 1108, in main raise RuntimeError("Unexpected action '%s'" % action) RuntimeError: Unexpected action 'None' reporter: libreport-2.9.3 cmdline: /usr/bin/python3 /usr/bin/bugzilla crash_function: main exception_type: RuntimeError executable: /usr/bin/bugzilla kernel: 4.15.13-300.fc27.x86_64 package: python-bugzilla-cli-2.1.0-2.fc27 reason: bugzilla:1108:main:RuntimeError: Unexpected action 'None' runlevel: N 5 type: Python3 uid: 1000
It is not fixed yet for Fedora 27. What to do?
It's just an error reporting issue. Your command line is invalid, you need to specify a complete command
Shouldn't `bugzilla` command at least provide a little human readable help if it command line is invalid? I would expect from officially recommended command line tool to at least have command line help.
Yes, that's the bug. But you can do the standard bugzilla --help to get that info as well
Reported upstream - https://github.com/python-bugzilla/python-bugzilla/issues/68 So, should this issue hang open until fixed upstream?
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.
python-bugzilla-2.2.0-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-8368410b1a
python-bugzilla-2.2.0-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-8368410b1a
python-bugzilla-2.2.0-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.