Ask Your Question
0

network fail to start in controller node

asked 2018-11-27 02:17:58 -0600

anonymous user

Anonymous

updated 2018-11-28 03:44:06 -0600

After the installation of the controller node on ubuntu-server 18.04 and the configuration of their environment. After the creation of virtual networks, networking are failed to update or get something from internet but the command "service networking status" return active status and the "ifconfig" return a lot of network cards without an ip address associated to them

Everything works on my controller node besides the launch of instance it return always an error status using the command "openstack server list" I tried to launch the instance manually and from dashboard and i failed in the two cases

How can i fix these errors ?

** I found these errors in neutron-linuxbridge-agent.log

2018-11-27 14:34:11.768 4070 ERROR neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent [-] Tunneling cannot be enabled without the local_ip bound to an interface on the host. Please configure local_ip 192.168.1.23 Please configure local_ip 192.168.1.23 on the host interface to be used for tunneling and restart the agent.

MessagingTimeout: Timed out waiting for a reply to message ID 7ab31945451141cda4a3767c4b0fbb51

AMQP server on 192.168.1.23:5672 is unreachable: <amqperror: unknown="" error="">. Trying again in 1 seconds.: RecoverableConnectionError: <amqperror: unknown="" error="">

AMQP server on 192.168.1.23:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 4 seconds.: error: [Errno 111] ECONNREFUSED

ERROR neutron.plugins.ml2.drivers.agent._common_agent

edit retag flag offensive close merge delete

Comments

1

Can you elaborate what you mean by “networking are failed to update” and “get something from internet”?

An active status, and interfaces without IP addresses are not errors.

To understand why your instances fail to launch, start by showing the output of openstack server show.

Bernd Bausch gravatar imageBernd Bausch ( 2018-11-27 02:51:12 -0600 )edit

openstack server show

fault: Build of instance b737b661-89c3-4af7-96ce-ae080721dc99 aborted: Failed to allocate the network, not rescheduling.', u'code': 500, u'created': u'2018-11-27

najeh gravatar imagenajeh ( 2018-11-27 04:05:26 -0600 )edit

Are you not able to see the controller physical NIC and IP address when you run ifconfig?

John Bernad gravatar imageJohn Bernad ( 2018-11-27 05:04:15 -0600 )edit

What are the instance launch parameters?

The message seems to imply that Nova wants to create a network that doesn’t exist yet. I might be wrong but you should explore that possibility.

Bernd Bausch gravatar imageBernd Bausch ( 2018-11-27 05:18:47 -0600 )edit

the official guide parameters cirros image+ security-group mykey + the created provider network id (https://docs.openstack.org/install-guide/launch-instance.html (https://docs.openstack.org/install-gu...))

openstack server create --flavor m1.nano --image cirros --nic net-id=ID --security-group default --key-name mykey provider-instanc

najeh gravatar imagenajeh ( 2018-11-27 06:11:50 -0600 )edit

1 answer

Sort by » oldest newest most voted
0

answered 2018-11-28 09:10:00 -0600

najeh gravatar image

The problem is solved by adding lockpath to the neutron-linuxbridge-agent.conf of the compute node

nano /etc/neutron/neutron.conf

[oslo_concurrency]

lock_path=/var/log/neutron

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2018-11-27 02:17:58 -0600

Seen: 46 times

Last updated: Nov 28