VMs should try to start on another compute node if they fail to start on one node

Bug #719588 reported by Christian Berendt
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Won't Fix
Wishlist
Unassigned

Bug Description

I started a few new instances with euca-run-instances. On one compute node I had some configuration errors, so the instances couldn't start there. After running euca-describe-instances the instances on the misconfigured node change into the state pending, but no more try to start them on a other node.

I'm not sure if this is a bug or a design decision.

Thierry Carrez (ttx)
summary: - machines not restarted on other computed node after crashing
+ VMs should try to start on another compute node if they fail to start on
+ one node
Changed in nova:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Sean Dague (sdague) wrote :

This is working as designed. Instance create failures should be tracked by the end user.

Changed in nova:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.