Bug 2222420 - designate worker notify messages rejected by bind9 when deploying IPv6 [NEEDINFO]
Summary: designate worker notify messages rejected by bind9 when deploying IPv6
Keywords:
Status: ON_DEV
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: tripleo-ansible
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z2
: 17.1
Assignee: Brent Eagles
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-12 17:06 UTC by Brent Eagles
Modified: 2023-08-14 11:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
ifrangs: needinfo? (beagles)

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 2027608 0 None None None 2023-07-12 17:10:11 UTC
OpenStack gerrit 888300 0 None NEW Designate: add extra bind IPs to the allow notify list 2023-07-12 17:10:11 UTC
Red Hat Issue Tracker OSP-26552 0 None None None 2023-07-12 17:09:17 UTC

Description Brent Eagles 2023-07-12 17:06:52 UTC 
notify messages from the designate worker are sometimes rejected by tripleo deployed bind instances as the worker sometimes use a source address that is not on the allow-notify list in bind configuration. So far this has only been noticed in IPv6 deployments.
Note You need to log in before you can comment on or make changes to this bug.