Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Virtual Instance can't obtain IP address (OpenStack Havana)

Hello, I've a distributed installation of OpenStack Havana on 3 different nodes:

  1. Controller node

  2. nova-api

  3. nova-cert
  4. nova-scheduler
  5. nova-consoleauth
  6. nova-novncproxy
  7. nova-conductor
  8. keystone + glance
  9. neutron server
  10. Dashboard

  11. compute node

  12. nova-compute

  13. network node

  14. l3-agent
  15. dhcp-agent
  16. 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 if I monitor 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 I could more deeply investigate ?

thanks,

Alvise

Virtual Instance can't obtain IP address (OpenStack Havana)

Hello, I've a distributed installation of OpenStack Havana on 3 different nodes:

  1. Controller node

  2. nova-api

  3. nova-cert
  4. nova-scheduler
  5. nova-consoleauth
  6. nova-novncproxy
  7. nova-conductor
  8. keystone + glance
  9. neutron server
  10. Dashboard

  11. compute node

  12. nova-compute

  13. network node

  14. l3-agent
  15. dhcp-agent
  16. 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 if I monitor 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 I could more deeply investigate ?

thanks,

Alvise

Virtual Instance can't obtain IP address (OpenStack Havana)

Hello, I've a distributed installation of OpenStack Havana on 3 different nodes:

  1. Controller node
  2. nova-api
  3. nova-cert
  4. nova-scheduler
  5. nova-consoleauth
  6. nova-novncproxy
  7. nova-conductor
  8. keystone + glance
  9. neutron server
  10. Dashboard

  11. compute node

  12. nova-compute

  13. network node

  14. l3-agent
  15. dhcp-agent
  16. 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 if I monitor 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 I could more deeply investigate ?

thanks,

Alvise

Virtual Instance can't obtain IP address (OpenStack Havana)

Hello, I've a distributed installation of OpenStack Havana on 3 different nodes:

  1. Controller node

  2. nova-api
  3. + nova-cert
  4. nova-scheduler
  5. + nova-scheduler + nova-consoleauth
  6. nova-novncproxy
  7. nova-conductor
  8. + nova-novncproxy + nova-conductor + keystone + glance
  9. glance + neutron server
  10. + Dashboard

  11. compute node

  12. nova-compute

  13. network node

  14. l3-agent
  15. dhcp-agent
  16. 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 if I monitor 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 I could more deeply investigate ?

thanks,

Alvise

Virtual Instance can't obtain IP address (OpenStack Havana)

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 if I monitor 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 I could more deeply investigate ?

thanks,

Alvise

Virtual Instance can't obtain IP address (OpenStack Havana)

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 if I monitor 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 I could more deeply investigate ?

thanks,

Alvise
thanks, Alvise