Comment 57 for bug 1953165

Hi Florian and Brian,

Sorry for the slow reaction! And thanks for all the testing.

I'm wondering if we could get rid of the "cannot bind socket" error without the use of haproxy transparent binding. I did not try it yet, but it seems to me that with a small refactoring that should be possible. Basically we would need to move this:

https://opendev.org/openstack/neutron/src/commit/181177fe885f49f2d31f3e175d33efbf21ac3676/neutron/agent/metadata/driver.py#L243-L249

to between lines 277-278, and there we would already know the outcome of DAD and based on that we could control _get_metadata_proxy_callback(bind_address_v6=...).

This way we would not depend on haproxy compile options.

What do you think?