-
Bug
-
Resolution: Unresolved
-
Major
-
4.19
-
None
-
1
-
Metal Platform 267
-
1
-
Approved
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
While creating the provisioning resource on UPI cluster of 4.19, the metal3 pods fail to come up, because the init-container machine-os-images fails.
Version-Release number of selected component (if applicable):
4.19.0-0.nightly-arm64-2025-02-14-044543
How reproducible:
always in arm64 cluster
Steps to Reproduce:
1. On a UPI cluster create provisioning resource
2. Check the pods being created on openshift-machine-api namespace
Actual results:
$ cat provisioning-upi.yaml
apiVersion: metal3.io/v1alpha1
kind: Provisioning
metadata:
name: provisioning-configuration
spec:
provisioningNetwork: "Disabled"
watchAllNamespaces: false
$ oc get pods -n openshift-machine-api
NAME READY STATUS RESTARTS AGE
cluster-autoscaler-operator-fd96c97bf-psbt7 2/2 Running 1 (82m ago) 91m
cluster-baremetal-operator-fb7cbbb65-dp7zb 2/2 Running 1 (82m ago) 92m
control-plane-machine-set-operator-68596d754-ckfwq 1/1 Running 1 (82m ago) 91m
ironic-proxy-j7whx 1/1 Running 0 28s
ironic-proxy-nchz6 1/1 Running 0 28s
ironic-proxy-wjgj6 1/1 Running 0 28s
machine-api-operator-7dcd67759b-nqnv8 2/2 Running 0 92m
metal3-5d77cd875-xpcsf 0/3 Init:CrashLoopBackOff 1 (6s ago) 34s
metal3-baremetal-operator-9b465b848-j2ztt 1/1 Running 0 33s
metal3-image-customization-767bd55db5-49pnn 0/1 Init:CrashLoopBackOff 1 (5s ago) 29s
$ oc logs -f metal3-image-customization-767bd55db5-49pnn machine-os-images -n openshift-machine-api
extracting PXE files...
/shared/html/images/coreos-aarch64-initrd.img
/shared/html/images/coreos-aarch64-rootfs.img
/shared/html/images/coreos-aarch64-vmlinuz
gzip: /shared/html/images/coreos-aarch64-vmlinuz.gz: not in gzip format
Expected results:
All 3 metal pods should be in Running state
- depends on
-
-
- Verified
-
- links to
