Bug 1714130 - No need for kubevirt to config Hypervisor Server
Summary: No need for kubevirt to config Hypervisor Server
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Virt-who Configure Plugin
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.6.0
Assignee: Marek Hulan
QA Contact: Kunxin Huang
satellite-doc-list
URL:
Whiteboard:
Depends On: 1745944
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-27 08:03 UTC by Kunxin Huang
Modified: 2019-12-17 11:35 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-foreman_virt_who_configure-0.4.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:51:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27379 0 Normal Closed No need for kubevirt to config Hypervisor Server 2020-07-09 16:01:18 UTC

Description Kunxin Huang 2019-05-27 08:03:17 UTC
Created attachment 1573806 [details]
The current UI of kubevirt

Description of problem:

Input the path of the configuration file to 'Path to kubeconfig file' option, no matter what we input to the 'Hypervisor Server', the virt-who-configure plugin can be deployed successfully and send the mapping info.

And the kubeconfig file has the necessary info about master, server, and token, there is no need for kubevirt to config 'Hypervisor Server'



Additional info:

The current UI of kubevirt see attachment kubeconfig.png
The content of kubeconfig see attachment kube.conf

Comment 3 Marek Hulan 2019-07-23 06:33:29 UTC
Created redmine issue https://projects.theforeman.org/issues/27379 from this bug

Comment 7 Bryan Kearney 2019-10-22 19:51:35 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-2019:3172


Note You need to log in before you can comment on or make changes to this bug.