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

Bug 1780120

Summary: RHCOS VM unable to boot, goes into emergency , Device doesn't exist or access denied.
Product: [oVirt] ovirt-engine Reporter: Evgeny Slutsky <eslutsky>
Component: BLL.VirtAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED DUPLICATE QA Contact: Avihai <aefrat>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.3.7.2CC: bugs
Target Milestone: ---   
Target Release: ---   
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-12-05 16:13:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine log + domainxml
none
rhcos journal none

Description Evgeny Slutsky 2019-12-05 12:46:32 UTC 
Description of problem:

An RHCOS VM which is run for the first time, with ignition set correctly,
goes into emergency mode, issue reproduced on random occasions.


How reproducible:


Steps to Reproduce:
1. Have 1 host
2. Create an RHCOS VM with custom_script with basic ignition  https://coreos.com/ignition/docs/latest/examples.html 
3. boot the VM
4. watch the VM unable to boot correctly, goes into emergency mode.

Actual results:
vm doesnt boot goes into emergency mode, unable to mount disk correctly.

Expected results:
vm boots successfully



Additional info:

domainXML from engine.log
https://paste.centos.org/view/57b91ea2


journal logs extracted from RCHOs:
https://paste.centos.org/view/6a1a3c71#L754
Comment 1 Evgeny Slutsky 2019-12-05 12:49:43 UTC 
Created attachment 1642367 [details]
engine log + domainxml
Comment 2 Evgeny Slutsky 2019-12-05 12:50:14 UTC 
Created attachment 1642368 [details]
rhcos journal
Comment 3 Evgeny Slutsky 2019-12-05 16:13:39 UTC 

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