Uploaded image for project: 'OpenShift Monitoring'
  1. OpenShift Monitoring
  2. MON-1842

OCP cluster reports wrong number of worker nodes

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Duplicate
    • Icon: Normal Normal
    • None
    • None
    • None
    • False
    • False
    • NEW
    • NEW
    • Undefined

      Description of problem:
      When tagging the server as infra node-role.kubernetes.io/infra: "", the same still present as worker node. We can see the same in the cluster dashboard as part of worker instead of control plane.

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

      How reproducible:
      100%

      Steps to Reproduce:
      1. create the ocp cluster (using core os)
      2. configure the telemetry and push all the info to cloud.redhat.com
      3. analyze the data via cluster page
      4. change the tag on the worker node to infra

      Actual results:
      The information still the same

      Expected results:
      The # of control plane and workers should change

      Additional info:
      If we move from infra to master, voilรก, we can see the control plane increasing and the workers decreasing.

      Seems like OCP cluster that got a node switched to a worker node, does not sync the correct number of worker nodes to OCM.

      Reported in https://bugzilla.redhat.com/show_bug.cgi?id=1975165

        1. oc_get_nodes_5controllers_1worker.png
          oc_get_nodes_5controllers_1worker.png
          56 kB
        2. new_01.png
          new_01.png
          80 kB
        3. cluster_page_4controllers_2workers.png
          cluster_page_4controllers_2workers.png
          112 kB

            [MON-1842] OCP cluster reports wrong number of worker nodes

            Jan Fajerski added a comment -

            See duplicates link

            Jan Fajerski added a comment - See duplicates link

            Jan Fajerski added a comment -

            hasun@redhat.com This sounds similar as the linked bug you're working on. Wdyt?

            Jan Fajerski added a comment - hasun@redhat.com This sounds similar as the linked bug you're working on. Wdyt?

            Arunprasad Rajkumar (Inactive) added a comment -

            spasquie@redhat.com, We can take it up.

            Arunprasad Rajkumar (Inactive) added a comment - spasquie@redhat.com , We can take it up.

            Simon Pasquier added a comment -

            Yes please. arajkumar pgough@redhat.com is it something you can looked into once wpinheir has a reproducer?

            Simon Pasquier added a comment - Yes please. arajkumar pgough@redhat.com is it something you can looked into once wpinheir has a reproducer?

            Waldirio Pinheiro added a comment -

            Hello spasquie@redhat.com ,

             

            My cluster is gone, but it's easy to reproduce. Please, let me know if you still needing it, if yes, I'll be working on it.

             

            Thank you

            Waldirio

            Waldirio Pinheiro added a comment - Hello spasquie@redhat.com ,   My cluster is gone, but it's easy to reproduce. Please, let me know if you still needing it, if yes, I'll be working on it.   Thank you Waldirio

            Simon Pasquier added a comment -

            wpinheir do you still see the issue? If yes can we get access to a cluster exhibiting the problem?

            Simon Pasquier added a comment - wpinheir do you still see the issue? If yes can we get access to a cluster exhibiting the problem?

            Timothy Williams added a comment -

            vkarehfa this likely belongs with lserven@redhat.com and the telemetry team. Probably ping in #forum-telemetry, I think Lucas is on PTO.

            Timothy Williams added a comment - vkarehfa this likely belongs with lserven@redhat.com and the telemetry team. Probably ping in #forum-telemetry, I think Lucas is on PTO.

            Victor Kareh added a comment -

            jlucky@redhat.com any chance we can move this to a more relevant team? OCM is reporting the data as it comes from telemetry and we have no insight on the source of this data from the OCM point of view.

            Victor Kareh added a comment - jlucky@redhat.com any chance we can move this to a more relevant team? OCM is reporting the data as it comes from telemetry and we have no insight on the source of this data from the OCM point of view.

            Elad Tabak added a comment -

            vkarehfa any update on this?

            Elad Tabak added a comment - vkarehfa  any update on this?

            Victor Kareh added a comment -

            I don't have a contact, but according to the config manifest: https://github.com/openshift/cluster-monitoring-operator/blob/master/manifests/0000_50_cluster-monitoring-operator_04-config.yaml#L133 there is a GitHub team https://github.com/orgs/openshift/teams/openshift-team-olm/members that either owns or is subscribed to that metric, but I'm not entirely sure.

            Victor Kareh added a comment - I don't have a contact, but according to the config manifest: https://github.com/openshift/cluster-monitoring-operator/blob/master/manifests/0000_50_cluster-monitoring-operator_04-config.yaml#L133 there is a GitHub team https://github.com/orgs/openshift/teams/openshift-team-olm/members that either owns or is subscribed to that metric, but I'm not entirely sure.

              arajkumar Arunprasad Rajkumar (Inactive)
              rhn-support-wpinheir Waldirio Pinheiro
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: