I have now stumbled upon this issue again in the context of setting up functional testing for the corresponding function in OSC, see https://review.openstack.org/559068. After some local testing I found out that setting the DNS parameters on creating a floating IP only works if "external_dns_driver = designate" is set in neutron.conf. Without that parameter the options are being ignored.
What I'm wondering now is whether this is intentional behaviour or a bug. If it is intentional, then the documentation at https://docs.openstack.org/neutron/latest/admin/config-dns-int.html should probably be amended to document this behaviour. If it is a bug, then, well, it should be fixed. ;-)
I'd prefer the latter, because that would allow for the functional tests to proceed without having to add the whole designate stack into the deployment.
I have now stumbled upon this issue again in the context of setting up functional testing for the corresponding function in OSC, see https:/ /review. openstack. org/559068. After some local testing I found out that setting the DNS parameters on creating a floating IP only works if "external_ dns_driver = designate" is set in neutron.conf. Without that parameter the options are being ignored.
What I'm wondering now is whether this is intentional behaviour or a bug. If it is intentional, then the documentation at https:/ /docs.openstack .org/neutron/ latest/ admin/config- dns-int. html should probably be amended to document this behaviour. If it is a bug, then, well, it should be fixed. ;-)
I'd prefer the latter, because that would allow for the functional tests to proceed without having to add the whole designate stack into the deployment.