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.

Bug 1188706

Summary: typo in error message "exitting" -> "exiting" and some more
Product: Red Hat Enterprise Linux 7 Reporter: Jan Hutař <jhutar>
Component: virt-whoAssignee: Radek Novacek <rnovacek>
Status: CLOSED ERRATA QA Contact: Li Bin Liu <liliu>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.1CC: gxing, ovasik, sgao, shihliu
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: virt-who-0.14-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 11:56:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Hutař 2015-02-03 14:52:22 UTC 
Description of problem:
There is a typo in error message "exitting" -> "exiting". That made me to try and run code through hunspell.


Version-Release number of selected component (if applicable):
virt-who-0.11-5.el7.noarch


How reproducible:
always


Steps to Reproduce:
1. # virt-who --one-shot --satellite --satellite-server=<sat_fqdn> --satellite-username=<sat_user> --satellite-password=<sat_pass> -d --rhevm --rhevm-server=<ip> --rhevm-username=<user> --rhevm-password=<pass>


Actual results:
ERROR: Required parameter 'owner' is not set, exitting


Expected results:
ERROR: Required parameter 'owner' is not set, exiting


Additional info:
Rest of the typos I have found:

39c39
< /usr/share/virt-who/daemon/daemon.py:""" Daemon process behaviour.
---
> /usr/share/virt-who/daemon/daemon.py:""" Daemon process behavior.
187,188c187,188
< /usr/share/virt-who/manager/satellite/satellite.py:                self.logger.exception("Unable to send host/guest assocaition to the satellite:")
< /usr/share/virt-who/manager/satellite/satellite.py:                raise SatelliteError("Unable to send host/guest assocaition to the satellite: % " % str(e))
---
> /usr/share/virt-who/manager/satellite/satellite.py:                self.logger.exception("Unable to send host/guest association to the satellite:")
> /usr/share/virt-who/manager/satellite/satellite.py:                raise SatelliteError("Unable to send host/guest association to the satellite: % " % str(e))
682c682
< /usr/share/virt-who/virt/rhevm/rhevm.py:                self.logger.warning("Guest %s claims that it belongs to host %s which doen't exist" % (guest_id, host_id))
---
> /usr/share/virt-who/virt/rhevm/rhevm.py:                self.logger.warning("Guest %s claims that it belongs to host %s which doesn't exist" % (guest_id, host_id))
766c766
< /usr/share/virt-who/virtwho.py:                                epilog="virt-who also reads enviromental variables. They have the same name as command line arguments but uppercased, with underscore instead of dash and prefixed with VIRTWHO_ (e.g. VIRTWHO_ONE_SHOT). Empty variables are considered as disabled, non-empty as enabled")
---
> /usr/share/virt-who/virtwho.py:                                epilog="virt-who also reads enviromental variables. They have the same name as command line arguments but uppercase, with underscore instead of dash and prefixed with VIRTWHO_ (e.g. VIRTWHO_ONE_SHOT). Empty variables are considered as disabled, non-empty as enabled")
840c840
< /usr/share/virt-who/virtwho.py:            logger.error("Required parameter '%s' is not set, exitting" % name)
---
> /usr/share/virt-who/virtwho.py:            logger.error("Required parameter '%s' is not set, exiting" % name)
Comment 2 Radek Novacek 2015-05-07 11:03:17 UTC 
This bug is resolved upstream and will be fixed by virt-who rebase (bug 1200374).
Comment 3 Radek Novacek 2015-06-23 13:33:17 UTC 
Fixed in virt-who-0.14-1.el7.
Comment 5 Liushihui 2015-07-21 08:39:47 UTC 
Reopen it since virt-who can't monitor parameter 'owner' in the latest virt-who-0.14-1.el7.noarch.

Checked version:
virt-who-0.14-1.el7.noarch
subscription-manager-1.15.5-1.el7.x86_64
python-rhsm-1.15.3-1.el7.x86_64

Checked process:
1 Register system to satellite5.7
2 Run virt-who with command line without "--owner"
[root@hp-z220-05 product-default]# virt-who -d -o --satellite --satellite-server=satellite57.July20.redhat.com --satellite-username=admin --satellite-password=redhat --rhevm --rhevm-env=Library --rhevm-server=https://10.66.79.83:443 --rhevm-username=admin@internal --rhevm-password=redhat
2015-07-21 16:33:49,768 INFO: Using configuration "env/cmdline" ("rhevm" mode)
2015-07-21 16:33:50,018 DEBUG: Initializing satellite connection to https://satellite57.July20.redhat.com/XMLRPC
2015-07-21 16:33:50,018 INFO: Initialized satellite connection
2015-07-21 16:33:50,018 INFO: Sending update in hosts-to-guests mapping: {'47a3d1de-7b73-4224-811f-011dc40de87f': []}
2015-07-21 16:33:50,018 DEBUG: Loading systemid for 47a3d1de-7b73-4224-811f-011dc40de87f
2015-07-21 16:33:50,018 DEBUG: Loading system id info from /var/lib/virt-who/hypervisor-systemid-47a3d1de-7b73-4224-811f-011dc40de87f

Result: virt-who hasn't monitor the --env parameter, it should show error
"Required parameter 'owner' is not set, exiting"
Comment 6 Radek Novacek 2015-07-30 07:22:41 UTC 
--owner-* is only used in the SAM mode (not with --satellite) and therefore it's not even checked.
Comment 7 Liushihui 2015-07-30 08:06:47 UTC 
Verified it on virt-who-0.14-2.el7.noarch. 

Verified version
virt-who-0.14-2.el7.noarch
subscription-manager-1.15.6-1.el7.x86_64
python-rhsm-1.15.3-1.el7.x86_64
SAM-1.4.1-RHEL-6-20141113.0

Verified process
1 Check the output when it hasn't set "--owner" option
[root@hp-z220-06 ~]# virt-who -d -i 3 --sam --rhevm --rhevm-env=Library --rhevm-owner= --rhevm-server=https://10.66.79.83:443 --rhevm-username=admin@internal --rhevm-password=redhat
Option --rhevm-owner (or VIRTWHO_RHEVM_OWNER environment variable) needs to be set

Result:
It hasn't show error word "exitting". Therefore, verified it
Comment 8 errata-xmlrpc 2015-11-19 11:56:04 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://rhn.redhat.com/errata/RHBA-2015-2370.html