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

[4.19 Backport] Use kube_statefulset_replicas for KubeStatefulSetReplicasMismatch

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • 4.19.z
    • 4.10.z
    • Monitoring
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 3
    • None
    • None
    • None
    • None
    • MON Sprint 278
    • 1
    • In Progress
    • Bug Fix
    • Hide
      KubeStatefulSetReplicasMismatch alert now fires on pod creation failure::
      Before this update, the `KubeStatefulSetReplicasMismatch` alert did not fire when the StatefulSet controller failed to create pods. As a consequence, users were not notified when the StatefulSet did not reach the desired number of replicas. With this release, the alert now fires correctly when the controller cannot create pods. As a result, users are alerted whenever the StatefulSet replicas do not match the configured amount.
      +
      link:https://issues.redhat.com/browse/OCPBUGS-60689[OCPBUGS-60689]
      Show
      KubeStatefulSetReplicasMismatch alert now fires on pod creation failure:: Before this update, the `KubeStatefulSetReplicasMismatch` alert did not fire when the StatefulSet controller failed to create pods. As a consequence, users were not notified when the StatefulSet did not reach the desired number of replicas. With this release, the alert now fires correctly when the controller cannot create pods. As a result, users are alerted whenever the StatefulSet replicas do not match the configured amount. + link: https://issues.redhat.com/browse/OCPBUGS-60689 [ OCPBUGS-60689 ]
    • None
    • None
    • None
    • None

      Description of problem:

          kube_statefulset_status_replicas returns "the number of Pods created by the StatefulSet controller". Therefore this alert only fires when the StatefulSet controller is able to create the pod, but it does not get ready.In cases where the controller is unable to create the pod (e.g. invalid pod spec) this alert does not fire. This is contrary to the expectation of firing when the statefulset does not match the configured amount of replicas.

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

      How reproducible:

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

      Expected results:

      Additional info:

          Setting affected version to 4.10.z, since that's as far back as it goes, but this first surfaced in 4.1 (Feb, 2020): https://github.com/aeber/kubernetes-mixin/commit/e748721881c2c752fb5b90d81467b7d9efc91c36.

              prasriva@redhat.com Pranshu Srivastava
              prasriva@redhat.com Pranshu Srivastava
              None
              None
              Junqi Zhao Junqi Zhao
              Eliska Romanova Eliska Romanova
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: