- Issued:
- 2020-09-29
- Updated:
- 2020-09-29
RHBA-2020:3865 - Bug Fix Advisory
Synopsis
virt-who bug fix update
Type/Severity
Bug Fix Advisory
Red Hat Insights patch analysis
Identify and remediate systems affected by this 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.9 Release Notes linked from the References section.
Users of virt-who are advised to upgrade to these updated packages.
Solution
Before applying this update, make sure all previously released errata
relevant to your system have been applied.
For details on how to apply this update, refer to:
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 - 1409984 - Failed to get mapping info from vcenter6.5 when there isn't host on it
- BZ - 1448343 - It shows "The session is not authenticated" when stop virt-who for esx mode.
- BZ - 1450738 - It displays exception info to rhsm log when run virt-who with wrong rhsm_hostname/rhsm_port
- BZ - 1751441 - [Kubevirt] Failed to run virt-who in kubevirt mode by cli due to kubeconfig option not set
- BZ - 1760161 - -m, -l, -f and -r arguments are not in virt-who man page
- BZ - 1762780 - When "reporter_id=" is empty, it doesn't use default "HOSTNAME-MACHINEID"
- BZ - 1775535 - [Kubevirt/CNV] Failed to run virt-who in Openshift-4.2 with CNV-2.1
- BZ - 1780467 - [RHEVM] Allow unicode characters in password
- BZ - 1806572 - virt-who using V3 APIs for communication with RHEVM which is deprecated
- BZ - 1809098 - Convert first 3 fields of UUID reported by VMware HW to match the OS UUID
- BZ - 1825843 - virt-who is connecting too much and eating cpu time
- BZ - 1835132 - [CNV2.4] Virt-who is failed to send host-to-guest mapping to subscription server
- BZ - 1844364 - If run virt-who with a bad configuration file, virt-who should fail to start.
CVEs
(none)
References
(none)
Red Hat Enterprise Linux Server 7
SRPM | |
---|---|
virt-who-0.28.9-1.el7.src.rpm | SHA-256: cb5b2ac6738ad07521753904efed55849a628b4a89a3ab557880a04cff1edefa |
x86_64 | |
virt-who-0.28.9-1.el7.noarch.rpm | SHA-256: 7dd66903b8296d43c622464926523720d33ba0e0f76a55522ba9985f04db0442 |
Red Hat Enterprise Linux Server - Extended Life Cycle Support 7
SRPM | |
---|---|
virt-who-0.28.9-1.el7.src.rpm | SHA-256: cb5b2ac6738ad07521753904efed55849a628b4a89a3ab557880a04cff1edefa |
x86_64 | |
virt-who-0.28.9-1.el7.noarch.rpm | SHA-256: 7dd66903b8296d43c622464926523720d33ba0e0f76a55522ba9985f04db0442 |
Red Hat Enterprise Linux Workstation 7
SRPM | |
---|---|
virt-who-0.28.9-1.el7.src.rpm | SHA-256: cb5b2ac6738ad07521753904efed55849a628b4a89a3ab557880a04cff1edefa |
x86_64 | |
virt-who-0.28.9-1.el7.noarch.rpm | SHA-256: 7dd66903b8296d43c622464926523720d33ba0e0f76a55522ba9985f04db0442 |
Red Hat Enterprise Linux Desktop 7
SRPM | |
---|---|
virt-who-0.28.9-1.el7.src.rpm | SHA-256: cb5b2ac6738ad07521753904efed55849a628b4a89a3ab557880a04cff1edefa |
x86_64 | |
virt-who-0.28.9-1.el7.noarch.rpm | SHA-256: 7dd66903b8296d43c622464926523720d33ba0e0f76a55522ba9985f04db0442 |
Red Hat Enterprise Linux for IBM z Systems 7
SRPM | |
---|---|
virt-who-0.28.9-1.el7.src.rpm | SHA-256: cb5b2ac6738ad07521753904efed55849a628b4a89a3ab557880a04cff1edefa |
s390x | |
virt-who-0.28.9-1.el7.noarch.rpm | SHA-256: 7dd66903b8296d43c622464926523720d33ba0e0f76a55522ba9985f04db0442 |
Red Hat Enterprise Linux for Power, big endian 7
SRPM | |
---|---|
virt-who-0.28.9-1.el7.src.rpm | SHA-256: cb5b2ac6738ad07521753904efed55849a628b4a89a3ab557880a04cff1edefa |
ppc64 | |
virt-who-0.28.9-1.el7.noarch.rpm | SHA-256: 7dd66903b8296d43c622464926523720d33ba0e0f76a55522ba9985f04db0442 |
Red Hat Enterprise Linux for Power, little endian 7
SRPM | |
---|---|
virt-who-0.28.9-1.el7.src.rpm | SHA-256: cb5b2ac6738ad07521753904efed55849a628b4a89a3ab557880a04cff1edefa |
ppc64le | |
virt-who-0.28.9-1.el7.noarch.rpm | SHA-256: 7dd66903b8296d43c622464926523720d33ba0e0f76a55522ba9985f04db0442 |
Red Hat Enterprise Linux Server - Extended Life Cycle Support (for IBM z Systems) 7
SRPM | |
---|---|
virt-who-0.28.9-1.el7.src.rpm | SHA-256: cb5b2ac6738ad07521753904efed55849a628b4a89a3ab557880a04cff1edefa |
s390x | |
virt-who-0.28.9-1.el7.noarch.rpm | SHA-256: 7dd66903b8296d43c622464926523720d33ba0e0f76a55522ba9985f04db0442 |
Red Hat Enterprise Linux Server - Extended Life Cycle Support for IBM Power, big endian 7
SRPM | |
---|---|
virt-who-0.28.9-1.el7.src.rpm | SHA-256: cb5b2ac6738ad07521753904efed55849a628b4a89a3ab557880a04cff1edefa |
ppc64 | |
virt-who-0.28.9-1.el7.noarch.rpm | SHA-256: 7dd66903b8296d43c622464926523720d33ba0e0f76a55522ba9985f04db0442 |
Red Hat Enterprise Linux Server - Extended Life Cycle Support for IBM Power, little endian 7
SRPM | |
---|---|
virt-who-0.28.9-1.el7.src.rpm | SHA-256: cb5b2ac6738ad07521753904efed55849a628b4a89a3ab557880a04cff1edefa |
ppc64le | |
virt-who-0.28.9-1.el7.noarch.rpm | SHA-256: 7dd66903b8296d43c622464926523720d33ba0e0f76a55522ba9985f04db0442 |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.