RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1542358 - event-test.py help info error
Summary: event-test.py help info error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt-python
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: lcheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-06 07:25 UTC by Yanqiu Zhang
Modified: 2018-10-30 11:10 UTC (History)
7 users (show)

Fixed In Version: libvirt-python-4.4.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 11:10:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:3204 0 None None None 2018-10-30 11:10:41 UTC

Description Yanqiu Zhang 2018-02-06 07:25:25 UTC
Description of problem:
event-test.py help info error

Version-Release number of selected component (if applicable):
libvirt-python-3.9.0-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. # python /usr/share/doc/libvirt-python-3.9.0/examples/event-test.py  -h
usage: event-test.py [-hdl] [uri]
   uri will default to qemu:///system
   --help, -h   Print(this help message
   --debug, -d  Print(debug output
   --loop=TYPE, -l   Choose event-loop-implementation (native, poll, asyncio)
   --timeout=SECS  Quit after SECS seconds running


Actual results:
There're extra '(' in introduction for '--debug' and '--help'

Expected results:
   --help, -h   Print this help message
   --debug, -d  Print debug output

Additional info:

Comment 1 Jiri Denemark 2018-02-06 11:01:16 UTC
Fixed upstream by

commit 324197bfaaf0a7628b467db31f2cde27b6c6a4fd
Refs: v4.0.0-1-g324197b
Author:     Jiri Denemark <jdenemar>
AuthorDate: Tue Feb 6 11:58:42 2018 +0100
Commit:     Jiri Denemark <jdenemar>
CommitDate: Tue Feb 6 11:58:42 2018 +0100

    event-test.py: Remove extra ( in --help output

    Signed-off-by: Jiri Denemark <jdenemar>

Comment 3 lcheng 2018-06-26 03:17:42 UTC
Verify on libvirt-python-4.4.0-1.el7.x86_64. Don't find extra '(' in introduction.


# python /usr/share/doc/libvirt-python-4.4.0/examples/event-test.py -h
usage: event-test.py [-hdl] [uri]
   uri will default to qemu:///system
   --help, -h   Print this help message
   --debug, -d  Print debug output
   --loop=TYPE, -l   Choose event-loop-implementation (native, poll, asyncio)
   --timeout=SECS  Quit after SECS seconds running


So move to VERIFIED.

Comment 5 errata-xmlrpc 2018-10-30 11:10:24 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:3204


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