Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1868792

Summary: [4.3.z] Application behind service load balancer with PDB is not disrupted
Product: OpenShift Container Platform Reporter: Micah Abbott <miabbott>
Component: NetworkingAssignee: Antonio Ojea <aojeagar>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED NOTABUG Docs Contact:
Severity: medium    
Priority: medium CC: aconstan, amcdermo, aojeagar, aos-bugs, bbennett, ccoleman, hongkliu, mnewby, rkhan, skunkerk, vrutkovs, wking, zzhao
Version: 4.3.z   
Target Milestone: ---   
Target Release: 4.3.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: SDN-CI-IMPACT
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1868489 Environment:
Application behind service load balancer with PDB is not disrupted
Last Closed: 2020-09-03 17:12:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1868489, 1868490, 1886620    
Bug Blocks:    

Description Micah Abbott 2020-08-13 19:52:31 UTC 
+++ This bug was initially created as a clone of Bug #1868489 +++

test:
Application behind service load balancer with PDB is not disrupted 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=4.4&maxMatches=5&maxBytes=20971520&groupBy=job&search=Application+behind+service+load+balancer+with+PDB+is+not+disrupted

Additional info: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-azure-upgrade-4.4/1293537828600287232

--- Additional comment from W. Trevor King on 2020-08-12 22:27:59 UTC ---

Links a 4.4 example, so setting the target to 4.4.z and adjusting to only depend on the 4.5 bug 1868490.
Comment 1 Micah Abbott 2020-08-13 19:55:10 UTC 
Lots of evidence of this in the various 4.3 upgrade tests:

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.2-nightly-to-4.3-nightly/1293945736316063744

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.2-nightly-to-4.3-nightly/1293703890222452736

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.2-to-4.3/1293865209034706944

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.2-to-4.3-to-4.4-to-4.5-ci/1293778637308301312

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.2-to-4.3/1293764542450372608
Comment 2 Ben Bennett 2020-09-03 17:12:38 UTC 
We are not going to address this before 4.3 end-of-life.