Creation of br-int times out when spinning up devstack due to malformed connection string

[Frederick F. Kautz IV]

When setting up a new devstack, creating the br-int fails due to a poorly formed OVS->ODL connection string.

networking-odl/devstack/entry_points for ODL_MANAGERS variable:

$ ping devstack # demonstrate devstack resolves
PING devstack (127.0.0.1) 56(84) bytes of data.
64 bytes from devstack (127.0.0.1): icmp_seq=1 ttl=64 time=0.036 ms

Fails when script attempts to use host name:
tcp:devstack:6640

Works when IP is hard coded into script:
tcp:127.0.0.1:6640

Here's a log of when it fails:

$ tail /var/log/openvswitch/*.log
==> /var/log/openvswitch/ovsdb-server.log <==
2017-03-10T02:22:22.488Z|00155|socket_util|ERR|devstack:6640: bad IPv4 address "devstack"
2017-03-10T02:22:22.488Z|00156|stream_tcp|ERR|tcp:devstack:6640: connect: Address family not supported by protocol
2017-03-10T02:22:22.488Z|00157|reconnect|INFO|tcp:devstack:6640: connecting...
2017-03-10T02:22:22.488Z|00158|reconnect|INFO|tcp:devstack:6640: connection attempt failed (Address family not supported by protocol)
2017-03-10T02:22:22.488Z|00159|reconnect|INFO|tcp:devstack:6640: waiting 8 seconds before reconnect
2017-03-10T02:22:30.489Z|00160|socket_util|ERR|devstack:6640: bad IPv4 address "devstack"
2017-03-10T02:22:30.489Z|00161|stream_tcp|ERR|tcp:devstack:6640: connect: Address family not supported by protocol
2017-03-10T02:22:30.489Z|00162|reconnect|INFO|tcp:devstack:6640: connecting...
2017-03-10T02:22:30.489Z|00163|reconnect|INFO|tcp:devstack:6640: connection attempt failed (Address family not supported by protocol)
2017-03-10T02:22:30.489Z|00164|reconnect|INFO|tcp:devstack:6640: waiting 8 seconds before reconnect

==> /var/log/openvswitch/ovs-vswitchd.log <==
2017-03-10T02:13:08.338Z|00002|ovs_numa|INFO|Discovered 2 CPU cores on NUMA node 0
2017-03-10T02:13:08.338Z|00003|ovs_numa|INFO|Discovered 1 NUMA nodes and 2 CPU cores
2017-03-10T02:13:08.338Z|00004|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connecting...
2017-03-10T02:13:08.338Z|00005|reconnect|INFO|unix:/var/run/openvswitch/db.sock: connected
2017-03-10T02:13:08.340Z|00006|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.5.0
2017-03-10T02:18:39.423Z|00007|memory|INFO|10768 kB peak resident set size after 331.1 seconds
2017-03-10T02:18:39.424Z|00008|socket_util|ERR|devstack:6640: bad IPv4 address "devstack"
2017-03-10T02:18:39.440Z|00009|socket_util|ERR|devstack:6640: bad IPv4 address "devstack"
2017-03-10T02:18:39.707Z|00010|socket_util|ERR|devstack:6640: bad IPv4 address "devstack"
2017-03-10T02:18:39.713Z|00011|socket_util|ERR|devstack:6640: bad IPv4 address "devstack"

[Frederick F. Kautz IV (fkautz)]

I have a working patch for this, going to run some tests on my system first then I'll submit a patch to gerrit.

[Frederick F. Kautz IV (fkautz)]

I added a change for review at https://review.openstack.org/#/c/445165/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/445165
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=4f6e286388ccbaabd9f4c980fd6d339faf8572ea
Submitter: Jenkins
Branch: master

commit 4f6e286388ccbaabd9f4c980fd6d339faf8572ea
Author: Frederick F. Kautz IV <email address hidden>
Date: Thu Mar 9 20:02:48 2017 -0800

    OVS connects to ODL using IP instead of hostname.

    Change-Id: Ib1f6b61f7094410d2b8ca6961983b3c7c3e107e1
    Closes-Bug: #1671678

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/networking-odl 11.0.0.0b1 development milestone.