Description of problem: the openshift-vitualization-os-images is not listed as a namespace the user can access when trying to create a VM from a pvc in that namespace. therefore the user cannot select a pvc from teh namespace. Version-Release number of selected component (if applicable): image: brew.registry.redhat.io/rh-osbs/iib:23684 How reproducible: always Steps to Reproduce: 1. put a mastr image in the openshift-virtualization-os-images namespace 2. create a virtual machine using the wizard 3. on the disks section of the wizard, add a disk and shoose clone an existing pvc as the source. 4. select the dropdown for the namespace, openshift-vitualization-os-images is not there. Actual results: since teh namespace cannot be selected, the pvc inside the namespace is not seen in the gui. Expected results: to see the namespace and to see the pvcs within it. Additional info: Running this command from cli allowed me to see the namespace in the gui: oc adm policy add-role-to-group view system:authenticated
The openshift-vitualization-os-images is not meant to be hosting any images - it is supposed to be holding the images bound to operating systems. The flow should be that you upload an image to a pvc using the PVC upload screen and select that you want to "Attach this data to a Virtual Machine operating system". Than, once done, in the vm wizard you pick that OS and the source will be cloned automatically. Does this flow work for you?
This flow does not work in my case. I am also a little confused with the following statement and it might be me not understanding terminology: "The openshift-vitualization-os-images is not meant to be hosting any images - it is supposed to be holding the images bound to operating systems." I would assume "bound" means the the image is tied to a running VM. But your next statement says it will be cloned in the VM wizard. Here is the flow I was considering: I need to create a Windows VM using the installation ISO. I want the disk on the Windows VM to be used as a master image to create VMs from. All of the above would replace the PVC upload screen of your flow. Then, using the GUI, I need to: 1. create a VM 2. attach the installation ISO 3. attach a blank disk 4. Install the operating system and install the virtio drivers 5. run a windows sysprep.exe on the VM to make it generic 6. remove the VM but not the disk it created. I can do all the above without issue. In fact I can do this in the openshift-virtualization-os-images namespace, which I should not be able to do. There is another bug about this: https://bugzilla.redhat.com/show_bug.cgi?id=1891808 I then need to clone or move the DV/PVC from teh namespace I created the VM in, into the openshift-virtualization-os-images namespace. After that, I need to use the GUI wizard to create the VM. 1. Create a VM - Workloads -> Virtualization -> Create Virtual Machine -> New with Wizard 2. Under the General section of the wizard - For the Boot source, select "Existing PVC" 3. Under the Storage section of the wizard - Add Disk 3a. For Source, select "Clone an existing PVC" 3b. A PVC Namespace dropdown appears. I should see the openshift-virtualization-os-images namespace here, but I dont. This prevents me from selecting the image I created above that resides in that namespace. 3c. For Persistent Volume Claim - I should select the master image I created earlier so it can be cloned into a new VM. I cannot select this because I cannot see the namespace. Thanks,
Upstream PR: https://github.com/kubevirt/ssp-operator/pull/74
On latest build created a user and created a virtual machine using the wizard, openshift-virtualization-os-images namespace is visible by the user.
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 Virtualization 2.6.0 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-2021:0799