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.
(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.
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 ***
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.
er... s/bz was consistently failing the gcp-upgrade job/e2e test was consistently failing the gcp-upgrade job/
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.
@Andrew, please provide update when you return from PTO :-)
(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.
Resetting status to NEW as the PR was closed in comment #7.
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.
Assigning to Steve to work through the issue.