Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Juno + Centos 7 - BuildAbortException: Build of instance aborted: Failed to allocate the network(s), not rescheduling.

Hi,

I have a setup with Ubunt AIO 14.04 running Juno, seems to be working fine, after two months I decided to play around with adding new compute node but running on Centos 7.

Problem is that I start any instance on Centos host, every creation fails with Exception as in the title.

Right before this Exception there is another one which should not influence instance creation based on nova/compute/manager.py:

instance.save(expected_task_state=[None]) (...) RemoteError: Remote error: OperationalError (OperationalError) (1048, "Column 'instance_uuid' cannot be null") 'UPDATE instance_extra SET updated_at=%s, instance_uuid=%s WHERE instance_extra.id = %s' (datetime.datetime(2014, 12, 30, 21, 34, 4, 684113), None, 150L)

Adding in nova.confg did not help (it was the same issue on Ubuntu before and following lines helped in that case):

vif_plugging_is_fatal=False vif_plugging_timeout=0

I am pretty sure that vif creation is successful but it happens few seconds after I start my instance whereas instance creation fails instantaneously (without waiting for vif creation), the following logs on controller node (Ubuntu) proves that such event is sent (I know here it is error but it was error due to my typo on controller node in neutron.conf):

2014-12-30 22:23:21.567 3710 ERROR neutron.notifiers.nova [-] Failed to notify nova on events: [{'status': 'completed', 'tag': u'60f129c9-02f6-43ac-b15c-29bdd47005e1', 'name': 'network-vif-plugged', 'server_uuid': u'09bbb54c-68c3-4c64-bdce-4a63aa78a699'}, {'status': 'completed', 'tag': u'ef56d76f-79c9-41f0-8f41-659bcfa8527d', 'name': 'network-vif-plugged', 'server_uuid': u'83c11b41-1420-4693-ba04-faf4afbbee06'}]

I assume that as soon as this event is received on compute node, neutron agent there instructs OVS to create appropriate interfaces with appropriate IP addressing.

Does anybody have a clue how to troubleshoot this issue ? Or are there any caveats on adding new compute nodes ?

Br, Michal

Juno + Centos 7 - BuildAbortException: Build of instance aborted: Failed to allocate the network(s), not rescheduling.

Hi,

I have a setup with Ubunt AIO 14.04 running Juno, seems to be working fine, after two months I decided to play around with adding new compute node but running on Centos 7.

Problem is that I start any instance on Centos host, every creation fails with Exception as in Exception:

 BuildAbortException: Build of instance aborted: Failed to allocate the title.

network(s), not rescheduling.

Right before this Exception there is another one which should not influence instance creation based on nova/compute/manager.py:

instance.save(expected_task_state=[None])
(...)
RemoteError: Remote error: OperationalError (OperationalError) (1048, "Column 'instance_uuid' cannot be null") 'UPDATE instance_extra SET updated_at=%s, instance_uuid=%s WHERE instance_extra.id = %s' (datetime.datetime(2014, 12, 30, 21, 34, 4, 684113), None, 150L)

150L)

Adding in nova.confg did not help (it was the same issue on Ubuntu before and following lines helped in that case):

vif_plugging_is_fatal=False 
vif_plugging_timeout=0

vif_plugging_timeout=0

I am pretty sure that vif creation is successful but it happens few seconds after I start my instance whereas instance creation fails instantaneously (without waiting for vif creation), the following logs on controller node (Ubuntu) proves that such event is sent (I know here it is error but it was error due to my typo on controller node in neutron.conf):

2014-12-30 22:23:21.567 3710 ERROR neutron.notifiers.nova [-] Failed to notify nova on events: [{'status': 'completed', 'tag': u'60f129c9-02f6-43ac-b15c-29bdd47005e1', 'name': 'network-vif-plugged', 'server_uuid': u'09bbb54c-68c3-4c64-bdce-4a63aa78a699'}, {'status': 'completed', 'tag': u'ef56d76f-79c9-41f0-8f41-659bcfa8527d', 'name': 'network-vif-plugged', 'server_uuid': u'83c11b41-1420-4693-ba04-faf4afbbee06'}]

u'83c11b41-1420-4693-ba04-faf4afbbee06'}]

I assume that as soon as this event is received on compute node, neutron agent there instructs OVS to create appropriate interfaces with appropriate IP addressing.

Does anybody have a clue how to troubleshoot this issue ? Or are there any caveats on adding new compute nodes ?

Br, Michal