[Openstack-operators] VM status keeps ACTIVE after its nova-compute host is powered off
matt
matt at nycresistor.com
Wed Aug 7 07:19:19 UTC 2013
imagine a scenario in which rabbitmq were to fail to poll the nova-compute
service and put the system into an inactive state... yet, the instances
were still up and operating as expected.
i am not sure there is a way for openstack to ensure down or up in the
scenario in which message bus communications are severed. so i don't see a
benefit either assuming down or coasting with previous values until
otherwise updated.
-matt
On Wed, Aug 7, 2013 at 12:11 AM, Zhang, Kimi (NSN - CN/Cheng Du) <
kimi.zhang at nsn.com> wrote:
> Hi, ****
>
> ** **
>
> Currently if a nova-compute host is down not gracefully, e.g. a power
> cut. Its hosting VMs still have ACTIVE status in Database.****
>
> ** **
>
> Even though nova knows the compute node is down, it does nothing to VMs
> status.****
>
> ** **
>
> Should Nova be improved to update those VMs status to something else(e.g.
> ERROR) other than confusing “ACTIVE” ??****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> Kimi Zhang****
>
> +86 186 0800 8182****
>
> ** **
>
> ** **
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130807/213647c5/attachment.html>
More information about the OpenStack-operators
mailing list