Bug 1780794
Summary: | Router emits unhelpful "another route has claimed this host" log messages | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Miciah Dashiel Butler Masters <mmasters> |
Component: | Networking | Assignee: | Dan Mace <dmace> |
Networking sub component: | router | QA Contact: | Hongan Li <hongli> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | low | ||
Priority: | medium | CC: | alegrand, anpicker, aos-bugs, ematysek, erooth, hongli, kakkoyun, lcosic, mifiedle, mloibl, pkrupa, surbania |
Version: | 4.3.0 | ||
Target Milestone: | --- | ||
Target Release: | 4.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1780398 | Environment: | |
Last Closed: | 2020-05-04 11:19:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Miciah Dashiel Butler Masters
2019-12-06 23:57:04 UTC
In each router pod's logs, I see 9995 instances of this message logged in a period of about 11 seconds. Just to make sure I'm not missing a more serious issue, can you confirm that the test in question created about 9995 routes with conflicting host names? The test does create a large number of artificial routes from the same template. I will open an issue to make those routes more realistic. verified with 4.4.0-0.nightly-2019-12-20-210709 and issue has been fixed. create two routes with same hostname, then oc -n openshift-ingress logs router-default-568c75cc44-8jgqf | grep "claimed" repeat the same steps with old build then $ oc -n openshift-ingress logs router-default-678757dd74-5nzc5 | grep "claimed" E1223 08:10:14.876097 1 router_controller.go:244] another route has claimed this host Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581 |