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

Disruption Automated Test Data Update Stuck for a Month

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • 4.15.0
    • None
    • None
    • False
    • None
    • False

      https://github.com/openshift/origin/pull/28360

      Failing unit tests.

      Every row has MasterNodesUpdated null, might have something to do with it. Fix would be in ci-tools.

            [TRT-1362] Disruption Automated Test Data Update Stuck for a Month

            Devan Goodwin added a comment -

            MasterNodesUpdated is null, but perhaps this was always the case for ALERT data, it's not that way for disruption data, so that could be addressed but it doesn't seem to be the root cause here.

            It looks like we don't see the data because of just 84 job runs. We're supposed to record 0s for every alert combo, as soon as we've seen it once in that release. This particular alert we're looking for in the unit test fires for every ci job run, so why would we only have 84 results in 4.15?

            Devan Goodwin added a comment - MasterNodesUpdated is null, but perhaps this was always the case for ALERT data, it's not that way for disruption data, so that could be addressed but it doesn't seem to be the root cause here. It looks like we don't see the data because of just 84 job runs. We're supposed to record 0s for every alert combo, as soon as we've seen it once in that release. This particular alert we're looking for in the unit test fires for every ci job run, so why would we only have 84 results in 4.15?

              rhn-engineering-dgoodwin Devan Goodwin
              rhn-engineering-dgoodwin Devan Goodwin
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: