[OCPBUGS-48814] Cloud Controller manager adds the uninitialized taint to the Infra node in the fresh Azure IPI cluster - Red Hat Issue Tracker

Type: Bug
Resolution: Not a Bug
Priority: Minor
Fix Version/s: None
Affects Version/s: 4.16.z
Component/s: Cloud Compute / Cloud Controller Manager
Labels:
None

Regression:
None
Blocked:
False
Blocked Reason:

Hide

None

Show
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Impact Score:

Description of problem:

    A newly created OCP 4.16.8 Azure IPI cluster is getting the following taints:

effect: NoSchedule
key: node.cloudprovider.kubernetes.io/uninitialized
value: "true"

This causes infra workloads like "ingress router" pod scheduling issues(It goes into the pending state).

Version-Release number of selected component (if applicable):

How reproducible:

    Always with OCP 4.16.8 Azure IPI cluster.

Steps to Reproduce:

    1.
    2.
    3.

Actual results:

    Ingress router pods are not getting scheduled to infra nodes.

Expected results:

    Infra nodes should be schedulable for infra workloads.

Additional info:

A similar BUG was noticed after the upgrade from 4.12.26 to 4.14.16.

BUG: https://issues.redhat.com/browse/OCPBUGS-33405

Assignee:: Joel Speed

Reporter:: Sameer Sardar

QA Contact:: Zhaohua Sun

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2025/01/23 7:12 PM

Updated:: 2025/02/24 11:49 AM

Resolved:: 2025/02/24 11:49 AM