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.

Currently, if we want to run kubevirt mode for virt-who, we have to install python-kubernetes and python-kubevirt packages in virt-who host, this will bring a lot of dependencies to virt-who, virt-who should not depend on the hypervisor's sdk.

Is it possible that virt-who connects kubevirt environment without the third-party packages, just like other hypervisors by API or some other protocol.

Thanks.

Given that the implementation depends on those libraries, and replacing them would essentially mean re-implementing, and we are not going to re-implement.

I will change the status to NEW and hope more discussion.

*** Bug 1684497 has been marked as a duplicate of this bug. ***

Tested it against the upstream master, seems that we are not passing the auth headers, so hit the 403 error again.

Also, on_qa should be put when we've the new rpm to consume.

Since this issue determines how to design our test cases for kubevirt mode, I'd like to change the severity to urgent.

Actually d/s is not ready for verification so moving to modified.

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-2019:2070