Bug 1940296 - VM cloned from a VM(HPP) is stucking at starting
Summary: VM cloned from a VM(HPP) is stucking at starting
Status: CLOSED DUPLICATE of bug 1924728
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Yaacov Zamir
QA Contact: Guohua Ouyang
Depends On:
Blocks: 1946886
TreeView+ depends on / blocked
Reported: 2021-03-18 04:50 UTC by Guohua Ouyang
Modified: 2021-04-07 07:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1946886 (view as bug list)
Last Closed: 2021-04-07 06:40:04 UTC
Target Upstream Version:

Attachments (Terms of Use)

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:

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

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 ***

Note You need to log in before you can comment on or make changes to this bug.