Description of problem: Currently, while editing the boot source of a cloned template, the accessMode is ReadWriteMany in the opened modal, user may not notice it and then saved, which causes unexpected results. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. clone a template 2. edit the bootsource of this cloned template 3. Actual results: the default access mode is RWX Expected results: the default access mode is RWO Additional info:
The optimized StorageProfile settings should be applied while editing the disk in all places.
"Apply optimized StorageProfile settings" is checked while adding a new disk, But not checked while editing a existing disk
Created attachment 1892016 [details] accessmode
Now the "Apply optimized StorageProfile settings" is checked by default, which is very good as it ensures no unexpected results will happen. But there is still a UI here, it shows "ReadWriteMany" for HPP in the disk modal, which should be "ReadWriteOnce". If we check the disk attributes after the disk is created, it's actually "ReadWriteOnce", that should be the work of "Apply optimized StorageProfile settings".
verified on v4.12.0-88
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 Virtualization 4.11.0 Images security and bug fix 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:6526