** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => liberty-1
--
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/1408859
Title:
Scheduler didn't release already allocated HostState resources after
multiple creating instances fails
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
We multiple-create 3 instances, but the host resource is only enough for 1
instance,
nova-scheduler consume the resource of selected host for the first instance
in select_destinations.
After the multiple creating fails, we try to boot 1 instance with same
flavor, the host have
enough resource to boot it, but nova-scheduler raise 'No Valid Host'. And
more worse is that
host resource tracker only update compute node into DB when the host resource
have changed,so ComputeNode's update time in DB will be less than the update
time in scheduler cache,the scheduler cache can't be updated. In this case, the
host will not be selected forever.
We need to release the host resource when multiple creating instance is
failed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1408859/+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
