Bug 1783013

Summary:	Unable to boot RHCOS instances using libvirtd on s390x
Product:	OpenShift Container Platform	Reporter:	Alex Crawford <crawford>
Component:	Cloud Compute	Assignee:	Alex Crawford <crawford>
Status:	CLOSED ERRATA	QA Contact:	Jeremy Poulin <jpoulin>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.2.z	CC:	jpoulin
Target Milestone:	---
Target Release:	4.2.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1783010	Environment:
Last Closed:	2020-01-07 17:55:11 UTC	Type:	---
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:	1783004, 1783010
Bug Blocks:

Description Alex Crawford 2019-12-12 19:46:22 UTC

+++ This bug was initially created as a clone of Bug #1783010 +++

+++ This bug was initially created as a clone of Bug #1783004 +++

s390x doesn't support the QEMU firmware config device that we use to pass Ignition configs through to RHCOS guests. As a fallback, libguestfish was used to modify the root disk to directly inject the Ignition config. This doesn't work on remote machines though(as is always the case with libvirt and the cluster API provider), so the new approach is to use the RHCOS images built for OpenStack and to pass the Ignition config through the config-drive mechanism instead.

Comment 4 errata-xmlrpc 2020-01-07 17:55:11 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0014