-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.13
-
None
-
Important
-
None
-
8
-
Sprint 232, Sprint 233, Sprint 234
-
3
-
Rejected
-
False
-
-
NA
-
Release Note Not Required
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
- depends on
-
TRT-812 Add a periodic for gcp ovn micro upgrades
- Closed
-
TRT-813 Audit disruption fallbacks for safety/accuracy
- Closed
- is related to
-
OCPBUGS-6947 Ingress Takes 40s on Average Downtime During GCP OVN Upgrades
- Closed
- links to