This is working as designed. Instance create failures should be tracked
by the end user.
** Changed in: nova
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/719588
Title:
VMs should try to start on another compute node if they fail to start
on one node
Status in OpenStack Compute (Nova):
Won't Fix
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/719588/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
