-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.16
-
None
This is a clone of issue OCPBUGS-55373. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-54617. The following is the description of the original issue:
—
Description of problem:
- When provisioning Spot VM via Machineset ,if the cloud provider stops the VM between Machine gets provisioned and it joins to the cluster as Node , the machine remains powered-off (Deallocated in Azure clusters) causing machine-controller get stuck in a loop waiting machine to join the node: [controller.go:318] machine-name-xxxx: has no node yet, requeuing
Version-Release number of selected component (if applicable):
How reproducible:
Scale up a Spot
Steps to Reproduce:
1. 2. 3.
Actual results:
After machine joins as Node everithing works as expected and workloads are scheduled in surviving nodes.
Expected results:
If the SpotVM gets Deallocated during provisionig phase, openshift should reconcile the status of the machine-controller.
Additional info:
- blocks
-
OCPBUGS-56092 Spot Machine should be Failed if during provisioning Machine becomes Deallocated on Azure
-
- Closed
-
- clones
-
OCPBUGS-55373 Spot Machine should be Failed if during provisioning Machine becomes Deallocated on Azure
-
- Closed
-
- is blocked by
-
OCPBUGS-55373 Spot Machine should be Failed if during provisioning Machine becomes Deallocated on Azure
-
- Closed
-
- is cloned by
-
OCPBUGS-56092 Spot Machine should be Failed if during provisioning Machine becomes Deallocated on Azure
-
- Closed
-
- links to
-
RHBA-2025:7669 OpenShift Container Platform 4.17.z bug fix update