Bug 1940296

Summary: VM cloned from a VM(HPP) is stucking at starting
Product: OpenShift Container Platform Reporter: Guohua Ouyang <gouyang>
Component: Console Kubevirt PluginAssignee: Yaacov Zamir <yzamir>
Status: CLOSED DUPLICATE QA Contact: Guohua Ouyang <gouyang>
Severity: high Docs Contact:
Priority: high    
Version: 4.8CC: aos-bugs, gouyang
Target Milestone: ---   
Target Release: 4.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1946886 (view as bug list) Environment:
Last Closed: 2021-04-07 06:40:04 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:
Bug Depends On:    
Bug Blocks: 1946886    

Description Guohua Ouyang 2021-03-18 04:50:00 UTC
Description of problem:
Two situations will prevent a VM cloned from another VM(HPP) cannot be started at all, it stucks at starting state.
1. the original VM is never started before, the PVC for the VM is in pending and not bounded.
2. the original VM is running before the cloned VM starts.

Only happens with storageClass HPP, not OCS.

Version-Release number of selected component (if applicable):
CNV 2.6/CNV 2.7

How reproducible:
100%

Steps to Reproduce:
1. create a VM 'A with storage class HPP, uncheck "Start on creation"
2. clone a VM 'B' from VM 'A'
3. start VM 'B'  / start VM 'A' and then start VM 'B'

Actual results:
VM 'B‘ is never becoming running, stucks in starting state.

Expected results:
VM 'B' can become running as this is normal flow.

Additional info:
The root cause is the datavolume clone is never run, no clue in import pod logs at all.
ref: https://groups.google.com/g/kubevirt-dev/c/FAo2raBtlKI

Comment 1 Guohua Ouyang 2021-03-18 04:53:46 UTC
This should be a storage issue, report it in console kubevirt for a review firstly because the flow is quite normal. 
1. created a HPP VM, it could run well.
2. after sometime cloned a new VM from it
3. try to start both VMs

only the firstly VM can be started, the cloned VM is stucking at 'starting' and no useful logs/informations at all.

Comment 2 Yaacov Zamir 2021-04-07 06:40:04 UTC
set as duplicate of BZ#1924728 because the root of this problem is the fact that the user can't see the problem and need to look into events and logs to understand what happen

Note:
we can also open a bug on storage to fix the specific issue here

*** This bug has been marked as a duplicate of bug 1924728 ***