Bug 1831684

Summary: [sig-network] Services [Top Level] [sig-network] Services should be rejected when no endpoints exist [Skipped:Network/OVNKubernetes] [Suite:openshift/conformance/parallel] [Suite:k8s]
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: NetworkingAssignee: Ben Bennett <bbennett>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED DUPLICATE Docs Contact:
Severity: urgent    
Priority: urgent CC: aconstan, ccoleman, sdodson, vlaad, wking
Version: 4.4   
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
[sig-network] Services [Top Level] [sig-network] Services should be rejected when no endpoints exist [Skipped:Network/OVNKubernetes] [Suite:openshift/conformance/parallel] [Suite:k8s]
Last Closed: 2020-05-07 14:09:29 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:
Bug Depends On: 1781575, 1832332, 1834184    
Bug Blocks:    

Description Scott Dodson 2020-05-05 13:39:52 UTC
test:
[sig-network] Services [Top Level] [sig-network] Services should be rejected when no endpoints exist [Skipped:Network/OVNKubernetes] [Suite:openshift/conformance/parallel] [Suite:k8s] 

is failing frequently in CI, see search results:
https://search.svc.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-network%5C%5D+Services+%5C%5BTop+Level%5C%5D+%5C%5Bsig-network%5C%5D+Services+should+be+rejected+when+no+endpoints+exist+%5C%5BSkipped%3ANetwork%2FOVNKubernetes%5C%5D+%5C%5BSuite%3Aopenshift%2Fconformance%2Fparallel%5C%5D+%5C%5BSuite%3Ak8s%5C%5D

Comment 2 Clayton Coleman 2020-05-05 20:18:31 UTC
This failure means that a fundamental part of the product stopped working if the flake rate suddenly spiked.  If the flake rate is low, disabling the test isn't hte right approach, it's finding out why it is failing.  If the 4.4 promote test is failing, that means RHEL regressed us.

Comment 3 Scott Dodson 2020-05-07 00:07:11 UTC
RHCOS 8.2 rebase was rolled back, this should no longer fail. Unsure what SDN team would like to do with this bug so leaving it as is.

Comment 4 Alexander Constantinescu 2020-05-07 14:09:29 UTC
Hi 

I am closing this as a dupe of 1832332, since we have multiple bugs assigned to us for this e2e test failure and all link to that bug as well. 

/Alex

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