-
Bug
-
Resolution: Done
-
Major
-
4.13
-
None
-
Important
-
No
-
False
-
Description of problem:
Agent based installation is stuck on the booting screen for the arm64 SNO cluster.
The installer shuold validate the architecture set by the users in the install-config.yaml with the payload image being used.
Version-Release number of selected component (if applicable):
4.13
How reproducible:
100%
Steps to Reproduce:
[Fixed original version] 1. Create agent ISO with the amd64 payload 2. Boot the created ISO on arm64 server 3. Monitor the booting screen for error [Generalized] 1. Set the install-config.yaml controlPlane.architecture to arm64 2. Try to install with an
Actual results:
The installation is currently stuck on the initial booting screen.
Expected results:
The SNO cluster should be installed without any issues.
Additional info:
Compact cluster installation was successful, here is the prow ci link: https://gcsweb-qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/qe-private-deck/logs/periodic-ci-openshift-openshift-tests-private-release-4.13-arm64-nightly-baremetal-compact-agent-ipv4-static-connected-p1-f7/1665833590451081216/artifacts/baremetal-compact-agent-ipv4-static-connected-p1-f7/baremetal-lab-agent-install/build-log.txt
- is caused by
-
OCPBUGS-19037 agent-tui failure blocks ssh + console login
- Closed
- links to