-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.21.z
-
None
-
False
-
-
3
-
Moderate
-
None
-
x86_64
-
None
-
None
-
Metal Platform 285
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
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-worker-98rpp baremetal-ocp-worker-mbhbh]' reason: SyncingFailed status: "True" type: Degraded Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Always
Actual results:
Installation fails.
Expected results:
Installation successful.
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
- is duplicated by
-
OCPBUGS-77523 Openshift ABI multicluster installation on Baremetal platform fails with machine-api degraded and metal3 pod crashloopbackoff
-
- Closed
-
-
OCPBUGS-77524 Openshift ABI multicluster installation on Baremetal platform fails with machine-api degraded and metal3 pod crashloopbackoff
-
- Closed
-
-
OCPBUGS-77525 Openshift ABI multicluster installation on Baremetal platform fails with machine-api degraded and metal3 pod crashloopbackoff
-
- Closed
-
-
OCPBUGS-77526 Openshift ABI multicluster installation on Baremetal platform fails with machine-api degraded and metal3 pod crashloopbackoff
-
- Closed
-
-
OCPBUGS-77527 Openshift ABI multicluster installation on Baremetal platform fails with machine-api degraded and metal3 pod crashloopbackoff
-
- Closed
-
- links to