-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
4.21.z
-
None
-
None
-
False
-
-
None
-
Moderate
-
None
-
x86_64
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Agent-Based Installation on Bare Metal platform fails with the machine-api operator degraded due to "SyncingFailed"
- lastTransitionTime: "2026-03-02T03:53:33Z" message: 'Failed when progressing towards operator: 4.21.1 because minimum worker replica count (2) not yet met: current running replicas 0, waiting for [baremetal-ocp-rcb8h-worker-0-98rpp baremetal-ocp-rcb8h-worker-0-mbhbh]' reason: SyncingFailed status: "True" type: Degraded Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. $./oc version Client Version: 4.21.1 Kustomize Version: v5.7.1$ $./openshift-install version ./openshift-install 4.21.1built from commit 2c105c33e9e373b6e66c9ef8814f78a72539ae53release image quay.io/openshift-release-dev/ocp-release@sha256:7ca8870aa5e505f969aa26161594a3f99b65baf7d29bab8adaca0cade51b0bb6release architecture amd64 2. Create install-config and agent-config yaml with baremtal platform. 3./openshift-install agent create image --dir . --log-level=debugDEBUG 4. Boot the nodes with agent iso 5. ./openshift-install agent wait-for bootstrap-complete --dir . --log-level=debug
Actual results:
Installation fails.
Expected results:
Installation completed successfully
Additional info:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html/installing_an_on-premise_cluster_with_the_agent-based_installer/installing-with-agent-based-installer#installing-ocp-agent_installing-with-agent-based-installer
- duplicates
-
OCPBUGS-77528 Openshift ABI multicluster installation on Baremetal platform fails with machine-api degraded and metal3 pod crashloopbackoff
-
- POST
-