Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-1083

e2e-aws-ovn-serial fails because of OVNKubernetesControllerDisconnectedSouthboundDatabase

XMLWordPrintable

    • SDN Sprint 225, SDN Sprint 226
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      OVNKubernetesControllerDisconnectedSouthboundDatabase alert seems to fire in the e2e-aws-ovn-serial CI job. Note that something funny happens in the job itself, which is that a set of ovnkube-node pods get created and then deleted and then get recreated again and test runs. But the alert gets fired for the first set of pods that got deleted. From the initial screening of artifacts alone its not clear what happened to the old pods. This needs investigation

      Version-Release number of selected component (if applicable):

      4.12 OCP

      How reproducible:

      Seems like always

      Steps to Reproduce:

      1.https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/27043/pull-ci-openshift-origin-master-e2e-aws-ovn-serial/1568166237639282688
      2. https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/27043/pull-ci-openshift-origin-master-e2e-aws-ovn-serial/1567913444936519680
      

      Actual results:

      Alert is fired

      Expected results:

      Alert shouldn't be fired and this is expected in the serial job then we need to silence that alert for that job, make it flaky and not fail hard if that alert fires.

      Additional info:

       

            npinaeva@redhat.com Nadia Pinaeva
            sseethar Surya Seetharaman
            Anurag Saxena Anurag Saxena
            Votes:
            2 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: