Why is the interface in router are down? and how do I bring it up?

asked 2017-08-09 15:18:55 -0500

Riccardo M. gravatar image

updated 2017-08-09 15:19:53 -0500

my lab:

  • 1 VM for MAAS 50GB HDD + 8GB RAM
  • 1 VM for JUJU 50GB HDD + 8GB RAM
  • 1 VM for LANDSCAPE 50GB HDD + 8GB RAM
  • 4 VM for OPENSTACK 400GBx2 HDD + 16GB RAM

All services on nodes are all correctly installed, Openstack has been correctly deployed. The instance has been created with its own interfaces but on the router section the interface is down and it's impossible to ping the container.

here the https://pasteboard.co/GETQuPW.png (image). thanks in advance for your support

edit retag flag offensive close merge delete

Comments

The external interface is down on my router as well; this has no meaning except perhaps lazy programming. As to the internal interface, grep the logs of Neutron and the Neutron agent (e.g. openvswitch-agent.log) on controllers and compute node for the port's UUID 5ce69773...

Bernd Bausch gravatar imageBernd Bausch ( 2017-08-09 19:07:40 -0500 )edit

neutron-dhcp-agent.log http://paste.ubuntu.com/25283524/ (here) neutron-l3-agent.log http://paste.ubuntu.com/25283526/ (here) neutron-openvswitch-agent.log http://paste.ubuntu.com/25283530/ (here) neutron-ovs-cleanup.log http://paste.ubuntu.com/25283532/ (here)

there are a lot errors :-(

Riccardo M. gravatar imageRiccardo M. ( 2017-08-10 08:19:47 -0500 )edit

While using Ubuntu Openstack Autopilot that interface are in UP status and the ping works well, but for this lab I've another problem with the creation of the instance...

Riccardo M. gravatar imageRiccardo M. ( 2017-08-10 08:29:41 -0500 )edit