Uploaded image for project: 'OCP Technical Release Team'
  1. OCP Technical Release Team
  2. TRT-1575

CI: fail update suite if any ClusterOperator go Degraded=True

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None

      These are alarming conditions which may frighten customers, and we don't want to see them in our own, controlled, repeatable update CI. This example job had logs like:

      Feb 18 21:11:25.799 E clusteroperator/openshift-apiserver changed Degraded to True: APIServerDeployment_UnavailablePod: APIServerDeploymentDegraded: 1 of 3 requested instances are unavailable for apiserver.openshift-apiserver ()

      And the job failed, but none of the failures were "something made openshift-apiserver mad enough to go Degraded".

      Definition of done:

      • Same as OTA-362
      • File bugs or the existing issues
      • If bug exists then add the tests to the exception list.
      • Unless tests are in exception list , they should fail if we see degraded != false.

            dperique@redhat.com Dennis Periquet
            lmohanty@redhat.com Lalatendu Mohanty
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: