Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1831825

Summary:	Cannot use the same NetworkAttachmentDefinition multiple times on a single VM
Product:	OpenShift Container Platform	Reporter:	Petr Horáček <phoracek>
Component:	Console Kubevirt Plugin	Assignee:	Phillip Bailey <phbailey>
Status:	CLOSED ERRATA	QA Contact:	Radim Hrazdil <rhrazdil>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.5	CC:	aos-bugs, phbailey, rhrazdil, yzamir
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:35:12 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:

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:
Always


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.

https://access.redhat.com/errata/RHBA-2020:2409