Bug 1780120 - RHCOS VM unable to boot, goes into emergency , Device doesn't exist or access denied.
Summary: RHCOS VM unable to boot, goes into emergency , Device doesn't exist or acc...
Keywords:
Status: CLOSED DUPLICATE of bug 1775728
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.3.7.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Michal Skrivanek
QA Contact: Avihai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-05 12:46 UTC by Evgeny Slutsky
Modified: 2019-12-05 16:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-05 16:13:39 UTC
oVirt Team: Storage
Embargoed:

Attachments (Terms of Use)
engine log + domainxml (15.20 KB, text/plain)
2019-12-05 12:49 UTC, Evgeny Slutsky 		no flags Details
rhcos journal (67.03 KB, text/plain)
2019-12-05 12:50 UTC, Evgeny Slutsky 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.