Bug 1205520
| Summary: | virt-who uses wrong server when connecting to satellite | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Kurik <jkurik> |
| Component: | virt-who | Assignee: | Radek Novacek <rnovacek> |
| Status: | CLOSED ERRATA | QA Contact: | gaoshang <sgao> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.7 | CC: | ahumbe, cww, ekin.meroglu, gxing, jsvarova, liliu, matthew.lesieur, mfuruta, ovasik, pm-eus, pwayper, rbalakri, rnovacek, shihliu |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 1199397 | Environment: | |
| Last Closed: | 2015-04-21 08:34:10 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1199397 | ||
| Bug Blocks: | |||
|
Description
Jan Kurik
2015-03-25 06:15:53 UTC
Fixed by virt-who-0.10-8.el6_6.3. 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 . 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 |