Bug 1932493 - [sig-network-edge] Application behind service load balancer with PDB is not disrupted
Summary: [sig-network-edge] Application behind service load balancer with PDB is not d...
Keywords:
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Routing
Version: 4.6
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: 4.6.z
Assignee: aos-network-edge-staff
QA Contact: Hongan Li
URL:
Whiteboard:
: 1955662 (view as bug list)
Depends On: 1929396 1932629
Blocks: 1932491
TreeView+ depends on / blocked
 
Reported: 2021-02-24 17:59 UTC by Jon Jackson
Modified: 2021-06-11 23:02 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1929396
Environment:
[sig-network-edge] Application behind service load balancer with PDB is not disrupted job=periodic-ci-openshift-release-master-nightly-4.6-e2e-metal-ipi-upgrade=all
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Jon Jackson 2021-02-24 17:59:54 UTC
+++ This bug was initially created as a clone of Bug #1929396 +++

test:
[sig-network-edge] Application behind service load balancer with PDB is not disrupted 

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

Pass rate 50% on gcp according to sippy

Example:
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-ovn-upgrade-4.5-stable-to-4.6-ci/1361717216143216640

disruption_tests: [sig-network-edge] Application behind service load balancer with PDB is not disrupted expand_less
Run #0: Failed expand_less	1h11m46s
Service was unreachable during disruption for at least 9s of 1h8m31s (0%), this is currently sufficient to pass the test/job but not considered completely correct:

Feb 16 17:59:45.229 E ns/e2e-k8s-service-lb-available-1335 svc/service-test Service stopped responding to GET requests over new connections
Feb 16 17:59:46.229 - 5s    E ns/e2e-k8s-service-lb-available-1335 svc/service-test Service is not responding to GET requests over new connections
Feb 16 17:59:52.690 I ns/e2e-k8s-service-lb-available-1335 svc/service-test Service started responding to GET requests over new connections
Feb 16 18:01:44.229 E ns/e2e-k8s-service-lb-available-1335 svc/service-test Service stopped responding to GET requests over new connections
Feb 16 18:01:44.414 I ns/e2e-k8s-service-lb-available-1335 svc/service-test Service started responding to GET requests over new connections
Feb 16 18:18:00.411 E ns/e2e-k8s-service-lb-available-1335 svc/service-test Service stopped responding to GET requests over new connections
Feb 16 18:18:01.229 E ns/e2e-k8s-service-lb-available-1335 svc/service-test Service is not responding to GET requests over new connections
Feb 16 18:18:01.401 I ns/e2e-k8s-service-lb-available-1335 svc/service-test Service started responding to GET requests over new connections
Run #1: Passed expand_more

--- Additional comment from Miciah Dashiel Butler Masters on 2021-02-18 12:22:33 EST ---

From the Sippy results, I don't see a 50% failure rate.  Note that the Sippy link provided includes test runs where the test did not exceed the threshold to cause a failure.  Ryan will investigate to determine the actual failure rate and severity of the issue.

Comment 2 Candace Holman 2021-04-30 16:20:37 UTC
*** Bug 1955662 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.