Bug 1860880 - VM fails to boot after virtctl reboot
Summary: VM fails to boot after virtctl reboot
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 2.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: sgott
QA Contact: Israel Pinto
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-27 10:23 UTC by vsibirsk
Modified: 2020-07-28 10:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-28 10:41:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description vsibirsk 2020-07-27 10:23:34 UTC
Description of problem:
After starting VM, connecting via console to it and then rebooting, VM fails to boot:
[FAILED] Failed to mount /sysroot. (full console log and virt-launcher pod logs attached)

How reproducible:
100% (automation)

Steps to Reproduce:
1.Create dv and vm (yamls attached)
2.Start created vm: virtctl start <vm_name>
3.Connect to vm via console: virtctl console <vm_name>
4.Reboot vm: virtctl reboot <vm_name>

Actual results:
VM fails to boot

Expected results:
VM boots OK

Additional info:
Issue was found via automation where it reproduce all the time. Test steps are same as "Steps to Reproduce" section.
While investigating issue, we found that the issue won't reproduce if after connect to console step we add additional action (like once again connect/disconnect from console).
Also it doesn't matter how to reboot vm - reboot or stop/start makes no difference.

Issue reproduced on nfs and hpp, so seems not related to storage type.

Comment 5 vsibirsk 2020-07-28 09:00:35 UTC
After changing terminationGracePeriodSeconds from 0 to 30, issue doesn't reproduce

Comment 6 Israel Pinto 2020-07-28 10:41:24 UTC
Closing as works for me with request to update the terminationGracePeriodSeconds in templates: https://bugzilla.redhat.com/show_bug.cgi?id=1861297  
and Doc BZ for 2.4: https://bugzilla.redhat.com/show_bug.cgi?id=1861322


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