Bug 1841029
Summary: | DNS LB not allowing UDP traffic after Octavia upgrade | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Maysa Macedo <mdemaced> | |
Component: | Networking | Assignee: | Maysa Macedo <mdemaced> | |
Networking sub component: | kuryr | QA Contact: | GenadiC <gcheresh> | |
Status: | CLOSED ERRATA | Docs Contact: | ||
Severity: | medium | |||
Priority: | medium | CC: | gcheresh, ltomasbo, rlobillo | |
Version: | 4.4 | Keywords: | UpcomingSprint | |
Target Milestone: | --- | |||
Target Release: | 4.4.z | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Cause: Upon Octavia upgrade from OpenStack 13 to 16, UDP listener is supported and the strategy to enforce DNS resolution over TCP protocol is removed, requiring that the existent DNS service that specifies UDP protocol has the new listener added.
Consequence: The already existent DNS load-balancer have an old amphora image which does not support the new listener causing the listener creation to fail.
Fix: The DNS OpenShift service that requires UDP is recreated, causing a recreation of the load balancer with the new Amphora version. The recreation of the service and load balancer cause some down time on the DNS resolution.
Result: The load balancer for the DNS service is created with all the needed listeners.
|
Story Points: | --- | |
Clone Of: | 1829233 | |||
: | 1846459 (view as bug list) | Environment: | ||
Last Closed: | 2020-06-23 00:57:26 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: | ||||
Bug Depends On: | 1829233 | |||
Bug Blocks: | 1846459 |
Comment 4
rlobillo
2020-06-15 16:12:42 UTC
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:2580 |