Bug 2100103 - Can't delete rootdisk in customization wizard
Summary: Can't delete rootdisk in customization wizard
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Aviv Turgeman
QA Contact: Guohua Ouyang
Depends On: 2102302
TreeView+ depends on / blocked
Reported: 2022-06-22 12:51 UTC by Yaacov Zamir
Modified: 2022-08-09 02:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-08-09 02:36:03 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 11887 0 None open Bug 2100103: Can't delete rootdisk in customization wizard 2022-07-27 15:51:11 UTC
Github openshift console pull 11932 0 None open Revert "Bug 2100103: Can't delete rootdisk in customization wizard" 2022-08-04 08:08:40 UTC
Red Hat Product Errata RHSA-2022:5875 0 None None None 2022-08-09 02:37:33 UTC

Description Yaacov Zamir 2022-06-22 12:51:42 UTC
Description of problem:
Can't delete rootdisk in customization wizard
In the customzation wizard, a user can't delete the rootdisk

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

How reproducible:

Steps to Reproduce:
1.create a rhel8 vm using the wizard
2.choose customize
3.in the storage tab, try to delete the rootdisk

Actual results:
nothing happen

Expected results:
the disk get deleted, and the wizard warn the user that the vm will not start without a boot disk

Additional info:

Comment 3 Guohua Ouyang 2022-08-04 01:25:08 UTC
the fix causes the rootdisk is not showing on storage tab.

Comment 7 errata-xmlrpc 2022-08-09 02:36:03 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.10.26 security 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.


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