Bug 1086517
| Summary: | virt-who failed when testing against Satellite 5.6 due to missing folder /var/lib/virt-who in RHEL 7 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | gaoshang <sgao> |
| Component: | virt-who | Assignee: | Radek Novacek <rnovacek> |
| Status: | CLOSED ERRATA | QA Contact: | Li Bin Liu <liliu> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 | CC: | djuran, gxing, liliu, ovasik, shihliu |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-who-0.11-1.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-03-05 10:23:12 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
gaoshang
2014-04-11 04:00:38 UTC
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. This has been fixed by rebase to virt-who-0.11-1.el7, see bug 1122489. We now handling this bug, but we did have a useable Satellite server, and we learning to install the server. Can someone give us a useable satellite server so that we can verify the bug? Verify it on virt-who-0.11-5.el7.noarch Version-Release number of selected component (if applicable): [root@hp-z220-04 virt-who]# rpm -q virt-who virt-who-0.11-5.el7.noarch Verify process: 1.Register to satellite5.6 2.Configure virt-who run at esx mode: # cat /etc/sysconfig/virt-who VIRTWHO_DEBUG=1 VIRTWHO_BACKGROUND=1 VIRTWHO_INTERVAL=10 VIRTWHO_SATELLITE=1 VIRTWHO_ESX=1 VIRTWHO_ESX_OWNER=ACME_Corporation VIRTWHO_ESX_ENV=Library VIRTWHO_ESX_SERVER=10.66.78.75 VIRTWHO_ESX_USERNAME=Administrator VIRTWHO_ESX_PASSWORD=qwer1234P! VIRTWHO_SATELLITE_SERVER=http://10.66.128.29/XMLRPC VIRTWHO_SATELLITE_USERNAME=admin VIRTWHO_SATELLITE_PASSWORD=admin # service virt-who restart 3.Check the hypervisor uuid [root@hp-z220-04 virt-who]# cd /var/lib/virt-who [root@hp-z220-04 virt-who]# ls hypervisor-systemid-aee4ff00-8c33-11e2-994a-6c3be51d959a 4.Check the virt-who's log, virt-who has send esx hypervisor to satellite 5.6 2015-01-04 11:20:55,224 [INFO] @virtwho.py:458 - Using commandline or sysconfig configuration ("esx" mode) 2015-01-04 11:20:55,224 [DEBUG] @virtwho.py:170 - Starting infinite loop with 10 seconds interval 2015-01-04 11:21:00,314 [DEBUG] @satellite.py:60 - Initializing satellite connection to http://10.66.128.29/XMLRPC 2015-01-04 11:21:00,314 [INFO] @satellite.py:66 - Initialized satellite connection 2015-01-04 11:21:00,314 [INFO] @satellite.py:147 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [42384307-e2fb-97f1-700a-2e71043a7202]} 2015-01-04 11:21:00,314 [DEBUG] @satellite.py:152 - Loading systemid for aee4ff00-8c33-11e2-994a-6c3be51d959a 2015-01-04 11:21:00,315 [DEBUG] @satellite.py:74 - Loading system id info from /var/lib/virt-who/hypervisor-systemid-aee4ff00-8c33-11e2-994a-6c3be51d959a 2015-01-04 11:21:00,315 [DEBUG] @satellite.py:155 - Building plan for hypervisor aee4ff00-8c33-11e2-994a-6c3be51d959a: [42384307-e2fb-97f1-700a-2e71043a7202] 2015-01-04 11:21:00,315 [DEBUG] @satellite.py:159 - 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 aee4ff00-8c33-11e2-994a-6c3be51d959a', 'virt_type': 'fully_virtualized', 'vcpus': 1, 'uuid': '42384307e2fb97f1700a2e71043a7202'}], [0, 'crawl_ended', 'system', {}]] 5. Register esx's guest to satellite 5.6, it also can show on satellite 5.6 web UI 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/RHSA-2015-0430.html |