Comment 6 for bug 1000403

** Impact **

The multi scheduler allows the routing of VM-related ops to the compute_driver and the routing of Volume-related ops to the volume_driver.

Unfortunately, the Multi Scheduler does not handle capabilities updates correctly in that it does not pass the information on to the child schedulers. So when a request gets to the FilterScheduler (which is the default compute scheduler), the latter does not have any host capabilities, thus making a ComputeFilter fail to choose a specific host. This occur particularly if host selection is made based on the flavor's extra specs.

** Development Fix **

This has been addressed in: https://review.openstack.org/7526 and fixed in quantal

** Stable fix **

This has been addressed in: https://review.openstack.org/7592

** Test Case **

Run the nova.tests.scheduler tests

** Regression **

Minimal this has been tested in openstack-ci and has past tests.