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:
The only mention of Kubevirt in API and Hammer is in --provider list of options (regardless of whether foreman-clu-kubevirt plugin is installed). There are no ways to specify token, namespace etc.

Version-Release number of selected component (if applicable):
Reproduced on Sat 6.6 snap 13.

How reproducible:
Deterministic

Steps to Reproduce:
1. Look at https://${SAT_FQDN}/apidoc/v2/compute_resources/create.html
2. hammer compute-resource create --help | grep Kubevirt

Actual results:
No mention of Kubevirt specific fields. Installing or uninstalling foreman-cli-kubevirt doesn't change anything.

Expected results:
Kubevirt mentioned only with plugin installed, kubevirt CR addable, correctly documented in API doc and Hammer's help

Created redmine issue https://projects.theforeman.org/issues/27492 from this bug

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27492 has been resolved.

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/RHSA-2020:1454