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

Separate "Back-off restarting failed container" from pathological failures

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None
    • None

      The "[sig-arch] events should not repeat pathologically" test is a backstop test; one of the failures is like this:

      : [sig-arch] events should not repeat pathologically expand_less    0s{  2 events happened too frequently
      event happened 56 times, something is wrong: ns/openshift-cluster-csi-drivers pod/gcp-pd-csi-driver-controller-6747df4b84-bc96x node/ci-op-5nx16hrj-d3bee-4jzmr-master-1 - reason/BackOff Back-off restarting failed containerevent happened 78 times, something is wrong: ns/openshift-cluster-csi-drivers pod/gcp-pd-csi-driver-controller-6747df4b84-qjf5g node/ci-op-5nx16hrj-d3bee-4jzmr-master-2 - reason/BackOff Back-off restarting failed container} 

      from https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.11-e2e-gcp-upgrade/1517293457620602880 and which is part of https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/aggregated-gcp-sdn-upgrade-4.11-micro-release-openshift-release-analysis-aggregator/1517293463496822784

      The goal of this card is to separate out that test.

              dperique@redhat.com Dennis Periquet
              dperique@redhat.com Dennis Periquet
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: