designate/releasenotes/notes/Workaround-unassigned-opcode-14-d5e1c759db58bb10.yaml
Michael Johnson 41bf7dd319 Workaround issue with dnspython >= 2.3.0
The dnspython module >= 2.3.0 now validates the opcodes used when building DNS messages. This breaks Designate because designate is using an "unassigned"[1] opcode 14 for command/control messages inside the backend agents framework.

This patch adds a workaround to override the dnspython opcode enum to include
opcode 14. This will give us time to either remove the agent framework via deprecation or to change the agent framework protocol to not rely on unassigned opcode values.

[1] https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-5

Partial-Bug: #2002950

Change-Id: If10443b2e361aa1b467fb64124ad3c82540bcddd
2023-01-17 17:46:27 +00:00

7 lines
198 B
YAML

---
fixes:
- |
Workaround the use of an unassigned opcode(14) by Designate that fails
validation when used with dnspython >= 2.3.0.
`LP#2002950 <https://launchpad.net/bugs/2002950>`__