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

Bug 1861944

Summary: Regression: 1.19 applications behind service load balancer are disrupted during upgrade (was Failing e2e: 'Application behind service load balancer with PDB is not disrupted')
Product: OpenShift Container Platform Reporter: Maru Newby <mnewby>
Component: NetworkingAssignee: Stephen Greene <sgreene>
Networking sub component: router QA Contact: Hongan Li <hongli>
Status: CLOSED DUPLICATE Docs Contact:
Severity: urgent    
Priority: urgent CC: aos-bugs, bbennett, ccoleman, dhansen, vrutkovs, wking
Version: 4.6Keywords: Reopened, UpcomingSprint, Upgrades
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-14 21:15:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Maru Newby 2020-07-30 01:34:45 UTC
The following test is now skipped in origin's rules.go due to failing consistently on the gcp-upgrade

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

This test needs fixed and the skip removed asap.

Comment 1 Andrew McDermott 2020-07-30 08:15:47 UTC
(In reply to Maru Newby from comment #0)
> The following test is now skipped in origin's rules.go due to failing
> consistently on the gcp-upgrade

I must be missing the obvious. Which PR added the skip?

The last few commits in rules.go are:

$ git log --shortstat ./test/extended/util/annotate/rules.go
commit 05229dccd99dc286d630cda5093d38d6836fc8e1
Author: Maciej Szulik <maszulik>
Date:   Thu Jun 25 12:38:10 2020 +0200

    Bring back sig-cli tests

 1 file changed, 19 deletions(-)

commit 144c666acf185cc06d1e840175cc8b961df081d1 (from 0c123080cc637f0ee1770087c45109e9500f2f4c)
Merge: 0c123080cc b0aa6fbf3d
Author: OpenShift Merge Robot <openshift-merge-robot.github.com>
Date:   Wed May 27 15:15:52 2020 -0400

    Merge pull request #25012 from Gal-Zaidman/skip-network-tests
    
    Bug 1840707: oVirt, skip network service tests

 1 file changed, 6 insertions(+)


> 
> [sig-network-edge] Application behind service load balancer with PDB is not
> disrupted
> 
> This test needs fixed and the skip removed asap.

Comment 2 Andrew McDermott 2020-07-30 08:33:46 UTC
This looks to be a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1828858.

*** This bug has been marked as a duplicate of bug 1828858 ***

Comment 3 Maru Newby 2020-07-31 02:49:42 UTC
My apologies for not giving you enough context.

Example of failure on gcp-upgrade:

https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/25314/pull-ci-openshift-origin-master-e2e-gcp-upgrade/1288428932198043648

Skip was merged yesterday:

https://github.com/openshift/origin/pull/25314/commits/35927ea55554761c0a5c5034834a85a936672058

This bz was consistently failing the gcp-upgrade job, and I think it should be closed only when the above skip is removed.

Comment 4 Maru Newby 2020-07-31 03:03:40 UTC
er... s/bz was consistently failing the gcp-upgrade job/e2e test was consistently failing the gcp-upgrade job/

Comment 5 Andrew McDermott 2020-07-31 11:38:53 UTC
Need to see if https://github.com/openshift/kubernetes/pull/300 fixed this or whether commenting it out of the tests masks the issue. I had PRs in flight and not sure which change allowed won.

Added UpcomingSprint.

Comment 6 Daneyon Hansen 2020-08-13 16:32:32 UTC
@Andrew, please provide update when you return from PTO :-)

Comment 7 Andrew McDermott 2020-09-08 16:34:25 UTC
(In reply to Daneyon Hansen from comment #6)
> @Andrew, please provide update when you return from PTO :-)

The PR that I put together some time back wasn't a fix. I've since closed the PR so that it doesn't reflect that this bug was making progress.

Comment 8 Andrew McDermott 2020-09-10 11:39:09 UTC
Resetting status to NEW as the PR was closed in comment #7.

Comment 9 Andrew McDermott 2020-09-10 11:53:08 UTC
I’m adding UpcomingSprint, because I was occupied by fixing bugs with
higher priority/severity, developing new features with higher
priority, or developing new features to improve stability at a macro
level. I will revisit this bug next sprint.

Comment 10 Andrew McDermott 2020-09-14 17:42:52 UTC
Assigning to Steve to work through the issue.