Bug 1700776 - [Kubevirt-Foreman] Default pod network not visible anymore
Summary: [Kubevirt-Foreman] Default pod network not visible anymore
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - CNV
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.6.0
Assignee: Moti Asayag
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-17 11:10 UTC by Vatsal Parekh
Modified: 2019-10-22 19:51 UTC (History)
2 users (show)

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github masayag foreman_kubevirt pull 79 0 None None None 2019-04-22 14:01:59 UTC

Description Vatsal Parekh 2019-04-17 11:10:34 UTC
Description of problem:
On current plugin master seeing a regression that there is a pod CNV provider is shown but no default network option shown with it. So making it only ovs option available.

Version-Release number of selected component (if applicable):
plugin master

How reproducible:


Steps to Reproduce:
1.Go to create a host with pod network in interface 
2.
3.

Actual results:
No option for Pod network

Expected results:
Should not show any network choices if Pod was selected as CNI

Additional info:

Comment 3 Moti Asayag 2019-04-22 14:01:59 UTC
Instead of 'default' network, when selecting 'POD' as the network provider, the list of networks will be hidden.

Comment 4 Lukáš Hellebrandt 2019-07-31 14:07:52 UTC
Verified with Sat 6.6 snap 13.

1. Have a Sat with Kubevirt as CR
2. Hosts -> Create host
3. Deploy on = <Kubevirt_instance>
4. Interfaces tab
5. CNI provider = Pod

=> Pod selectable, Network field hidden after that, VM created after filling the rest of the form and submitting

Comment 5 Bryan Kearney 2019-10-22 19:51:50 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.