Ask Your Question
2

Instance failed to spawn : you must call 'aug-init' first to initialize Augeas

asked 2014-05-04 04:19:41 -0500

Super Wang gravatar image

updated 2014-05-04 04:24:17 -0500

I'm running icehouse on 5 ubuntu v14.04 nodes using VMWare Workstation 10.0.2

When I'm trying to create new instance, I've got the following error in my /var/log/nova/nova-compute.log:

2014-05-04 16:54:49.708 1968 INFO nova.virt.libvirt.driver [req-d1b25428-d1ff-4061-9c74-b781738b75fb 6404404b3fb34591bd72be8788bb1c7e b96454f1425b4a159da8daad18a438de] [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] Creating image

2014-05-04 16:55:31.825 1968 WARNING nova.compute.manager [-] Found 1 in the database and 0 on the hypervisor.

2014-05-04 16:55:31.826 1968 INFO nova.compute.manager [-] [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] During sync_power_state the instance has a pending task. Skip.

2014-05-04 16:57:07.387 1968 WARNING nova.virt.disk.vfs.guestfs [req-d1b25428-d1ff-4061-9c74-b781738b75fb 6404404b3fb34591bd72be8788bb1c7e b96454f1425b4a159da8daad18a438de] Failed to close augeas aug_close: do_aug_close: you must call 'aug-init' first to initialize Augeas

2014-05-04 16:57:07.662 1968 ERROR nova.compute.manager [req-d1b25428-d1ff-4061-9c74-b781738b75fb 6404404b3fb34591bd72be8788bb1c7e b96454f1425b4a159da8daad18a438de] [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] Instance failed to spawn**

2014-05-04 16:57:07.662 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] Traceback (most recent call last):

2014-05-04 16:57:07.662 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1720, in _spawn

2014-05-04 16:57:07.662 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] block_device_info)

2014-05-04 16:57:07.662 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2250, in spawn

2014-05-04 16:57:07.662 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] write_to_disk=True)

2014-05-04 16:57:07.662 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3431, in to_xml

2014-05-04 16:57:07.662 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] disk_info, rescue, block_device_info)

2014-05-04 16:57:07.662 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3247, in get_guest_config

2014-05-04 16:57:07.662 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] flavor)

2014-05-04 16:57:07.662 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 384, in get_config

2014-05-04 16:57:07.662 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] _("Unexpected vif_type=%s") % vif_type)

2014-05-04 16:57:07.662 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] NovaException: Unexpected vif_type=binding_failed

2014-05-04 16:57:07.662 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9]

2014-05-04 16:57:08.642 1968 ERROR nova.virt.libvirt.driver [-] [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] During wait destroy, instance disappeared.

2014-05-04 16:57:08.929 1968 ERROR nova.compute.manager [req-d1b25428-d1ff-4061-9c74-b781738b75fb 6404404b3fb34591bd72be8788bb1c7e b96454f1425b4a159da8daad18a438de] [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] Error: Unexpected vif_type=binding_failed

2014-05-04 16:57:08.929 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] Traceback (most recent call last):

2014-05-04 16:57:08.929 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1311, in _build_instance

2014-05-04 16:57:08.929 1968 TRACE nova.compute.manager [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] set_access_ip=set_access_ip)

2014-05-04 16:57:08.929 1968 TRACE nova.compute.manager [instance ... (more)

edit retag flag offensive close merge delete

Comments

Can anybody help on this? I really need a fix or workaround on this

Super Wang gravatar imageSuper Wang ( 2014-05-05 21:26:46 -0500 )edit

I'm getting the exact same issue. Still not sure what's going on

dcbarans gravatar imagedcbarans ( 2014-05-08 22:13:38 -0500 )edit

Are you running on physical or virtual machines? I'm still struggling with it.

Super Wang gravatar imageSuper Wang ( 2014-05-09 01:00:01 -0500 )edit
add a comment

2 answers

Sort by ยป oldest newest most voted
2

answered 2014-05-17 00:36:20 -0500

OldCrowEW gravatar image

Hello, I just had this issue. I was focusing on the warning as well. As someone else stated, the warning isnt a concern. The real error appears to be:

2014-05-04 16:57:08.929 1968 ERROR nova.compute.manager [req-d1b25428-d1ff-4061-9c74-b781738b75fb 6404404b3fb34591bd72be8788bb1c7e b96454f1425b4a159da8daad18a438de] [instance: a4463cd9-489b-4f96-b68a-d48462d83fe9] Error: Unexpected vif_type=binding_failed

This issue appeared after running updates today. My /etc/init.d/neutron-openvswitch-agent was clobbered. Give this a try: Ensure symbolic link is in place:

ln -s plugins/ml2/ml2_conf.ini /etc/neutron/plugin.ini

Fix init script

cp /etc/init.d/neutron-openvswitch-agent /etc/init.d/neutron-openvswitch-agent.orig
sed -i 's,plugins/openvswitch/ovs_neutron_plugin.ini,plugin.ini,g' /etc/init.d/neutron-openvswitch-agent

Then restart nova and openvswitch agent.

edit flag offensive delete link more

Comments

I followed your described steps but it does not work for me there are still problems and nothing changed

Moe gravatar imageMoe ( 2014-12-01 04:40:36 -0500 )edit
add a comment
1

answered 2014-05-20 11:42:12 -0500

fgorbat gravatar image

Had similar issue with the "Error: Unexpected vif_type=binding_failed" after upgrading of the openvswitch-agent rpm.
Fixing done according to the installation http://docs.openstack.org/icehouse/install-guide/install/yum/content/neutron-ml2-network-node.html (guide)

Due to a packaging bug, the Open vSwitch agent initialization script explicitly looks for the Open vSwitch plug-in configuration file rather than a symbolic link /etc/neutron/plugin.ini pointing to the ML2 plug-in configuration file. Run the following commands to resolve this issue:

cp /etc/init.d/neutron-openvswitch-agent /etc/init.d/neutron-openvswitch-agent.orig
sed -i 's,plugins/openvswitch/ovs_neutron_plugin.ini,plugin.ini,g' /etc/init.d/neutron-openvswitch-agent
edit flag offensive delete link more

Comments

This worked for me! The warning is not related as it's for a separate boot procedure

dcbarans gravatar imagedcbarans ( 2014-05-26 11:51:50 -0500 )edit

For the record: on RHEL7 you have to do this change in /usr/lib/systemd/system/neutron-openvswitch-agent.service

msuchy gravatar imagemsuchy ( 2015-02-20 07:51:14 -0500 )edit
add a comment

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

3 followers

subscribe to rss feed

Stats

Asked: 2014-05-04 04:19:41 -0500

Seen: 7,352 times

Last updated: May 20 '14

Related questions

Change default (path) emulator for libvirt

unable to login to dashboard

How to enable emulated ich6 sound board on a KVM instance in IceHouse?

Cannot connect to the instance console for a VM

How to delete network

Disk Quota for Projects

QCOW2 image convertion consumes disk space

Standalone mode (no network)

Hypervisor summary shows incorrect total storage

Unable to create instances icehouse due to rabbit mq timeout