Red Hat Bugzilla – Bug 1288034
Chapter 6 regarding virt-who contains deprecated configuration instructions
Last modified: 2016-06-16 00:21:27 EDT
Section Number and Name:
Chapter 6. Managing Hypervisors and Virtual Guest Subscriptions
Describe the issue:
This chapter contains some information that is not correct (confirmed with virt-who 0.14):
6.2.1 - Prerequisites
"The system running virt-who is registered already to the Satellite server(virt-who will use the host credentials)."
This is not correct anymore. virt-who can be run on a system that isn't registered to the Satellite. It can also run on the Satellite itself even if it is not self-registered.
6.2.3 - virt-who Configuration File Location
"The virt-who configuration is stored in the following configuration files: /etc/sysconfig/virt-who (default)"
The configuration should be done in configuration files in /etc/virt-who.d/ instead of /etc/sysconfig/virt-who (it even says so in that file).
6.4, 6.5, 6.6 are using /etc/sysconfig/virt-who for configuration.
Suggestions for improvement:
The prerequisites should clearly state that virt-who can run on any system regardless if it is registered to the Satellite or if it is virtual/physical.
There should be configuration examples using files in /etc/virt-who.d/ instead of /etc/sysconfig/virt-who.
I think it should be some information about running virt-who on the Satellite itself (self-registered or not, physical or virtual) since that is now possible.
I've successfully run virt-who 0.14 on a physical Satellite 6.1.4 that was not self-registered against vCenter and RHEV with the following configurations:
# cat /etc/virt-who.d/esx.conf
# cat /etc/virt-who.d/rhevm.conf
Assigning to Russell for review.
I believe the requirements specified in this BZ ticket will be met by the Satellite 6.2 "Virtual Instances Guide", which is available for the Beta at .
Please review the guide and confirm whether or not it delivers what you had requested.
I miss the part regarding how to configure virt-who to report to a Satellite that is not self registered. Chapter 5.3 through 5.5 contains good examples of configurations for esx, hyper-v and rhevm but all of these examples assumes that the Satellite is self registered. The following lines from the config example in this BZ would be needed if the Satellite is not self registered (if I'm not mistaken):
# or with encrypted password
rhsm_encrypted_password=<encrypted satellite password>
This content is now live on the Customer Portal.