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.
Description of problem:
The customer is not able to use virt-who with Nutanix as virt-who always reports the same VM's as the filter with the Nutanix REST API v3 seems not get applied
Version-Release number of selected component (if applicable):
Satellite 6.10.5
How reproducible:
always
The customer discovered the following:
The function make_rest_call in ahv_interface.py (https://github.com/candlepin/virt-who/blob/main/virtwho/virt/ahv/ahv_interface.py) doesn't apply the filter length and offset correctly. So virt-who always asks the Prism Central API for the first 20 vms over and over again - by totally forgetting every above that value. Because of that, RHEL installations on AHV hosts are not possible, even if they are licensed correctly.
Actual results:
RHEL installations on AHV hosts are not possible, even if they are licensed correctly.
Expected results:
Correct count of hosts returned
Additional info:
The customer created an MR on github for the upstream project. Maybe we can backport this when it is merged:
https://github.com/candlepin/virt-who/pull/376
(In reply to Oliver Ilian from comment #0)
> Description of problem:
> The customer is not able to use virt-who with Nutanix as virt-who always
> reports the same VM's as the filter with the Nutanix REST API v3 seems not
> get applied
>
> Version-Release number of selected component (if applicable):
> Satellite 6.10.5
>
> How reproducible:
> always
>
> The customer discovered the following:
> The function make_rest_call in ahv_interface.py
> (https://github.com/candlepin/virt-who/blob/main/virtwho/virt/ahv/
> ahv_interface.py) doesn't apply the filter length and offset correctly. So
> virt-who always asks the Prism Central API for the first 20 vms over and
> over again - by totally forgetting every above that value. Because of that,
> RHEL installations on AHV hosts are not possible, even if they are licensed
> correctly.
>
> Actual results:
> RHEL installations on AHV hosts are not possible, even if they are licensed
> correctly.
>
> Expected results:
> Correct count of hosts returned
>
> Additional info:
> The customer created an MR on github for the upstream project. Maybe we can
> backport this when it is merged:
> https://github.com/candlepin/virt-who/pull/376
Hi Oliver,
Thanks for reporting the bug. Can you please share the following details to helps us plan/target the fix correctly,
1. Please share the virt-who version
2. Please share the RHEL version of the system being used
Thanks,
Rehana
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 (virt-who bug fix and enhancement update), 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-2023:2747