Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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:
When creating a new host in Kubevirt CR, the operation fails with error and traceback. Happens for both network based and image based provisioning.

The error in WebUI is:
"""
Unable to save
Failed to create a compute kubevirt4 (KubeVirt) instance tommy-grosser.lab.eng.rdu2.redhat.com: undefined method `create_virtual_machine' for #<Fog::Kubevirt::Utils::ExceptionWrapper:0x00007f35165ea3b0> 
"""

Traceback attached.

Version-Release number of selected component (if applicable):
Sat 6.6 snap 17, kubevirt 4.2. Regression from some previous snap.

How reproducible:
Deterministic

Steps to Reproduce:
1. Have a Satellite, have a Kubevirt instance added as a CR in the Satellite, have other necessary entities such as domain, subnet...
2. Hosts -> Create host
3. Deploy on Kubevirt, fill necessary fields
4. Submit

Actual results:
Error, traceback, no VM created

Expected results:
VM created successfully, no error, no traceback

Additional info:

Created attachment 1609003 [details]
foreman-tail

I'm closing the BZ since This Bug is Kubevirt API bug,
this is the fix for the bug: https://github.com/kubernetes/kubernetes/pull/79495 
and it should be available in the lastest kubevirt version (0.20.1)