Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

For information on the advisory (Important: OpenShift Virtualization 4.14.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-2023:6817

CPaaS Service Account mentioned this issue in a merge request of cpaas-midstream / openshift-virtualization / kubevirt-plugin on branch cnv-4.15-rhel-9_upstream_ad48df6ba7e8b491fa7e2d1b90ee7d6d:

Updated US source to: f36902f Merge pull request #1405 from avivtur/fix-centos-vm-name

CPaaS Service Account mentioned this issue in a merge request of cpaas-midstream / openshift-virtualization / kubevirt-plugin on branch cnv-4.14-rhel-9_upstream_ad48df6ba7e8b491fa7e2d1b90ee7d6d:

Updated US source to: f36902f Merge pull request #1405 from avivtur/fix-centos-vm-name

Thanks Tal. So then the bug is also for creating VMs from InstanceTypes, too, in 4.14, where the checkbox is enabled but checked by default.

hstastna@redhat.com 
The checkbox should be enabled but not checked by default.

i.e - empty clickable square

Hi rh-ee-ttobias,

This applies anywhere we create new VMs (template and instancetype), but creating with instancetypes is in the correct state, so the only fix that should be done is in creating a VM from the template.

Does this mean that when creating VM from InstanceType the checkbox should be enabled?

hstastna@redhat.com 
You're right.

Another bug related to the checkbox:
when unchecking the checkbox and saving the change, the change is not saved at all:
when opening the checkbox the second time, it remains checked!
This is true for both "Use existing" and "Add new" radio buttons.

rh-ee-ttobias am I right and is this a bug? Or is that an intentional behavior? Thanks!

Hi hstastna@redhat.com 
This applies anywhere we create new VMs (template and instancetype), but creating with instancetypes is in the correct state, so the only fix that should be done is in creating a VM from the template.

Thank you!

Hi rh-ee-ttobias, just to make sure: does this apply ONLY on the scenario of creating a VM from template (in Catalog)? We have more ways of creating a VM. Thanks in advance!