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

ClusterOperator authentication should not blip Available=False during upgrade

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.21
    • apiserver-auth
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This bug has similar symptom as OCPBUGS-32089.

      It happens in upgrade to 4.21 as well.

      Failure job 1:

      : [Monitor:legacy-cvo-invariants][bz-apiserver-auth] clusteroperator/authentication should not change condition/Available expand_less1h45m8s{  2 unexpected clusteroperator state transitions during e2e test run.  These did not match any known exceptions, so they cause this test-case to fail:
      
      Nov 25 11:05:47.396 E clusteroperator/authentication condition/Available reason/OAuthServerDeployment_PreconditionNotFulfilled status/False
      Nov 25 11:05:47.396 - 8s    E clusteroperator/authentication condition/Available reason/OAuthServerDeployment_PreconditionNotFulfilled status/False
      
      1 unwelcome but acceptable clusteroperator state transitions during e2e test run.  These should not happen, but because they are tied to exceptions, the fact that they did happen is not sufficient to cause this test-case to fail:
      
      Nov 25 11:05:55.471 W clusteroperator/authentication condition/Available reason/AsExpected status/True All is well (exception: Available=True is the happy case)
      } 

      Failure job2:

      : [Monitor:legacy-cvo-invariants][bz-apiserver-auth] clusteroperator/authentication should not change condition/Available expand_lessRun #0: Failed expand_less1h45m19s{  0 unexpected clusteroperator state transitions during e2e test run, as desired.
      6 unwelcome but acceptable clusteroperator state transitions during e2e test run.  These should not happen, but because they are tied to exceptions, the fact that they did happen is not sufficient to cause this test-case to fail:
      
      Nov 24 22:56:29.660 E clusteroperator/authentication condition/Available reason/APIServices_Error status/False APIServicesAvailable: apiservices.apiregistration.k8s.io/v1.oauth.openshift.io: not available: failing or missing response from https://10.128.0.129:8443/apis/oauth.openshift.io/v1: Get "https://10.128.0.129:8443/apis/oauth.openshift.io/v1": context deadline exceeded (exception: https://issues.redhat.com/browse/OCPBUGS-20056)
      Nov 24 22:56:29.660 - 356ms E clusteroperator/authentication condition/Available reason/APIServices_Error status/False APIServicesAvailable: apiservices.apiregistration.k8s.io/v1.oauth.openshift.io: not available: failing or missing response from https://10.128.0.129:8443/apis/oauth.openshift.io/v1: Get "https://10.128.0.129:8443/apis/oauth.openshift.io/v1": context deadline exceeded (exception: https://issues.redhat.com/browse/OCPBUGS-20056)
      Nov 24 22:56:30.017 W clusteroperator/authentication condition/Available reason/AsExpected status/True All is well (exception: Available=True is the happy case)
      Nov 24 22:56:44.655 E clusteroperator/authentication condition/Available reason/APIServices_Error status/False APIServicesAvailable: apiservices.apiregistration.k8s.io/v1.oauth.openshift.io: not available: failing or missing response from https://10.128.0.129:8443/apis/oauth.openshift.io/v1: Get "https://10.128.0.129:8443/apis/oauth.openshift.io/v1": context deadline exceeded (exception: https://issues.redhat.com/browse/OCPBUGS-20056)
      Nov 24 22:56:44.655 - 126ms E clusteroperator/authentication condition/Available reason/APIServices_Error status/False APIServicesAvailable: apiservices.apiregistration.k8s.io/v1.oauth.openshift.io: not available: failing or missing response from https://10.128.0.129:8443/apis/oauth.openshift.io/v1: Get "https://10.128.0.129:8443/apis/oauth.openshift.io/v1": context deadline exceeded (exception: https://issues.redhat.com/browse/OCPBUGS-20056)
      Nov 24 22:56:44.781 W clusteroperator/authentication condition/Available reason/AsExpected status/True All is well (exception: Available=True is the happy case)
      } 

              Unassigned Unassigned
              hongkliu Hongkai Liu
              None
              None
              Xingxing Xia Xingxing Xia
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: