Bug 1687917 - Cannot add NIC to template on Network Interfaces page as no NADs are listed even when exist
Summary: Cannot add NIC to template on Network Interfaces page as no NADs are listed e...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.0
Assignee: Yaacov Zamir
QA Contact: Radim Hrazdil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-12 16:08 UTC by Radim Hrazdil
Modified: 2019-07-24 20:16 UTC (History)
5 users (show)

Fixed In Version: 2.0.0-9.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-24 20:15:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1850 0 None None None 2019-07-24 20:15:59 UTC

Description Radim Hrazdil 2019-03-12 16:08:37 UTC
Description of problem:
Cannot add NIC to template on Network Interfaces page as when Add NIC button is clicked, no NADs are provided even when there is an existing NAD.

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


How reproducible:
100%

Steps to Reproduce:
1.Create a networkAttachmentDefinition:
cat <<EOF | kubectl create -f -
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
  name: ovs-net-1
spec:
  config: '{
      "cniVersion": "0.3.1",
      "type": "ovs",
      "bridge": "br0"
    }'
EOF

2. Create a template and go to its 'Network Interfaces' tab. Try to add new NIC
3. Network cannot be configured because the dropdown doesn't provide the existing NAD

Actual results:


Expected results:


Additional info:
I double checked that the added NAD is listed in VM wizard and NIC can be added there.

Comment 3 Radim Hrazdil 2019-04-24 12:19:32 UTC
Verified with version v2.0.0-13. Network can be selected on template NICs tab.

Comment 5 errata-xmlrpc 2019-07-24 20:15:51 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/RHEA-2019:1850


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