Description of problem: When cloning a Virtual Machine from a template, if I edit the boot disk and change the storage class, the change is reverted when I dismiss the dialog. Version-Release number of selected component (if applicable): 4.9.0 How reproducible: Always Steps to Reproduce: 1. Create VM from wizard 2. Select a Template with an available boot source 3. Click "Customize Virtual Machine" and navigate to the storage page 4. Edit the rootdisk: change the storage class and click Save Actual results: The disk is not changed Expected results: The change should be apparent in the list of disks Additional info: This only seems to happen if "Apply optimized StorageProfile settings" is checked
This only happens with a template with boot source available, if the template has no boot source, change disk storageClass works.
I noticed that this issue is also happening when creating a new VM with no boot source. This is a pretty severe regression in my opinion. Bumping severity. Will you target it please?
target to 4.10 and updated priorities, thanks
Created attachment 1842265 [details] rootdisk storageClass I still only see this issue when the template has no boot source on OCP 4.9.6.
Cannot reproduce, I tried with both source and sourceless templates. please provide more info
Tal hi, this is a high severity issue, can you help with blocker +/- ?
setting to blocker- because we can't reproduce on 4.10
Just tested the bug still exists in 4.9.15, but not in 4.10.
Moving the 4.10 but to verified, Guohua, Tal, do we need to fix on 4.9.z ? If we do, we need to clone this bug to 4.9.z p.s. we need this 4.10 bug as verified, o/w we will not be able to merge a backport PR to 4.9.z)
see comment#9
(In reply to Yaacov Zamir from comment #10) > see comment#9 no problem, let me clone the bug to 4.9.z
bug for 4.9.z: https://bugzilla.redhat.com/show_bug.cgi?id=2042843
I've managed to reproduce for 4.10 as well, steps: 1. select any template, and add a boot source and wait for it 2. Create VM from wizard 3. Select a Template with an available boot source 4. Click "Customize Virtual Machine" and navigate to the storage page 5. Edit the rootdisk: change the storage class and click Save this bug is not reproducing for auto-images as boot source, moving back to ASSIGNED
Verified on master/4.10.0-0.nightly-2022-02-06-194614
Changing status back to ON_QA as the bug target version is 4.11.0, we need to verify the bug on OCP 4.11.0. And for 4.10.0 bug, it is the bug 2049762 in POST right now.
(In reply to Ying Cui from comment #17) > Changing status back to ON_QA as the bug target version is 4.11.0, we need > to verify the bug on OCP 4.11.0. And for 4.10.0 bug, it is the bug 2049762 > in POST right now. Or is the master the OCP 4.11.0 version? Could you add the accurate version information?
(In reply to Ying Cui from comment #18) > (In reply to Ying Cui from comment #17) > > Changing status back to ON_QA as the bug target version is 4.11.0, we need > > to verify the bug on OCP 4.11.0. And for 4.10.0 bug, it is the bug 2049762 > > in POST right now. > > Or is the master the OCP 4.11.0 version? Could you add the accurate version > information? the master is equaling to release-4.11 until 4.11 code freeze, so we're fine to verify 4.11 bugs on master.
Verified on master, commit 3018969ac7 https://github.com/openshift/console/commit/3018969ac709252572899a60c7835a5660eaff95
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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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. https://access.redhat.com/errata/RHSA-2022:5069
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days