Bug 1916099

Summary: VM creation - customization wizard - user should be allowed to delete and re-create root disk
Product: OpenShift Container Platform Reporter: Ruth Netser <rnetser>
Component: Console Kubevirt PluginAssignee: Yaacov Zamir <yzamir>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: high Docs Contact:
Priority: high    
Version: 4.7CC: aos-bugs, gouyang, yzamir
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:53:14 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:

Description Ruth Netser 2021-01-14 08:08:21 UTC
Description of problem:
When a VM is created using the customization wizard, it is not possible to delete the root disk and re-create a new root disk.
This is relevant for a case where a user would like to create a VM using and existing PVC (and not clone one).
The option to use an existing PVC is not offered in the boot source dropdown.
To allow a user to do that, it should be possible to delete the created root disk and re-create a new one.

Version-Release number of selected component (if applicable):
OCP 4.7, CNV 2.6

How reproducible:

Steps to Reproduce:
1. Create a VM using the customization wizard

Actual results:
There's no option to delete the root disk

Expected results:
There should be an option to delete the root disk.
If the user deletes the root disk and does not create a new one, there should be an error (this is already implemeneted)

Additional info:

Comment 4 errata-xmlrpc 2021-02-24 15:53:14 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.