Anything that would vary between instances in a request like this is
being removed from the request spec sent to the scheduler. The
scheduler should not care about the specific instances being scheduled,
only the requested resources that the instance needs from a compute.
** 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/1268450
Title:
request_spec[instance_properties] mismatches
Status in OpenStack Compute (nova):
Won't Fix
Bug description:
When boot VM with '--num-instances', the param
"request_spec['instance_properties']" that schedule_run_instance gets
will be only the first instance's properties of
request_spec.get('instance_uuids'), thus like
request_spec['instance_properties']['instance_uuid'] ,
request_spec['instance_properties']['hostname'] and so on are all just
the properties of the first VM.
Furthermore, if one of the VMs booting with '--num-instances'
reschedules, request_spec['instance_properties'] is still for the
first VM. Thus, using the data from
request_spec['instance_properties'] is mistake, like instance_uuid =
instance_properties.get('uuid') in filter_scheduler.py:def
_populate_retry().
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1268450/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
