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

consistent router test failure on gcp-ovn-upgrade jobs

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 4.13
    • Networking / router
    • None
    • Important
    • 8
    • Sprint 232, Sprint 233, Sprint 234
    • 3
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • NA
    • Release Note Not Required

    Description

      Description of problem:

      "Application behind service load balancer with PDB remains available using new connections" is consistently failing for multiple PRs that do not touch this space.  See:

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

sample failure:
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/27679/pull-ci-openshift-origin-master-e2e-gcp-ovn-upgrade/1619613372049788928

also failing on this PR:
https://github.com/openshift/origin/pull/27654

Marking as a blocker since we need this resolved to unstick PRs. (though we will override as needed for now, since we now have a tracker bug)

       

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

      4.13

      How reproducible:

      seems to always fail in test jobs

      Steps to Reproduce:

      1. run the ovn-gcp-upgrade test job against master (4.13) in origin
2.
3.

      Actual results:

      test fails

      Expected results:

      test succeeds

      Additional info:

      has been failing since at least jan 26th:
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/27679/pull-ci-openshift-origin-master-e2e-gcp-ovn-upgrade/1618724533357776896

       

      Attachments

        Issue Links

          depends on

          Story - Used to indicate the smallest unit of work for a team to complete and is end user-facing. Created by Jira Software - do not edit or delete. TRT-812 Add a periodic for gcp ovn micro 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

          Story - Used to indicate the smallest unit of work for a team to complete and is end user-facing. Created by Jira Software - do not edit or delete. TRT-813 Audit disruption fallbacks for safety/accuracy

          • 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.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-6947 Ingress Takes 40s on Average Downtime During GCP OVN Upgrades

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          links to

          Web Link [DownstreamMerge] 2-28-23

          Web Link node: add node healthz server for cloud load balancers

          Activity

            People

              cholman@redhat.com Candace Holman
              bparees@redhat.com Ben Parees
              Shudi Li Shudi Li
              Riccardo Ravaioli
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated: