Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-5452

Taking much time to update node count for MCP

    XMLWordPrintable

Details

    • MCO Sprint 247, MCO Sprint 248
    • 2
    • False
    • Hide

      None

      Show
      None
    • the MCO does not support managing nodes when they are not in a pool. If a node has been removed from all pools we should log an error.
    • Bug Fix
    • In Progress

    Description

      Description of problem:

      MCO taking too much time to update the node count for MCP when removing labels from node which MCP uses to match with nodes

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

       

      How reproducible:

      100%

      Steps to Reproduce:

      1. Remove `node-role.kubernetes.io/worker=` label from any worker node.
~~~
# oc label node worker-0.sharedocp4upi411ovn.lab.upshift.rdu2.redhat.com node-role.kubernetes.io/worker-
~~~
2. Check MCP worker for correct node count.
~~~
# oc get mcp  worker
NAME     CONFIG                                             UPDATED   UPDATING   DEGRADED   MACHINECOUNT   READYMACHINECOUNT   UPDATEDMACHINECOUNT   DEGRADEDMACHINECOUNT   AGE
worker   rendered-worker-6916abae250ad092875791f8297c13e1   True      False      False      3              3                   3                     0                      5d7h
~~~
3. Check after 10-15 mins
~~~
# oc get mcp  worker NAME     CONFIG                                             UPDATED   UPDATING   DEGRADED   MACHINECOUNT   READYMACHINECOUNT   UPDATEDMACHINECOUNT   DEGRADEDMACHINECOUNT   AGE worker   rendered-worker-6916abae250ad092875791f8297c13e1   True      False      False      2              2                   2                     0                      5d7h
~~~

      Actual results:

      It took 10-15 mins for MCP to detect node removal.

      Expected results:

      It should detect node removal as soon as the appropriate label from the node gets missing.

      Additional info:

       

      Attachments

        Issue Links

          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MCO-452 [tech-preview] Proper state reporting when the MCO changes state

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          GitHub openshift/machine-config-operator#4097: OCPBUGS-5452: If node is not in pool, error

          Web Link RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update

          Activity

            People

              cdoern@redhat.com Charles Doern
              rhn-support-dpateriy Divyam Pateriya
              Rio Liu Rio Liu
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: