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 1086517 - virt-who failed when testing against Satellite 5.6 due to missing folder /var/lib/virt-who in RHEL 7
Summary: virt-who failed when testing against Satellite 5.6 due to missing folder /var...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Radek Novacek
QA Contact: Li Bin Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-11 04:00 UTC by gaoshang
Modified: 2016-12-01 00:32 UTC (History)
5 users (show)

Fixed In Version: virt-who-0.11-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 10:23:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0430 0 normal SHIPPED_LIVE Moderate: virt-who security, bug fix, and enhancement update 2015-03-05 14:52:46 UTC

Description gaoshang 2014-04-11 04:00:38 UTC 
Description of problem:
In RHEL 7, /var/lib/virt-who not exist by default, it will cause error(see [1]) when writing hypervisor-systemid, after manually created above folder, this bug can be work around.

Version-Release number of selected component (if applicable):
# rpm -qa | grep virt-who
virt-who-0.8-12.el7.noarch
# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.0 (Maipo)

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
[1]
2014-04-11 11:51:10,312 [WARNING]  @virt-who.py:515 - Listening for events is not available in VDSM, ESX, RHEV-M or Hyper-V mode
2014-04-11 11:51:26,648 [ERROR]  @satellite.py:81 - Unable to write system id to /var/lib/virt-who/hypervisor-systemid-44454c4c-4200-1034-8039-b8c04f503258: [Errno 2] No such file or directory: u'/var/lib/virt-who/hypervisor-systemid-44454c4c-4200-1034-8039-b8c04f503258'

Expected results:


Additional info:
Though failed, virt-who did created a esx hypervisor in Satellite, but no guest in it.
Comment 2 RHEL Program Management 2014-04-19 05:47:46 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.
Comment 3 Radek Novacek 2014-09-11 10:45:37 UTC 
This has been fixed by rebase to virt-who-0.11-1.el7, see bug 1122489.
Comment 5 xingge 2014-11-24 07:22:35 UTC 
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?
Comment 6 Liushihui 2015-01-04 03:45:54 UTC 
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
Comment 8 errata-xmlrpc 2015-03-05 10:23:12 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/RHSA-2015-0430.html
Note You need to log in before you can comment on or make changes to this bug.