-
Bug
-
Resolution: Unresolved
-
Normal
-
4.18
-
None
-
s390x
-
False
-
Context thread.
Description of problem:
Monitoring the 4.18 agent-based installer CI job for s390x (https://github.com/openshift/release/pull/50293) I discovered unexpected behavoir onces the installation triggers reboot into disk step for the 2nd and 3rd control plane nodes. (The first control plane node is rebooted last because it's also the bootstrap node). Instead of rebooting successully as expected, it fails to find the OSTree and drops to dracut, stalling the installation.
Version-Release number of selected component (if applicable):
OpenShift 4.18 on s390x only; discovered using agent installer
How reproducible:
Try to install OpenShift 4.18 using agent-based installer on s390x
Steps to Reproduce:
1. Boot nodes with XML (see attached) 2. Wait for installation to get to reboot phase.
Actual results:
Control plane nodes fail to reboot.
Expected results:
Control plane nodes reboot and installation progresses.
Additional info:
See attached logs.
- blocks
-
MULTIARCH-4687 Assisted Installer CI workflow for P/Z
- New
-
OCPBUGS-44904 RHCOS fails to reboot after disk install from agent based installer on s390x [4.18 only]
- POST
- is cloned by
-
OCPBUGS-44744 RHCOS fails to reboot after disk install from agent based installer on s390x [4.17]
- New
-
OCPBUGS-44904 RHCOS fails to reboot after disk install from agent based installer on s390x [4.18 only]
- POST
- relates to
-
OCPBUGS-44744 RHCOS fails to reboot after disk install from agent based installer on s390x [4.17]
- New
-
OCPBUGS-44904 RHCOS fails to reboot after disk install from agent based installer on s390x [4.18 only]
- POST
- links to
- mentioned on