Ask Your Question

122014's profile - activity

2015-02-24 17:25:04 -0500 received badge  Famous Question (source)
2015-01-13 13:07:18 -0500 received badge  Notable Question (source)
2014-12-18 05:35:36 -0500 received badge  Scholar (source)
2014-12-17 11:40:09 -0500 received badge  Self-Learner (source)
2014-12-17 11:40:09 -0500 received badge  Teacher (source)
2014-12-17 05:12:26 -0500 commented question "connection to neutron failed" on network node (VirtualBox VM)

The question is below the blockquote in italics, I simply removed the 5 or so logs because they were irrelevant, as the problem wasn't related to /etc/network/interfaces, OpenStack or OpenVSwitch of the nodes, rather the VirtualBox setup. If it would be helpful I could reinclude the logs.

2014-12-17 05:10:03 -0500 received badge  Enthusiast
2014-12-16 23:42:10 -0500 received badge  Popular Question (source)
2014-12-16 03:53:16 -0500 commented question "connection to neutron failed" on network node (VirtualBox VM)

Update: the neutron/network node connectivity problem was fixed by changing the external network setup in VirtualBox from NAT to Bridged Interface, and updating the IPs in /etc/network/interfaces, config files and in the keystone database accordingly.

2014-12-15 04:52:59 -0500 asked a question "connection to neutron failed" on network node (VirtualBox VM)

neutron agent-list works on the controller node but fails on the network node.


Despite following the guide on ( there was no connection between the Network and Controller nodes while using "neutron agent-list" on the network node. Error was simply "connection to neutron failed".

The nodes were run on VirtualBox. The internal network 10.0.0.xx and tunneling 10.0.1.xx were host-only networks and the external network 10.0.3.xx was on NAT for internet access.

The solution to this was to change NAT to Bridged Network in VirtualBox.


Management Network ( is a host-only network.

VM Traffic Network ( is a host-only network.

Public Network ( is a bridged network. (IP begins with 192.168 but may end differently depending on your setup. The automatically generated IPs and default gateway were manually entered into /etc/network/interfaces/.)

Solved problem:

I am on the Network Node=>Check Neutron agents step of this guide: (

ConnectionFailed: Connection to neutron failed:
DEBUG: clean_up ListAgent
DEBUG: Got an error: Connection to neutron failed:

Nodes are Ubuntu 14.04 VMs on VirtualBox. Eth0 is a host-only network on 10.0.0.xx. Eth1 is a NAT network for internet access with fixed IPs and port forwarding, 10.0.3.xx. Eth2 is tunneling for the network node on 10.0.1.xx. Neutron server and RabbitMQ are configured and running.

Network node can ping the controller at (host-only) but not at (NAT). is the publicurl of neutron. The same happens with telnet. can be pinged by controller.

Pings from network to controller, internet and compute node through and work. Controller can ping network at and but not (br-ex; network's internet connection).

tcpdump of ping to (the br-ex IP of network node) from controller node
ARP, Request who-has tell, length 28
"Destination Host Unreachable. 100% packet loss."

After entering neutron agent-list, tcpdump on network's eth1 reports: ARP, Request who-has tell, length 28

Pinging from network node results in Destination Host Unreachable.

No bridges show up in brctl .

Is this a problem with the NAT setup on 10.0.3.xx or bridging (br-ex is on eth1 on

[Included logs were removed due to being unnecessary for solution]

2014-12-15 04:45:09 -0500 received badge  Popular Question
2014-12-04 08:07:11 -0500 received badge  Notable Question
2014-12-04 07:43:07 -0500 received badge  Editor
2014-12-03 04:54:18 -0500 commented question Can't ping outside network with default legacy network configuration on wheezy

Does anyone have an answer to this? (experiencing similar problem)

2014-12-02 12:34:34 -0500 received badge  Popular Question
2014-12-02 11:28:17 -0500 received badge  Supporter (source)