-
Bug
-
Resolution: Done
-
Major
-
None
-
4.17.0
-
None
-
Important
-
None
-
Installer (PB) Sprint 259, Installer Sprint 260
-
2
-
Rejected
-
False
-
Description of problem:
Day2 add node with oc binary is not working with multi payload on baremetal CI running
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. Running compact agent installation on amd64 platform 2. After the cluster is ready, run day2 install on arm64 worker node 3. After booting the node.aarch64.iso, there is error message: Extract the latest oc client... Create node.iso for day2 worker nodes... Copying the day2 node ISO image into the bastion host... stat local "/tmp/installer_day2/node.aarch64.iso": No such file or directory {"component":"entrypoint","error":"wrapped process failed: exit status 255","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2024-10-08T07:52:24Z"}12error: failed to execute wrapped command: exit status 255
Actual results:
Day2 install fail
Expected results:
Day2 install success.
Additional info:
https://qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/qe-private-deck/pr-logs/pull/openshift_release/57568/rehearse-57568-periodic-ci-openshift-openshift-tests-private-release-4.18-multi-nightly-baremetal-compact-agent-ipv4-dhcp-day2-amd-mixarch-f14/1843545260576215040
- clones
-
OCPBUGS-38450 Day2 add node with oc binary is not working on ARM64
- Closed
- links to