Public bug reported: At the moment, it seems that when using a DNS hostname for `ovn_nb_connection` or `ovn_sb_connection`, the connection never seems to go up.
It seems that the `ovs` library does not resolve an IP address before proceeding, I'm not sure if we should be resolving things and passing them on resolved to OVS, or tryign to look for fix upstream. This is pretty critical for HA deployments that rely on multiple replicas with hostnames (i.e. a Kubernetes StatefulSet) ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2028442 Title: Support DNS for ovn_{nb,sb}_connection Status in neutron: New Bug description: At the moment, it seems that when using a DNS hostname for `ovn_nb_connection` or `ovn_sb_connection`, the connection never seems to go up. It seems that the `ovs` library does not resolve an IP address before proceeding, I'm not sure if we should be resolving things and passing them on resolved to OVS, or tryign to look for fix upstream. This is pretty critical for HA deployments that rely on multiple replicas with hostnames (i.e. a Kubernetes StatefulSet) To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2028442/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp