Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionWaldirio M Pinheiro
2018-02-01 12:04:56 UTC
Description of problem:
Customer with RHEL6+Virt-who installed works fine on RHV 3.x, after upgrade to RHV-4.x stop.
Version-Release number of selected component (if applicable):
virt-who-0.18-6.el6_9.noarch
How reproducible:
100%
Steps to Reproduce:
1. Install virt-who on rhel6 machine, the latest version available will be virt-who-0.18-6.el6_9.noarch
2. Configure the conf file according our official docs
3. Execute the command virt-who -d -o
Actual results:
Error according below
---
2018-02-01 00:28:24,421 [virtwho.dc_rhv_01 ERROR] RhevM-1(3174):MainThread @virt.py:run:374 - Virt backend 'dc_rhv_01' fails with error: Unable to connect to RHEV-M server: 404 Client Error: Not Found
---
Expected results:
Collect all information from Manager related to the hypervisors and guests
---
...
2018-02-01 00:30:12,049 [virtwho.main INFO] MainProcess(3191):MainThread @subscriptionmanager.py:hypervisorCheckIn:195 - Sending update in hosts-to-guests mapping for config "dc_rhv_01": 2 hypervisors and 0 guests found
...
---
Additional info:
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://access.redhat.com/errata/RHBA-2018:1915