Testing multi-zone deployment, "nova boot" raises the following error with Rev.1439.
Scheduler driver was "HostFilterScheduler".
2011-08-17 16:05:29,522 ERROR nova [-] Exception during message handling
(nova): TRACE: Traceback (most recent call last):
(nova): TRACE: File "/root/openstack/nova/nova/rpc/amqp.py", line 230, in _process_data
(nova): TRACE: rval = node_func(context=ctxt, **node_args)
(nova): TRACE: File "/root/openstack/nova/nova/scheduler/manager.py", line 98, in _schedule
(nova): TRACE: **kwargs)
(nova): TRACE: File "/root/openstack/nova/nova/scheduler/zone_aware_scheduler.py", line 243, in schedule_run_instance
(nova): TRACE: request_spec, kwargs)
(nova): TRACE: File "/root/openstack/nova/nova/scheduler/zone_aware_scheduler.py", line 180, in _provision_resource
(nova): TRACE: instance_id, request_spec, kwargs)
(nova): TRACE: File "/root/openstack/nova/nova/scheduler/zone_aware_scheduler.py", line 166, in _provision_resource_from_blob
(nova): TRACE: request_spec, kwargs)
(nova): TRACE: File "/root/openstack/nova/nova/scheduler/zone_aware_scheduler.py", line 133, in _ask_child_zone_to_create_instance
(nova): TRACE: child_blob, reservation_id=reservation_id)
(nova): TRACE: TypeError: create() got multiple values for keyword argument 'reservation_id'
(nova): TRACE:
HostFilterScheduler has gone away since this bug was reported. Things have been re-factored so that one can specify host filters with any AbstractScheduler descendent. So, this bug probably needs to be 'Invalid'ated or something. Related to this, 'nova boot' doesn't work with AbstractSchedulers for a different reason. I'm fixing this with lp:844160.