Bug 1782992 - Unable to boot RHCOS instances on remote libvirtd on s390x
Summary: Unable to boot RHCOS instances on remote libvirtd on s390x
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.3.0
Assignee: Alex Crawford
QA Contact: Jeremy Poulin
Depends On: 1782986
Blocks: 1782994
TreeView+ depends on / blocked
Reported: 2019-12-12 18:48 UTC by Alex Crawford
Modified: 2020-01-23 11:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1782986
: 1782994 (view as bug list)
Last Closed: 2020-01-23 11:18:56 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 2803 0 None closed Bug 1782992: terraform/plugins: update libvirt provider 2020-04-17 07:59:27 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:19:14 UTC

Description Alex Crawford 2019-12-12 18:48:57 UTC
+++ This bug was initially created as a clone of Bug #1782986 +++

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, 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 1 Jeremy Poulin 2019-12-12 20:45:47 UTC
Moving to ON_QA since this is already merged and verified.

Comment 2 Jeremy Poulin 2019-12-12 20:46:32 UTC
Verified by the IBM Z team.
Ji Chen <jichenjc.com>

Moving it to verified.

Comment 4 errata-xmlrpc 2020-01-23 11:18:56 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.


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