Uploaded image for project: 'Machine Config Operator'
  1. Machine Config Operator
  2. MCO-1828

Fix pathological tests in the mco/disruptive suite

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • MCO Sprint 276, MCO Sprint 277
    • 0

      With the addition of the mco/disruptive suite we have observed that a few test cases generated by origin usually fail (example). The test cases are:

      • [sig-arch] events should not repeat pathologically for ns/openshift-dns (fails consistently)
      • [sig-arch] events should not repeat pathologically for ns/openshift-cluster-storage-operator (sometimes it passes)

      As we did with the container failures tests , we need to rework those tests that are not thought to play well with a disruptive suite to work in our suite. In this case the initial idea is not about removing them from the run, but finding a way to discard the pathological events triggered by reboot/drains in disruptive suites only.

              rh-ee-pabrodri Pablo Rodriguez Nava
              rh-ee-pabrodri Pablo Rodriguez Nava
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: