Created attachment 1842892 [details] Error cloning to new namespace Description of problem: When cloning a Virtual Machine and specifying a different namespace and error accrues. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Open a clone a virtual machine modal 2. Ask for a different namespace 3. Actual results: An error: Error "Authorization failed, message is: User system:serviceaccount:rhodes:default has insufficient permissions in clone source namespace tal-vms" for field "spec.dataVolumeTemplates[0]". Expected results: A vm is clonned Additional info:
Do we need to handle the clone permission on the UI? If yes, let's move the bug to CNV-UX for investigation.
(In reply to Guohua Ouyang from comment #4) > Do we need to handle the clone permission on the UI? If yes, let's move the > bug to CNV-UX for investigation. moving to CNV
Verified on OCP-v4.11.0-39, a message is added in the modal when select a different namespace during clone. "Make sure to have clone permissions in the destination namespace. Learn more "
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