On 03/21/2014 08:41 AM, Solly Ross wrote:
> Well, if messages are getting dropped on the floor due to communication
> issues, that's not a good thing.
> If you have time, could you determine why the messages are getting dropped on
> the floor? We shouldn't be
> doing things that require both the
we have a
connection.
Best Regards,
Solly Ross
- Original Message -
From: "Chris Friesen"
To: openstack-dev@lists.openstack.org
Sent: Thursday, March 20, 2014 2:59:55 PM
Subject: Re: [openstack-dev] [nova] instances stuck with task_state of
REBOOTING
On 03/20/2014 12:29 PM,
On 03/20/2014 12:29 PM, Chris Friesen wrote:
The fact that there are no success or error logs in nova-compute.log
makes me wonder if we somehow got stuck in self.driver.reboot().
Also, I'm kind of wondering what would happen if nova-compute was
running reboot_instance() and we rebooted the cont
On 03/20/2014 12:06 PM, Solly Ross wrote:
Hi Chris,
Are you in the position to determine whether or not this happens with the
latest master code?
Either way, it definitely looks like a bug.
Unfortunately not right now, working towards a deadline.
If you could give more specific reproduction
: "Chris Friesen"
To: openstack-dev@lists.openstack.org
Sent: Thursday, March 20, 2014 1:59:39 PM
Subject: [openstack-dev] [nova] instances stuck with task_state of REBOOTING
I'm running a havana install, and during some testing I've managed to
get the system into a state whe
I'm running a havana install, and during some testing I've managed to
get the system into a state where two instances are up and running but
are reporting a task_state of REBOOTING.
I can see the nova-api logs showing the soft-reboot request. I don't
see a corresponding nova-compute log indic
