Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1739447

Summary: Can't create VM from web console when using hostpath provisioner
Product: OpenShift Container Platform Reporter: Qixuan Wang <qixuan.wang>
Component: Console Kubevirt PluginAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED CURRENTRELEASE QA Contact: Qixuan Wang <qixuan.wang>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.0CC: alitke, aos-bugs, cnv-qe-bugs, gouyang, ncredi, sgordon
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-10 08:57:53 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 Qixuan Wang 2019-08-09 10:47:20 UTC
Description of problem:
When hostpath provisioner is default provisioner in the cluster, provision a VM from web console, PVC is pending with message:
persistentvolume-controller  waiting for a volume to be created, either by external provisioner "kubevirt.io/hostpath-provisioner" or manually created by system administrator
PVC and DV don't have kubevirt.io/provisionOnNode: <node> as an annotation.


Version-Release number of selected component (if applicable):
hostpath-provisioner: v1.4.1-4
CDI v1.4.1-1


How reproducible:
100%


Steps to Reproduce:
1. Set hostpath-provisioner as default in the cluster.
2. From URL to provision a VM on web console. 
3. Check PVC and DV 


Actual results:
1. [cloud-user@cnv-executor-qwang-14-master-b19d80-1 ~]$ oc get sc
NAME                                      PROVISIONER                        AGE
glusterfs-storage                         kubernetes.io/glusterfs            1d
hdd                                       kubernetes.io/no-provisioner       1d
kubevirt-hostpath-provisioner (default)   kubevirt.io/hostpath-provisioner   1d

3. [cloud-user@cnv-executor-qwang-14-master-b19d80-1 ~]$ oc get pvc
NAME                               STATUS    VOLUME    CAPACITY   ACCESS MODES   STORAGECLASS                    AGE
rootdisk-qwang-web-import-cirros   Pending                                       kubevirt-hostpath-provisioner   36s

[cloud-user@cnv-executor-qwang-14-master-b19d80-1 ~]$ oc describe pvc rootdisk-qwang-web-import-cirros
Name:          rootdisk-qwang-web-import-cirros
Namespace:     qwang-web
StorageClass:  kubevirt-hostpath-provisioner
Status:        Pending
Volume:
Labels:        app=containerized-data-importer
               cdi-controller=rootdisk-qwang-web-import-cirros
Annotations:   cdi.kubevirt.io/storage.contentType=kubevirt
               cdi.kubevirt.io/storage.import.endpoint=https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img
               cdi.kubevirt.io/storage.import.importPodName=importer-rootdisk-qwang-web-import-cirros-bvfk6
               cdi.kubevirt.io/storage.import.source=http
               cdi.kubevirt.io/storage.pod.phase=Pending
               volume.beta.kubernetes.io/storage-provisioner=kubevirt.io/hostpath-provisioner
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Events:
  Type    Reason                Age               From                         Message
  ----    ------                ----              ----                         -------
  Normal  ExternalProvisioning  7s (x6 over 44s)  persistentvolume-controller  waiting for a volume to be created, either by external provisioner "kubevirt.io/hostpath-provisioner" or manually created by system administrator


[cloud-user@cnv-executor-qwang-14-master-b19d80-1 ~]$ oc describe dv rootdisk-qwang-web-import-cirros
Name:         rootdisk-qwang-web-import-cirros
Namespace:    qwang-web
Labels:       kubevirt.io/created-by=c157c547-ba8f-11e9-9c00-fa163e34ff55
Annotations:  <none>
API Version:  cdi.kubevirt.io/v1alpha1
Kind:         DataVolume
Metadata:
  Creation Timestamp:  2019-08-09T10:23:39Z
  Generation:          1
  Owner References:
    API Version:           kubevirt.io/v1alpha3
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  VirtualMachine
    Name:                  qwang-web-import-cirros
    UID:                   c157c547-ba8f-11e9-9c00-fa163e34ff55
  Resource Version:        551054
  Self Link:               /apis/cdi.kubevirt.io/v1alpha1/namespaces/qwang-web/datavolumes/rootdisk-qwang-web-import-cirros
  UID:                     c15f2199-ba8f-11e9-9c00-fa163e34ff55
Spec:
  Pvc:
    Access Modes:
      ReadWriteOnce
    Data Source:  <nil>
    Resources:
      Requests:
        Storage:  10Gi
  Source:
    Http:
      URL:  https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img
Status:
  Phase:  Pending
Events:
  Type    Reason  Age               From                   Message
  ----    ------  ----              ----                   -------
  Normal  Synced  55s (x5 over 4m)  datavolume-controller  DataVolume synced successfully


Expected results:
Provision a PVC using hostpath provisioner is successful.


Additional info:

Comment 1 Tomas Jelinek 2019-08-12 11:53:56 UTC
It looks a lot like https://bugzilla.redhat.com/show_bug.cgi?id=1739456 - it makes me think, is it not a backend / env issue?

@Adam, are there some specifics we need to do differently if the hostpath provisioner is used?

Comment 4 Tomas Jelinek 2019-11-12 12:34:37 UTC
matching the state of the bug in which it is being fixed (https://bugzilla.redhat.com/show_bug.cgi?id=1739456)

Comment 7 Guohua Ouyang 2019-12-10 04:17:34 UTC
This is not an issue on UI as the VM is created successfully, the VM cannot get into running due to the backend pvc is pending, since bug 1739456 is not fixed, maybe we can close this directly.

@tomas, how do you think?

Comment 8 Tomas Jelinek 2019-12-10 08:43:29 UTC
@guohua: yes, I agree, it is a backend issue and there is no point in maintaining this BZ. Please feel free to close it with whatever resolution makes most sense to you.

Comment 9 Guohua Ouyang 2019-12-10 08:57:53 UTC
Close the issue because the VM can be created on UI.