Bug 1886620
| Summary: | Application behind service load balancer with PDB is not disrupted | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Benjamin Gilbert <bgilbert> |
| Component: | Networking | Assignee: | Antonio Ojea <aojeagar> |
| Networking sub component: | openshift-sdn | QA Contact: | zhaozhanqi <zzhao> |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | urgent | CC: | aconstan, amcdermo, anbhat, aojeagar, aos-bugs, bbennett, bgilbert, bparees, ccoleman, deads, dgoodwin, dmellado, hongkliu, huirwang, mnewby, rkhan, skunkerk, vrutkovs, wking, zzhao |
| Version: | 4.7 | Keywords: | Reopened, Upgrades |
| Target Milestone: | --- | ||
| Target Release: | 4.7.0 | ||
| 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: | 1828858 | Environment: |
Application behind service load balancer with PDB is not disrupted
|
| Last Closed: | 2021-01-13 15:23:26 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: | |||
| Bug Blocks: | 1868489, 1868490, 1868792, 1891711 | ||
|
Comment 4
Andrew McDermott
2020-10-21 10:22:49 UTC
*** Bug 1868490 has been marked as a duplicate of this bug. *** Hi, Antonio I just checked the scenario [sig-network-edge] Application behind service load balancer with PDB is not disrupted still in flaky list in the following 4.6 to 4.7 upgrade testing, As my understanding, it should be in pass list if this fixed. please correct me if I'm wrong, thanks. https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-upgrade-4.6-stable-to-4.7-ci/1325382252095344640 That failure mentioned there should be a pass > Service was unreachable during disruption for at least 4s of 50m15s (0%), this is currently sufficient to pass the test/job but not considered completely correct: As I commented in https://bugzilla.redhat.com/show_bug.cgi?id=1886620#c2, one of the probes has a minimal disruption (the one that create a new connection per each probe) and this must be related to something environmental, because the other probe (the on that does not create newer connections) never fails, that means that connectivity is ok @Antonio Ojea thanks the explanation. This doesn´t target a public release, is a test only fix Closing per https://source.redhat.com/groups/public/atomicopenshift/atomicopenshift_wiki/openshift_container_platform_bug_owner_responsibilities Else: AFTER the bug is VERIFIED by QA and only if the bug does not affect a publicly released version of the product it should simply be marked "CLOSED / CURRENTRELEASE" |