Period task shuts down instance

Bug #1463688 reported by Gary Kotton on 2015-06-10
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Medium
Unassigned

Bug Description

When the periodic task ran it detected that an instance was in a conflicting state. That is Nova was under the impression that the instance was running and it was actually not. This was due to an outage on the backend. When the instance was starting up again the period task forced the instance to shutdown.
In some cases this is too extreme and the admin should decide on the action to take.

Gary Kotton (garyk) on 2015-06-10
Changed in nova:
importance: Undecided → High

Fix proposed to branch: master
Review: https://review.openstack.org/190047

Changed in nova:
assignee: nobody → Gary Kotton (garyk)
status: New → In Progress
Matt Riedemann (mriedem) wrote :

I don't consider this a high severity issue. If someone is going to mess with things out of band then they can also manually bring them back up since they should know what they are doing.

Changed in nova:
importance: High → Medium
Matt Riedemann (mriedem) on 2015-07-27
tags: added: compute

Fix proposed to branch: master
Review: https://review.openstack.org/218975

Changed in nova:
assignee: Gary Kotton (garyk) → Matt Riedemann (mriedem)

Change abandoned by garyk (<email address hidden>) on branch: master
Review: https://review.openstack.org/190047
Reason: dsiaw!

Changed in nova:
assignee: Matt Riedemann (mriedem) → nobody
status: In Progress → Confirmed

Change abandoned by Michael Still (<email address hidden>) on branch: master
Review: https://review.openstack.org/218975
Reason: This patch has been idle for a long time, so I am abandoning it to keep the review clean sane. If you're interested in still working on this patch, then please unabandon it and upload a new patchset.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers