Bug 1831825 - Cannot use the same NetworkAttachmentDefinition multiple times on a single VM
Summary: Cannot use the same NetworkAttachmentDefinition multiple times on a single VM
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.0
Assignee: Phillip Bailey
QA Contact: Radim Hrazdil
Depends On:
TreeView+ depends on / blocked
Reported: 2020-05-05 17:28 UTC by Petr Horáček
Modified: 2020-07-13 17:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-07-13 17:35:12 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 5463 0 None closed Bug 1831825: Allow reuse of NADs in NIC creation modal 2020-06-24 01:43:49 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:35:32 UTC

Description Petr Horáček 2020-05-05 17:28:02 UTC
Description of problem:
The VirtualMachine wizard does not allow me to use single NetworkAttachmentDefinition multiple times. Since the NetworkAttachmentDefinition does not represent a single interface, but rather a "method" how to connect to a network, it should be a valid option to reuse it multiple times.

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

How reproducible:

Steps to Reproduce:
1. Create NetworkAttachmentDefinition via the wizard
2. Attach it to a VM in the VM wizard
3. Try to attach it again as a different interface

Actual results:
The NetworkAttachmentDefinition is not listed in available definitions anymore

Expected results:
It should be possible to use the same NetworkAttachmentDefinition multiple times.

Comment 3 Radim Hrazdil 2020-05-20 06:03:44 UTC
Verified that multiple NICs can be added using one NetworkAttachmentDefinition.

Comment 4 errata-xmlrpc 2020-07-13 17:35:12 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.


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