-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
None
-
0.42
-
False
-
-
False
-
None
-
---
-
---
-
-
No
Description of problem:
Login with a regular user, and add a volume in their own namespace. In catalog, user cannot see this volume and use it. However, use this volume from CLI is okay.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Login with a regular user "test" and create a namespace "test" 2. Add a volume "test" in namespace "test" 3. In catalog, the user cannot see volume"test" 4. Login with the user "test" in command line, and switch to project "test" 5. Create VM with this volume via below command: # virtctl create vm --name=test-vm --instancetype=u1.medium --volume-datasource=src:test/test --cloud-init-user-data I2Nsb3VkLWNvbmZpZwpjaHBhc3N3ZDoKICBleHBpcmU6IGZhbHNlCnBhc3N3b3JkOiA2cmIxLW16NzctZmZ4cgp1c2VyOiBjZW50b3MK | oc create -f - virtualmachine.kubevirt.io/test-vm created # oc get vm test-vm NAME AGE STATUS READY test-vm 53m Running True 6. the VM is able to be created from CLI
Actual results:
Regular user cannot create vm with their own volumes from UI, but it's okay via CLI.
Expected results:
Regular can create vm from with their own volumes.
Additional info:
- is duplicated by
-
CNV-41228 Users should be able to use their own base images
- Closed
- links to
-
RHEA-2023:122979 OpenShift Virtualization 4.16.0 Images
- mentioned on