-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
4.12, 4.11
-
Critical
-
None
-
False
-
Description of problem:
Ignition failure takes the coreos VMs to emergency mode.
This happened on master and worker nodes of the OCP cluster.
Version-Release number of selected component (if applicable):
OCP 4.12 with RHCOS 4.12.86 image (https://releases-rhcos-art.cloud.privileged.psi.redhat.com/storage/releases/rhcos-4.12-ppc64le/412.86.202208090152-0/ppc64le/rhcos-412.86.202208090152-0-openstack.ppc64le.qcow2.gz)
How reproducible:
Always
Steps to Reproduce:
1. Use 4.12.0-ec.1 (https://mirror.openshift.com/pub/openshift-v4/ppc64le/clients/ocp/4.12.0-ec.1/) build to deploy the cluster.
use RHEL 8.6 image for creating bastion and RHCOS 412.86 image for creating coreos nodes.
Actual results:
VMs are not created properly. It fails at ignition and goes to emergency mode.
Attaching the logs from worker-1 node.
Expected results:
All the VMs should boot properly and OCP cluster installation should complete successfully.
Additional info: