| darkhackernc | ykarel, Hi | 12:55 |
|---|---|---|
| darkhackernc | can you please check https://bugs.launchpad.net/designate/+bug/2119294 | 12:55 |
| ykarel | darkhackernc, so it works for neutron port but not when creating vm without pre create ports? | 13:38 |
| darkhackernc | yes sir | 13:39 |
| ykarel | can you update exact steps that you used there | 13:52 |
| ykarel | including server create commands | 13:53 |
| darkhackernc | ykarel, issue resolved, let me post what is actually happened. its not a bz its a workflow mistake actually. I will post that and I will raise a doc bug as well we should clearly mentioned that in the doc | 14:10 |
| ykarel | darkhackernc, perfect | 14:11 |
| darkhackernc | ykarel++ thank you very much. | 14:48 |
| darkhackernc | ykarel, ✅ Conclusion | 15:05 |
| darkhackernc | Yes — You must override the default openstacklocal with a real domain via dns_domain in Neutron and ensure Nova’s dhcp_domain matches, otherwise the DNSaaS integration (dynamic A/AAAA record creation in Designate) will not function. | 15:05 |
| ykarel | dns_domain config is required to be non default for dns integration to work | 15:13 |
| ykarel | but not sure about any requirement for that to be same with dhcp_domain | 15:14 |
| darkhackernc | ykarel, yeah as soon I changed the `dhcp_domain` it started working | 15:14 |
| darkhackernc | you can see the details in bz, earlier as well I was following the same method, and after the change as well same steps, no difference | 15:15 |
| ykarel | johnsom, oschwart mayconfirm if that's also some requirement | 15:15 |
| darkhackernc | ykarel, cool thank you Sir. | 15:17 |
| johnsom | I am not aware of a requirement for dhcp_domain either, maybe a good question for #openstack_neutron | 15:17 |
| oschwart | I couldn't find it in the designate repo | 15:18 |
| johnsom | There is definitely some oddness in the neutron extension about the dns_domain setting though | 15:18 |
| johnsom | oschwart Yeah, all of this is in the neutron code base. It is neutron extension code. | 15:18 |
| johnsom | Not designate | 15:19 |
| darkhackernc | agree with johnsom and oschwart | 15:19 |
| oschwart | https://opendev.org/openstack/neutron/src/branch/master/releasenotes/notes/dhcp-domain-removed-cc5bc6e2129fdf7f.yaml | 15:20 |
| darkhackernc | oh | 15:21 |
| oschwart | I am surprised that it worked for you, deprecated 9y ago | 15:21 |
| darkhackernc | dhcp_domain this is in nova | 15:21 |
| darkhackernc | root@jj-caracal-online:~# cat /etc/nova/nova.conf | grep ct.lan | 15:21 |
| darkhackernc | dhcp_domain = ct.lan. | 15:21 |
| darkhackernc | 15:21 | |
| darkhackernc | #/etc/openstack_deploy/user_variables.yml | 15:22 |
| darkhackernc | ``` | 15:22 |
| darkhackernc | neutron_dns_domain: "ct.lan." | 15:22 |
| darkhackernc | dhcp_domain: "{{ neutron_dns_domain }}" | 15:22 |
| darkhackernc | ``` | 15:22 |
| darkhackernc | these are the overrides | 15:22 |
| oschwart | It looks like it is defined and set in the neutron area | 15:22 |
| darkhackernc | so neutron shoud be dns_domain and nova should be dhcp_domain | 15:23 |
| oschwart | it is the first time I see this term, but that release note mentioned dns_domain should be used instead | 15:23 |
| darkhackernc | urrrrrrrrrrrr | 15:24 |
| ykarel | darkhackernc, i doubt if dhcp_domain is involved at all, so if you can just revert that and test | 15:25 |
| ykarel | because reading your comment 12 it's like neutron config was still pointing to openstacklocal and with that it's expected to not work | 15:25 |
| ykarel | saying by reading https://github.com/openstack/nova/blob/4100d4d8fbaa6416ea37d8cb3e64003f40ee1eb1/nova/network/neutron.py | 15:26 |
| darkhackernc | ykarel, infact if I change the dns_domain to someother still wont work , the way it should | 15:27 |
| ykarel | and what is that way and what value not working? | 15:32 |
| ykarel | the only requirement was it shouldn't be "openstacklocal" | 15:32 |
| darkhackernc | even If I set on neutron side to dns_domain=openstack.local. , A records are not creating while creaitng vm or creating a port, in both cases its failing. | 15:34 |
| darkhackernc | once I updated ``dns_domain = ct.lan.`` on neutron.conf and ``dhcp_domain = ct.aln.`` on nova.conf , A record started creating automatically | 15:36 |
| ykarel | may be there is some other issue, would suggest to iterate one by one | 15:39 |
| ykarel | if you still have that env from comment 13 | 15:39 |
| ykarel | can just revert dhcp_domain config and validate | 15:39 |
| darkhackernc | yes yes, | 15:40 |
| ykarel | atleast from code don't see anything wrong with dns_domain=openstack.local, in CI we do use dns_domain=openstackgate.local, not sure if we have full test coverage for designate records with different extensions | 15:40 |
| darkhackernc | ykarel++ | 15:43 |
| ykarel | thx johnsom++ oschwart++ for confirming too, we can revisit if we see non config issue here | 15:44 |
| darkhackernc | ykarel, yes tested not needed for nova | 17:18 |
| darkhackernc | only neutron is sufficient | 17:18 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!