The first time I deployed OpenStack, I met this problem, and the version was Havana,
Now deploy Essex time again encountered this problem, after some toss, solved this problem, record down, lest forget later.
===========================================================
1. View the/var/log/nova/nova-compute.log file there is a situation where:
Domain not found:no domain with matching name ' instance-00000008 '
2. Backup Document /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py to Commection.py.bak
3. Editing /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py
Find this line:virt_dom = self._conn.lookupbyname (instance[' name ')
And then delete this line
Add in the location of the deletion:
# note:in case of no domain up try:virt_dom = self._conn.lookupbyname (instance[' name ') except Exception, E:virt_dom = None
find this line again . XML = Virt_dom. Xmldesc (0) to delete the previous sentence of this line:if not xml:
Add again at the place of deletion:
If Virt_dom:xml = Virt_dom. Xmldesc (0) Else:xml = Self.to_xml (instance, network_info)
Finally find this line:
Self.destroy (instance, Network_info, Cleanup=false) The next behavior in this line (Self.plug_vifs (instance, network_info)) and added in its previous row
If Virt_dom:
Go to catalogue cd/var/lib/nova/instances/instance-00000008
Execute commands in this directory
Virsh Define Libvirt.xml
Then restart the instance. Then restart the Nova-compute service, check the Nova-manage Service list discovery is still xxx, and see in log this situation:
CRITICAL Nova [-] Invalid syntax (connection.py, line 397) #说明在397行的语法有问题.
Then the
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py changed the name to CONNECTION.PY.BAK2 (the reason is number 2, Because Connection.py.bak has been created before)
This time will
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py.bak Change to connection.py
and give permission: chmod 777 connection.py
Restart Nova-compute Services, service nova-compute restart View Nova-manage Service list service has become a smiley face;
Binary Host Zone Status State updated_at
Nova-consoleauth Server1 Nova enabled:-) 2014-01-08 02:45:57
Nova-cert Server1 Nova enabled:-) 2014-01-08 02:46:02
Nova-scheduler Server1 Nova enabled:-) 2014-01-08 02:46:02
Nova-compute Server1 Nova enabled:-) 2014-01-08 02:46:05
Nova-network Server1 Nova enabled:-) 2014-01-08 02:46:03
Nova-volume Server1 Nova enabled:-) 2014-01-08 02:46:03
Deployment of OpenStack Issues Summary (iv)--openstack in Nova-compute state status display as ' XXX ' issue