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 1205520 - virt-who uses wrong server when connecting to satellite
Summary: virt-who uses wrong server when connecting to satellite
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-who
Version: 6.7
Hardware: All
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: Radek Novacek
QA Contact: gaoshang
URL:
Whiteboard:
Depends On: 1199397
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-25 06:15 UTC by Jan Kurik
Modified: 2019-09-12 08:19 UTC (History)
14 users (show)

Fixed In Version: virt-who-0.10-8.el6_6.3
Doc Type: Bug Fix
Doc Text:
Previously, virt-who used the value of the "--esx-server" command-line option instead of the "--satellite-server" option value. As a consequence, virt-who attempted to report a host-guest association to the ESX server instead of satellite, and thus failed. With this update, "--satellite-server" works as intended, and virt-who uses the correct server when connecting to Red Hat Satellite.
Clone Of: 1199397
Environment:
Last Closed: 2015-04-21 08:34:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0859 0 normal SHIPPED_LIVE virt-who bug fix update 2015-04-21 12:33:50 UTC

Description Jan Kurik 2015-03-25 06:15:53 UTC 
This bug has been copied from bug #1199397 and has been proposed
to be backported to 6.6 z-stream (EUS).
Comment 3 Radek Novacek 2015-03-26 14:44:16 UTC 
Fixed by virt-who-0.10-8.el6_6.3.
Comment 5 Liushihui 2015-03-27 06:20:12 UTC 
Verified it on virt-who-0.10-8.el6_6.3.

Verified version:
Satellite-5.7.0-RHEL6-re20150108.2-x86_64
virt-who-0.10-8.el6_6.3.noarch
subscription-manager-1.12.14-7.el6.x86_64

Verified process:
1. Update virt-who to virt-who-0.10-8.el6_6.3
[root@hp-z220-06 ~]# rpm -Uvh virt-who-0.10-8.el6_6.3.noarch.rpm 
Preparing...                ########################################### [100%]
   1:virt-who               ########################################### [100%]
2. Register rhel to Satellite-5.7
3. Run virt-who, virt-who has send host/guest associate to satellite
[root@hp-z220-06 rhn]# virt-who -d -o --satellite --satellite-server=10.66.128.4 --satellite-username=test --satellite-password=redhat --esx --esx-owner=lsh_org --esx-env=Library --esx-server=https://10.66.79.68:443 --esx-username=administrator --esx-password=qwer1234P!
INFO: Using virt-who configuration: virt-who
DEBUG: Initializing satellite connection to https://10.66.128.4/XMLRPC
INFO: Initialized satellite connection
INFO: Sending update in hosts-to-guests mapping: {564d20f4-71b7-acdb-f875-d64ecec4a6c0: [4226082e-2746-17dc-6f01-dc91c6fc7fbb, 42248226-68fb-a3e1-dce1-0e264e7a37d1]}
DEBUG: Loading systemid for 564d20f4-71b7-acdb-f875-d64ecec4a6c0
DEBUG: Loading system id info from /var/lib/virt-who/hypervisor-systemid-564d20f4-71b7-acdb-f875-d64ecec4a6c0
DEBUG: New system created in satellite, system id saved in /var/lib/virt-who/hypervisor-systemid-564d20f4-71b7-acdb-f875-d64ecec4a6c0
DEBUG: Building plan for hypervisor 564d20f4-71b7-acdb-f875-d64ecec4a6c0: [4226082e-2746-17dc-6f01-dc91c6fc7fbb, 42248226-68fb-a3e1-dce1-0e264e7a37d1]
DEBUG: Sending plan: [[0, 'exists', 'system', {'uuid': '0000000000000000', 'identity': 'host'}], [0, 'crawl_began', 'system', {}], [0, 'exists', 'domain', {'state': 'running', 'memory_size': 0, 'name': u'VM from esx hypervisor 564d20f4-71b7-acdb-f875-d64ecec4a6c0', 'virt_type': 'fully_virtualized', 'vcpus': 1, 'uuid': '4226082e274617dc6f01dc91c6fc7fbb'}], [0, 'exists', 'domain', {'state': 'running', 'memory_size': 0, 'name': u'VM from esx hypervisor 564d20f4-71b7-acdb-f875-d64ecec4a6c0', 'virt_type': 'fully_virtualized', 'vcpus': 1, 'uuid': '4224822668fba3e1dce10e264e7a37d1'}], [0, 'crawl_ended', 'system', {}]]
4.IN the satellite web UI, Go to system, esx hypervisor can show on it. Therefore, verify it .
Comment 8 errata-xmlrpc 2015-04-21 08:34:10 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-0859.html
Note You need to log in before you can comment on or make changes to this bug.