Bug 1879121

Summary: [sig-network][Feature:Router] The HAProxy router should serve the correct routes when running with the haproxy config manager
Product: OpenShift Container Platform Reporter: Joseph Callen <jcallen>
Component: NetworkingAssignee: Stephen Greene <sgreene>
Networking sub component: router QA Contact: Hongan Li <hongli>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: medium CC: aos-bugs, bperkins, mfisher
Version: 4.6   
Target Milestone: ---   
Target Release: 4.7.0   
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][Feature:Router] The HAProxy router should serve the correct routes when running with the haproxy config manager
Last Closed: 2020-09-15 19:20:11 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 Joseph Callen 2020-09-15 13:36:50 UTC 
test:
[sig-network][Feature:Router] The HAProxy router should serve the correct routes when running with the haproxy config manager 

is failing 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%5C%5D%5C%5BFeature%3ARouter%5C%5D+The+HAProxy+router+should+serve+the+correct+routes+when+running+with+the+haproxy+config+manager


FIXME: Replace this paragraph with a particular job URI from the search results to ground discussion.  A given test may fail for several reasons, and this bug should be scoped to one of those reasons.  Ideally you'd pick a job showing the most-common reason, but since that's hard to determine, you may also chose to pick a job at random.  Release-gating jobs (release-openshift-...) should be preferred over presubmits (pull-ci-...) because they are closer to the released product and less likely to have in-flight code changes that complicate analysis.

FIXME: Provide a snippet of the test failure or error from the job log
Comment 1 mfisher 2020-09-15 16:06:03 UTC 
Target set to 4.7 while investigation is either ongoing or pending.  Will be considered for earlier release versions when diagnosed and resolved.