openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #19422
Re: nova-compute not starting
It turned out to be that last one. What I don't understand is where
openstack found the instance id from. That doesn't exist in the database,
or anywhere on the file system I could find.
Kind regards
-- joe.
On 13 December 2012 10:27, Razique Mahroua <razique.mahroua@xxxxxxxxx>wrote:
> Hey Joe,
> yes, several solutions there
> First, check if the domain exists by running
> $ virsh list --all (supposing you use libvirt)
>
> check /var/lib/nova/instances/instance-0000002a
> if the dir. exists $cd into it and run "virsh define libvirt.xml"
> then restart nova-compute
>
> If the dir. doesn't exist, you may want to update the nova database,
> figure out your instance entry within the "instances" table and update the
> field "deleted" to 1
>
> Regards,
> *Razique Mahroua** - **Nuage & Co*
> razique.mahroua@xxxxxxxxx
> Tel : +33 9 72 37 94 15
>
>
> Le 12 déc. 2012 à 17:07, Joe Warren-Meeks <joe.warren.meeks@xxxxxxxxx> a
> écrit :
>
> Hi guys,
>
> You think you have Openstack working, then you cough and it all breaks.
>
> I'm getting the following error when trying to start nova-compute after a
> reboot of the compute node (to install non-related patches)
>
> libvirtError: Domain not found: no domain with matching name
> 'instance-0000002a'
>
> Now, I've dumped all the DBs to disk and grepped through it for '00002a'
> and grep -R'ed /etc/ and /var/
>
> I can't find any reference to that anywhere, but it is causing
> nova-compute to fail to start.
>
> Anyone know how to fix that? If not, anyone know a cloud platform that
> isn't made from very thin glass, pre-shattered for your pleasure?
>
> -- joe.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
>
Follow ups
References