Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When run virt-who with refresh interval below to 60s at CLI mode, it will show a ambiguous warning info
Version-Release number of selected component (if applicable):
virt-who-0.16-5.el6.noarch
subscription-manager-1.16.8-3.el6.x86_64
python-rhsm-1.16.6-1.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Register system to satellite6.
2. Run virt-who with refresh interval 3s at CLI mode.
[root@sgi-xe270-01 ~]# virt-who --hyperv --hyperv-owner=xxxxxx --hyperv-env=xxxxx --hyperv-server=10.73.5.227 --hyperv-username=administrator --hyperv-password=Welcome1 -i 3
2016-03-03 03:33:10,240 WARNING: Interval value may not be set below the default of 60 seconds. Will use default value.
Actual results:
It will show warning info as the following:
WARNING: Interval value may not be set below the default of 60 seconds. Will use default value.
Expected results:
It should throw warning info as the following:
WARNING: Interval value maybe set below the default of 60 seconds. Will use default value.
Additional info:
"WARNING: Interval value maybe set below the default of 60 seconds. Will use default value." - this is also a bit confusing.
What about this wording:
WARNING: Interval value can't be lower than 60 seconds. Default value of 60 seconds will be used.
verified in virt-who-0.18-1.el6.
when interval < 60s, it will show:
[virtwho.init WARNING] MainProcess(30487):MainThread @parser.py:parseOptions:279 - Interval value can't be lower than 60 seconds. Default value of 60 seconds will be used.
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://rhn.redhat.com/errata/RHBA-2017-0675.html