RHBA-2019:2070 - Bug Fix Advisory

Topic

An update for virt-who is now available for Red Hat Enterprise Linux 7.

Description

The virt-who service collects information about the connection between the hypervisor and its virtual guests that are present in the system and provides the subscription manager with a mapping file containing the hypervisor-guest pairs. The service periodically queries the hypervisor to report its guests and changes the mapping file accordingly, making sure that the information stored in the subscription manager is accurate.

For detailed information on changes in this release, see the Red Hat Enterprise Linux 7.7 Release Notes linked from the References section.

Users of virt-who are advised to upgrade to these updated packages.

Solution

For details on how to apply this update, refer to:

https://access.redhat.com/articles/11258

Affected Products

• Red Hat Enterprise Linux Server 7 x86_64
• Red Hat Enterprise Linux Server - Extended Life Cycle Support 7 x86_64
• Red Hat Enterprise Linux Workstation 7 x86_64
• Red Hat Enterprise Linux Desktop 7 x86_64
• Red Hat Enterprise Linux for IBM z Systems 7 s390x
• Red Hat Enterprise Linux for Power, big endian 7 ppc64
• Red Hat Enterprise Linux for Power, little endian 7 ppc64le
• Red Hat Enterprise Linux Server - Extended Life Cycle Support (for IBM z Systems) 7 s390x
• Red Hat Enterprise Linux Server - Extended Life Cycle Support for IBM Power, big endian 7 ppc64
• Red Hat Enterprise Linux Server - Extended Life Cycle Support for IBM Power, little endian 7 ppc64le

Fixes

• BZ - 1369634 - It will show error page's html code in log when virt-who received "Invalid response (403) from Hyper-V"
• BZ - 1377247 - Most options in /etc/virt-who.conf are not available
• BZ - 1410600 - [RFE] virt-who need to make sure there is only one entry in satellite content host for the same hypervisor when configure hypervisor_id for uuid or hostname or hwuuid
• BZ - 1445160 - When owner/env option is missing in config file(s) an error message should be displayed
• BZ - 1472727 - Virt-who fail to start when configured only one hypervisor with encrypted password but no key file in '/var/lib/virt-who/'
• BZ - 1486270 - [RFE] Add no_proxy setting in /etc/virt-who.conf
• BZ - 1506167 - Virt-who process is killed after run command "subscription-manager unregister ; subscription-manager clean"
• BZ - 1519704 - When configure interval<60s, it should be better to give reminder info - "Interval value can't be lower than 60 seconds. Default value of 3600 seconds will be used."
• BZ - 1522384 - No global option "print_" exists, but it always prints warning info about the option not set.
• BZ - 1522661 - "is_hypervisor" option is only for fake mode, but it always prints warning info about the option is not set when run virt-who in non-fake mode.
• BZ - 1523482 - Failed to report mappings if configure "interval=" value to null in /etc/virt-who.conf.
• BZ - 1530290 - When "env" option is disabled or null value, some test results are not expected.
• BZ - 1557296 - virt-who does not ignore commented out lines that are prefixed with tab space
• BZ - 1581021 - "UnicodeDecodeError" occurs when run virt-who in HYPERV mode with account password containing Unicode characters.
• BZ - 1591525 - Customer would like to enable/disable warning on the RHSM log file
• BZ - 1622812 - No other options for kubevirt mode in /etc/sysconfig/virt-who besides "VIRTWHO_KUBEVIRT="
• BZ - 1622971 - No module named kubernetes or kubevirt when testing in kubevirt mode
• BZ - 1631013 - Rebase virt-who component to the latest upstream branch for RHEL 7.7
• BZ - 1656265 - [RFE] make virt-who access kubevirt environment by API or other remote protocol.
• BZ - 1667522 - Offline hypervisor on ESX are not skipped by virt-who if 'hypervisor_id' is set as 'uuid' causing virt-who one shot to fail.
• BZ - 1684478 - [kubevirt] virt-who fails incorrectly even if the config file given
• BZ - 1684499 - [kubevirt] virt-who fails with APIException error
• BZ - 1693858 - Include system uuid with all hypervisor reports for additional fabrics
• BZ - 1695519 - Failed to create host-to-guest association in server webui for kubevirt
• BZ - 1695538 - hypervisor_id option doesn't take effect when run virt-who in kubevirt mode
• BZ - 1698359 - Inefficient WQL is used to get Hyper-V version caused virt-who connection timeout.
• BZ - 1708524 - [Kubevirt] There should be special introduction for kubevirt mode in virt-who-config man page
• BZ - 1708534 - [Kubevirt] Add "kubeconfig=" option and introduce for kubevirt in /etc/virt-who.d/template.conf
• BZ - 1714091 - When 'is_hypervisor' option is not configured for fake mode, if should give warning log.
• BZ - 1718304 - virt-who connected to a HyperV fails with "NoneType object has no attribute __getitem__" in decodeWinUUID

CVEs

(none)

References

• https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/7.7_release_notes/index