[Openstack-operators] Virtual Instance can't obtain IP address (OpenStack Havana)

George Shuklin george.shuklin at gmail.com
Wed Jan 29 20:58:43 UTC 2014


  '#' - comment sign for ini-files. You got no local_ip in 
ovs_neutron_plugin.ini file.

Uncomment it, change to 10.0.0.9, reboot node and be happy.

PS Same should be done on all compute/network nodes.

On 01/29/2014 08:11 PM, Alvise Dorigo wrote:
> On 29 Jan 2014, at 17:15, George Shuklin <george.shuklin at gmail.com> wrote:
>
>> One more trick:
>>
>> Check /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini for local_ip value.
>>
>> Find local interface with that address (if none found - this is config bug). run tcpdump -ni THAT_INTERFACE proto gre to see if some traffic is ever leave compute node.
> [root at network ~]# grep local_ip /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini
> # local_ip =
> # local_ip = 10.0.0.3
> [root at network ~]# ifconfig eth1
> eth1      Link encap:Ethernet  HWaddr 00:0C:29:8D:2E:D2
>            inet addr:10.0.0.9  Bcast:10.0.0.255  Mask:255.255.255.0
>            UP BROADCAST RUNNING MULTICAST  MTU:1000  Metric:1
>            RX packets:2391 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:2561 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:296093 (289.1 KiB)  TX bytes:562554 (549.3 KiB)
>
>
> 	Alvise
>
>
>> Same thing can be done on network node to see if any  GRE traffic is reach it.
>> On 29.01.2014 17:25, Alvise Dorigo wrote:
>>> Hello,
>>> I've a distributed installation of OpenStack Havana on 3 different nodes:
>>>
>>>   1. Controller node: nova-api + nova-cert + nova-scheduler + nova-consoleauth + nova-novncproxy + nova-conductor + keystone + glance + neutron server + Dashboard
>>>
>>>   2. compute node: nova-compute
>>>
>>>   3. network node: l3-agent + dhcp-agent + metadata-agent
>>>
>>> Of course, on all of them, the l2-agent (neutron-openvswitch-agent) is also running.
>>>
>>>  From the dashboard I created a simple cirros image; then I launched it and attached to an non-external network (created in the Admin project, and having its own subnet and dhcp enabled). Nova assigned an IP to the VM, but actually when the VM's operating system bootstrapped it couldn't obtain from the DHCP the assigned IP.
>>>
>>> I monitored the br-int interface on the compute node and on the network node, using "tcpdump -i br-int".
>>>
>>> I saw the packet traffic going through the two br-int interfaces (from compute node to network node). But when I monitored the tapXYZ... in the dhcp network namespace (in the network node) I didn't see any packet traversing it:
>>>
>>>      ip netns exec qdhcpXYZ… "tcpdump -i tap37fgw74frwgc"
>>>
>>> … nothing … :-(
>>>
>>> So, it seems that the DHCP client's request correctly originates from the VM, and is correctly trasmitted to the network node by mean of the data network the two br-int interfaces are connected to; but for some reason the dhcp-agent doesn't receive anything, as proved by the null traffic on its tap.
>>>
>>> Any idea about what and how I could more deeply investigate ?
>>>
>>> thanks,
>>> Alvise
>>>
>>>
>>> _______________________________________________
>>> OpenStack-operators mailing list
>>>
>>> OpenStack-operators at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators




More information about the OpenStack-operators mailing list