*** Bug 1890011 has been marked as a duplicate of this bug. ***
*** Bug 1868490 has been marked as a duplicate of this bug. ***
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.
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"