Created attachment 577590[details]
compute log snippet
Okay, I'm not sure if this is just me doing something wrong, but the f17 'getting started' docs aren't letting me launch an instance. This is a reasonably fresh f17 host. Everything seems to go fine up until I try and launch the instance like:
nova boot myserver2 --flavor 2 --key_name mykey --image $(glance index | grep f16-jeos | awk '{print $1}')
It seems to kick off fine, sits in BUILD status for a minute, then falls into ERROR status.
The compute.log indicates that network setup timed out. Annoyingly though there isn't a peep in the network.log. And extra annoyingly, 'nova delete' claims to work but the dead VMs don't go anywhere :(
Is 'nova-manage network create' supposed to immediately create the bridge device? It isn't doing so in my case, but it could just queue changes until actually needed.
So the root cause I think is that I had a stale nova-network iptables lock file, as someone else mentioned recently on the public list:
http://www.mail-archive.com/openstack@lists.launchpad.net/msg09986.html
This situation shouldn't happen understandably, so I guess we can use this bug to track that.
Created attachment 577590 [details] compute log snippet Okay, I'm not sure if this is just me doing something wrong, but the f17 'getting started' docs aren't letting me launch an instance. This is a reasonably fresh f17 host. Everything seems to go fine up until I try and launch the instance like: nova boot myserver2 --flavor 2 --key_name mykey --image $(glance index | grep f16-jeos | awk '{print $1}') It seems to kick off fine, sits in BUILD status for a minute, then falls into ERROR status. The compute.log indicates that network setup timed out. Annoyingly though there isn't a peep in the network.log. And extra annoyingly, 'nova delete' claims to work but the dead VMs don't go anywhere :( Is 'nova-manage network create' supposed to immediately create the bridge device? It isn't doing so in my case, but it could just queue changes until actually needed.