Bug 2203727
| Summary: | [4.13.z] Missing virtctl vmexport download manifests command | ||
|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Jenia Peimer <jpeimer> |
| Component: | Storage | Assignee: | Alexander Wels <awels> |
| Status: | CLOSED ERRATA | QA Contact: | Jenia Peimer <jpeimer> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.13.0 | CC: | alitke, awels, dholler, ngavrilo, yadu |
| Target Milestone: | --- | ||
| Target Release: | 4.13.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | v4.13.1.rhel9-91 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-08-16 14:10:01 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jenia Peimer
2023-05-15 06:55:05 UTC
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 |