Description of problem: In 4.13 we can download manifests from VMExport, virtctl makes the process much easier Version-Release number of selected component (if applicable): 4.13 How reproducible: Always Steps to Reproduce: 1. Create a VMExport, try to download a manifest: virtctl vmexport download export --manifest --vm=example Actual results: Command not supported Expected results: Command supported, manifest downloaded
Verified on v4.13.1.rhel9-152 1. Created VM, stopped the VM $ oc get vm -A NAMESPACE NAME AGE STATUS READY default vm-cirros-source-ocs 22m Stopped False 2. $ virtctl vmexport download export --manifest --vm=vm-cirros-source-ocs --include-secret --output=manifest.yaml VirtualMachineExport 'default/export' created succesfully waiting for VM Export export status to be ready... $ oc get vmexport -A NAMESPACE NAME SOURCEKIND SOURCENAME PHASE default export VirtualMachine vm-cirros-source-ocs Ready 3. Copied the manifest.yaml to the target cluster, edited a namespace 4. In the target cluster: $ oc create -f manifest.yaml configmap/export-ca-cm-export created virtualmachine.kubevirt.io/vm-cirros-source-ocs created secret/header-secret-export created $ virtctl start vm-cirros-source-ocs -n target-export $ oc get vm -A NAMESPACE NAME AGE STATUS READY target-export vm-cirros-source-ocs 29m Running True
Jenia, can this bug be closed now?
Yes, this bug was Verified a long time ago, it should have been moved to RELEASE_PENDING by errata automation, and then CLOSED when the target version was released. There was probably an issue somewhere in this process. Dominik dholler, could you please check if there's anything we should do with this? Or can we just close the bug?
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.13.3 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:4664