Bug 1840766

Summary:	cannot create VM with disks again with the same name
Product:	OpenShift Container Platform	Reporter:	Filip Krepinsky <fkrepins>
Component:	Console Kubevirt Plugin	Assignee:	Phillip Bailey <phbailey>
Status:	CLOSED ERRATA	QA Contact:	Guohua Ouyang <gouyang>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.5	CC:	aos-bugs, gouyang, phbailey, spadgett, tjelinek
Target Milestone:	---
Target Release:	4.6.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-10-27 16:01:07 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 Filip Krepinsky 2020-05-27 14:53:52 UTC

How reproducible:
100


Steps to Reproduce:
1. create VM with http / attach cloned disk source
2. delete the VM and uncheck Delete Disks
3. create the same VM (you can change things like http source) with the same name again


Actual results:

the VM returns an error: Failed to create DataVolume: admission webhook "datavolume-validate.cdi.kubevirt.io" denied the request: Destination PVC already exists

Expected results:
The VM gets and DVs get created and can start sucessfully 

Additional info:

We should generateName for all of our dataVolumes (also for example in clone-modal, etc.)

Comment 3 Guohua Ouyang 2020-07-02 03:07:38 UTC

Could reproduce the issue on 4.5.0-rc.4 and verified it on remotes/upstream/release-4.6(commit 5d355c87839fca0cec4a012434ce3826ea3280f8).

Comment 5 errata-xmlrpc 2020-10-27 16:01:07 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 (OpenShift Container Platform 4.6 GA Images), 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:4196