Bug 1734776

Summary:	Kubevirt related fields missing in API, Hammer
Product:	Red Hat Satellite	Reporter:	Lukáš Hellebrandt <lhellebr>
Component:	Compute Resources - CNV	Assignee:	Shira Maximov <mshira>
Status:	CLOSED ERRATA	QA Contact:	Vladimír Sedmík <vsedmik>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.6.0	CC:	egolov, pkliczew, vsedmik
Target Milestone:	6.7.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_kubevirt-0.1.5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-14 13:25:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1728655

Description Lukáš Hellebrandt 2019-07-31 12:10:30 UTC

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

Comment 3 Shira Maximov 2019-08-01 10:02:02 UTC

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

Comment 4 Bryan Kearney 2019-08-11 14:01:56 UTC

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

Comment 8 errata-xmlrpc 2020-04-14 13:25:08 UTC

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