Bug 1731179

Summary: virtctl image-upload times out with volumeMode as block.
Product: Container Native Virtualization (CNV) Reporter: Gowrishankar Rajaiyan <grajaiya>
Component: StorageAssignee: Daniel Erez <derez>
Status: CLOSED ERRATA QA Contact: Gowrishankar Rajaiyan <grajaiya>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0CC: alitke, cnv-qe-bugs, grajaiya, igoihman, qixuan.wang, sgordon, ycui
Target Milestone: ---   
Target Release: 2.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-31 14:08:47 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 Gowrishankar Rajaiyan 2019-07-18 14:25:24 UTC
Description of problem: virtctl image-upload times out while volumeMode is 'block'.


Version-Release number of selected component (if applicable):
hco-bundle-registry:v2.0.0-36

How reproducible: Always


Steps to Reproduce:
0. Ensure that you have block PV's available.
1. Perform image-upload using virtctl.


Actual results: image-upload fails with 'timed out waiting for the condition'.

$ virtctl image-upload --pvc-name=route-test-with-route --image-path=/tmp/pytest-of-cnv-qe-jenkins/pytest-39/test_successful_upload_with_su7/cirros-0.4.0-x86_64-disk.qcow2.xz --pvc-size=1Gi --insecure --storage-class local-blk
PVC local-storage/route-test-with-route created
Waiting for PVC route-test-with-route upload pod to be running...
timed out waiting for the condition



Expected results: image-upload is successful.


Additional info: Note that based on my discussion with Irit, image-upload could be worked around by creating a PVC before executing 'virtctl image-upload'.




************************************************************************
*          Check if some pods in not Running state                     *
************************************************************************
No pods in not running status in kubevirt-hyperconverged
************************************************************************
*                          oc version                                  *
************************************************************************
oc version: Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.4", GitCommit:"c9e4f28ff", GitTreeState:"clean", BuildDate:"2019-06-26T23:04:27Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+c62ce01", GitCommit:"c62ce01", GitTreeState:"clean", BuildDate:"2019-06-27T18:14:14Z", GoVersion:"go1.11.6", Compiler:"gc", Platform:"linux/amd64"}
************************************************************************
*                        kubectl version                               *
************************************************************************
kubectl version: Client Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+c9e4f28ff", GitCommit:"c9e4f28ff", GitTreeState:"clean", BuildDate:"2019-06-26T23:04:27Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.4+c62ce01", GitCommit:"c62ce01", GitTreeState:"clean", BuildDate:"2019-06-27T18:14:14Z", GoVersion:"go1.11.6", Compiler:"gc", Platform:"linux/amd64"}
************************************************************************
*                        virtctl version                               *
************************************************************************
virtctl version: Client Version: version.Info{GitVersion:"v0.17.4", GitCommit:"adfdb8c07830b99fc79d2fd1d004e862ef70979e", GitTreeState:"clean", BuildDate:"2019-06-27T17:03:10Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{GitVersion:"v0.17.4", GitCommit:"adfdb8c07830b99fc79d2fd1d004e862ef70979e", GitTreeState:"clean", BuildDate:"2019-06-27T14:08:17Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
************************************************************************
*                         HCO image id                                 *
************************************************************************
HCO Image Id: NAME                IMAGE_ID
hco-catalogsource   brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/container-native-virtualization/hco-bundle-registry:v2.0.0-36
************************************************************************

Comment 2 Qixuan Wang 2019-09-18 07:10:32 UTC
Tested with hco-bundle-registry-v2.1.0-47, CDI v2.1.0-14, virtctl client v0.20.1, virtctl server v0.20.5
Large image is uploaded successfully and VM can run with it. The bug has been fixed. Move it to VERIFIED, thanks.

[cnv-qe-jenkins@cnv-executor-ying ~]$ virtctl image-upload --storage-class=rook-ceph-block --image-path=./cirros-0.4.0-x86_64-disk.img --pvc-size=11Gi --block-volume --pvc-name=upload-block-rhel8-1 --insecure
PVC bug/upload-block-rhel8-1 created
Waiting for PVC upload-block-rhel8-1 upload pod to be running...
Pod now running
Uploading data to https://cdi-uploadproxy-openshift-cnv.apps.working.oc4

 12.13 MiB / 12.13 MiB [=================================================================================================================] 100.00% 2s

Uploading ./cirros-0.4.0-x86_64-disk.img completed successfully

Comment 4 errata-xmlrpc 2019-10-31 14:08:47 UTC
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, 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/RHEA-2019:3282