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

improve scaling strategy error message

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • 4.20.0
    • 4.18
    • Etcd
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • Done
    • Bug Fix
    • Hide
      In previous versions, during temporary downtime of the API server, the Cluster etcd Operator reported incorrect information, such as messages that the `openshift-etcd` namespace was non-existent. With this update, the Cluster etcd Operator status message now correctly indicates API server unavailability instead of suggesting the absence of the `openshift-etcd` namespace. As a result, the Cluster etcd Operator status now more accurately reflects the presence of the `openshift-etcd` namespace, enhancing system reliability.
      Show
      In previous versions, during temporary downtime of the API server, the Cluster etcd Operator reported incorrect information, such as messages that the `openshift-etcd` namespace was non-existent. With this update, the Cluster etcd Operator status message now correctly indicates API server unavailability instead of suggesting the absence of the `openshift-etcd` namespace. As a result, the Cluster etcd Operator status now more accurately reflects the presence of the `openshift-etcd` namespace, enhancing system reliability.
    • None
    • None
    • None
    • None

      Description of problem:

      When apiserver is not available briefly, the CEO status suggests that the openshift-etcd namespace does not exist:
      
      > EtcdEndpointsDegraded: EtcdEndpointsController can't evaluate whether quorum is safe: CheckSafeToScaleCluster failed to get bootstrap scaling strategy: failed to get openshift-etcd namespace: namespace "openshift-etcd" not found...
      
      which is evidently wrong, because the api has just responded with that exact status, which means etcd has returned this as a result.    
      
      We should reword this message to indicate the actual error.
      
      Code path is here:
      https://github.com/openshift/cluster-etcd-operator/blob/release-4.17/pkg/operator/ceohelpers/bootstrap.go#L120-L123

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

      any supported release 

      How reproducible:

      always    

      Steps to Reproduce:

          1. created some temporary downtime on apiserver
          2. check the CEO status using oc get co    

      Actual results:

      CEO returns "failed to get openshift-etcd namespace: namespace "openshift-etcd" not found."

      Expected results:

      CEO should not indicate that namespace is missing    

      Additional info:

          

              dwest@redhat.com Dean West
              tjungblu@redhat.com Thomas Jungblut
              None
              None
              Ge Liu Ge Liu
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: