Uploaded image for project: 'OpenShift Over the Air'
  1. OpenShift Over the Air
  2. OTA-980

Is the Failing=True status condition is a good indicator for admins?

    XMLWordPrintable

Details

    • Spike
    • Resolution: Unresolved
    • Major
    • None
    • None
    • None
    • 3
    • False
    • None
    • False
    • OTA 255

    Description

      Is the Failing=True status condition is a good indicator that admins should intervene. Can tracking % of clusters with the Failing=True status condition in the whole fleet give us a good indicator of overall success/failure rate for updates or generic (update and non-update) cluster health? Can we ask Webconsole to use the Failing=True status condition as the indicator for whether an upgrade is healthy or needs admin intervention?

      Definition of done:

      • Check the Failing=True status condition trend chart using superset dashboard and discuss with team.
      • Check CI to see how many clusters show Failing=True when there are failure expected as part of the test and discuss with team.
      • Create follow of cards to do the work to make tests should fail if they show Failing=True  status condition when failures are not expected as part of the test.

      Attachments

        Issue Links

          is blocked by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OTA-362 CI: fail update suite if any ClusterOperator go Available=False

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OTA-1087 Add Upgrade Health section to oc adm upgrade status command

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. TRT-1578 Ensure all HA components are not degraded by design during upgrades

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • New

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OTA-700 Ensure availability of all HA components during upgrades

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              lmohanty@redhat.com Lalatendu Mohanty
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: