Bug 1927473
Summary: | virtctl image-upload dv to an empty pvc times out when using virtctl-2.6.0 | ||
---|---|---|---|
Product: | Container Native Virtualization (CNV) | Reporter: | Alex Kalenyuk <akalenyu> |
Component: | Storage | Assignee: | skagan |
Status: | CLOSED ERRATA | QA Contact: | Alex Kalenyuk <akalenyu> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.6.0 | CC: | cnv-qe-bugs, mrashish, ngavrilo, yadu |
Target Milestone: | --- | Keywords: | Automation |
Target Release: | 4.8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | kubevirt 4.8.0-177 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-07-27 14:24:44 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
Alex Kalenyuk
2021-02-10 20:09:28 UTC
Alex, in the old virtctl, when you upload to a DV when you have an existing PVC - did a DV get created? (In reply to Natalie Gavrielov from comment #2) > Alex, in the old virtctl, when you upload to a DV when you have an existing > PVC - did a DV get created? A DV doesn't get created in the old/current virtctl for this operation: Downgraded: kubevirt-virtctl-2.5.4-107.el7_9.x86_64 Complete! [cnv-qe-jenkins@stg01-alex-rjlb7-executor virtctl-exist-pvc]$ oc create -f empty_pvc.yaml persistentvolumeclaim/empty-pvc created (reverse-i-search)`virt': ^Crtctl image-upload dv empty-pvc --image-path=./cirros-qcow2.img --insecure --no-create (reverse-i-search)`--in': virtctl image-upload dv empty-pvc --image-path=./cirros-qcow2.img ^Cinsecure --no-create [cnv-qe-jenkins@stg01-alex-rjlb7-executor virtctl-exist-pvc]$ virtctl image-upload dv empty-pvc --image-path=./cirros-qcow2.img --insecure --no-create Using existing PVC openshift-virtualization-os-images/empty-pvc Waiting for PVC empty-pvc upload pod to be ready... Pod now ready Uploading data to https://cdi-uploadproxy-openshift-cnv.apps.stg01-alex.cnv-qe.rhcloud.com 12.13 MiB / 12.13 MiB [==========================================================================================================================================================================================================] 100.00% 0s Uploading data completed successfully, waiting for processing to complete, you can hit ctrl-c without interrupting the progress Processing completed successfully Uploading ./cirros-qcow2.img completed successfully [cnv-qe-jenkins@stg01-alex-rjlb7-executor virtctl-exist-pvc]$ oc get dv -A No resources found The combination of options used in this scenario is invalid: "virtctl image-upload dv empty-pvc --image-path=./cirros-qcow2.img --insecure --no-create" "dv" means use a DataVolume. --no-create means don't create the DataVolume because it already exists But you have created a PVC with the same name. So virtctl is looking for a DV which you said already exists and this eventually times out. I think we can improve virtctl with better messages in the following scenarios: 1. "virtctl dv my-disk ... --no-create" where my-disk does not exist: - Continue waiting but print a message "DV my-disk not found..." each time it is checked 2. "virtctl pvc my-disk ... --no-create" where my-disk does not exist: - Continue waiting but print a message "PVC my-disk not found..." each time it is checked 3. "virtctl dv my-disk ... --no-create" where my-disk is a PVC but a DV of the same name does not exist: - Print a message "Error: No DataVolume is associated with the existing PVC my-disk" and exit immediately. 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 4.8.0 Images), 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:2920 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 4.8.0 Images), 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:2920 |