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 1188568 - virt-who requires --*-env and --*-owner to be set even for satellite 5
Summary: virt-who requires --*-env and --*-owner to be set even for satellite 5
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-who
Version: 6.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Radek Novacek
QA Contact: gaoshang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-03 09:25 UTC by Radek Novacek
Modified: 2016-12-01 00:33 UTC (History)
4 users (show)

Fixed In Version: virt-who-0.12-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-22 07:15:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1377 0 normal SHIPPED_LIVE virt-who bug fix and enhancement update 2015-07-20 17:58:35 UTC

Description Radek Novacek 2015-02-03 09:25:52 UTC 
When virt-who is used in satellite 5 mode, it requires --*-env and --*-owner options to be set, although they're not used.

virt-who --one-shot --satellite --satellite-server=<server> --satellite-username=<username> --satellite-password=<pwd> -d --rhevm --rhevm-server=<server> --rhevm-username=<username> --rhevm-password=<pwd>

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

Workaround is to supply --*-env=something and --*-owner=something, these options won't be used.
Comment 2 Radek Novacek 2015-02-26 14:56:03 UTC 
This bug has been addressed upstream and will be fixed by rebase of virt-who in RHEL-6.7.
Comment 3 Radek Novacek 2015-02-27 19:42:32 UTC 
Fixed by rebase to virt-who-0.12-1.el6.
Comment 5 Liushihui 2015-04-07 02:35:42 UTC 
Verified it on virt-who-0.12-2.el6.noarch.

Verified version:
virt-who-0.12-2.el6.noarch
subscription-manager-1.14.1-1.el6.x86_64
python-rhsm-1.14.1-1.el6.x86_64
Satellite-5.7.0-RHEL6-re20150108.2-x86_64

Verified process:
1.Register rhel to Satellite-5.7
[root@hp-z220-06 rhn]# rhnreg_ks --username virtwho_test --password=redhat123
[root@hp-z220-06 rhn]# subscription-manager identity
server type: RHN Classic
2. Make virt-who run at command-line without --*-env and --*-owner options to be set.
[root@hp-z220-06 rhn]# virt-who --one-shot --satellite --satellite-server=10.66.128.4 --satellite-username=virtwho_test --satellite-password=redhat123 --rhevm --rhevm-server=https://10.66.79.58:443 --rhevm-username=admin@internal --rhevm-password=redhat --rhevm-env=test --rhevm-owner=aaa
2015-04-07 10:34:27,024 INFO: Using configuration "env/cmdline" ("rhevm" mode)
2015-04-07 10:34:27,329 INFO: Initialized satellite connection
2015-04-07 10:34:27,329 INFO: Sending update in hosts-to-guests mapping: {'7a1a3ef3-4d6b-40fe-ae13-32e5289a7f95': []}

Result: virt-who can send host/guest mapping to satellite, therefore, verify it.
Comment 6 Liushihui 2015-04-13 03:38:36 UTC 
Please ignore the comment 5, update the verify process as the following:

Verified it on virt-who-0.12-2.el6.noarch.

Verified version:
virt-who-0.12-2.el6.noarch
subscription-manager-1.14.1-1.el6.x86_64
python-rhsm-1.14.1-1.el6.x86_64
Satellite-5.7.0-RHEL6-re20150108.2-x86_64

Verified process:
1.Register rhel to Satellite-5.7
[root@hp-z220-06 rhn]# rhnreg_ks --username virtwho_test --password=redhat123
[root@hp-z220-06 rhn]# subscription-manager identity
server type: RHN Classic
2. Make virt-who run at command-line without --*-env and --*-owner options to be set.
[root@hp-z220-06 virt-who.d]# virt-who --one-shot --satellite --satellite-server=10.66.128.4 --satellite-username=virtwho_test --satellite-password=redhat123 --rhevm --rhevm-server=https://10.66.79.58:443 --rhevm-username=admin@internal --rhevm-password=redhat
2015-04-13 11:36:47,909 INFO: Using configuration "env/cmdline" ("rhevm" mode)
2015-04-13 11:36:48,222 INFO: Initialized satellite connection
2015-04-13 11:36:48,222 INFO: Sending update in hosts-to-guests mapping: {'cb70a094-6ab8-4c15-8f52-d557f4f7ef83': [], '7691fd80-6f02-45e5-a83c-d38e01cfcbf7': ['9e73efbb-fbee-4212-8b2b-b81dedf061e9', '2d78eb42-d66b-46a6-a52c-c43eb9fb8af8']}

Result: virt-who can send host/guest mapping to satellite, therefore, verify it.
Comment 7 errata-xmlrpc 2015-07-22 07:15:48 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-1377.html
Note You need to log in before you can comment on or make changes to this bug.