Bug 2110726 - rndc uses internal api source address to talk to bind, requiring asymmetric routing
Summary: rndc uses internal api source address to talk to bind, requiring asymmetric r...
Keywords:
Status: CLOSED DUPLICATE of bug 2073026
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: tripleo-ansible
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: Alpha
: 17.0
Assignee: Brent Eagles
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-25 18:36 UTC by Brent Eagles
Modified: 2022-07-26 15:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-26 15:55:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 850943 0 None NEW Move rndc traffic onto bind network 2022-07-25 22:31:09 UTC
Red Hat Issue Tracker OSP-17847 0 None None None 2022-07-25 18:41:48 UTC

Description Brent Eagles 2022-07-25 18:36:30 UTC 
rndc is executed by designate worker to send commands to bind. designate worker is hosted on the internal API network but deployed bind is hosted on the public API network. Due to the asymmetric routing and strict reverse path filtering, this results in rndc calls hanging when a worker tries to execute a command on a bind on another node.

This is 100% reproducible with multi-controller deployments.
Comment 5 Brent Eagles 2022-07-26 15:55:45 UTC 
Closing as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2073026. While slightly different, they are the same functional issue (networking issues between rndc and bind instances)

*** This bug has been marked as a duplicate of bug 2073026 ***
Note You need to log in before you can comment on or make changes to this bug.