ChanceScheduler doesn't return properly the nodename attribute

[Sylvain Bauza]

ChanceScheduler was implemented before multiple nodes were possible for the same nova-compute service.
As a result, it returns a tuple (host, node, limits) where node is None but that's then not possible to know which ComputeNode object was provided. Instead, we should choose between all the related nodes so that ChanceScheduler could be used for Ironic driver.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/466725

[OpenStack Infra (hudson-openstack)]

Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/466725
Reason: This review is > 4 weeks without comment, and is not mergable in it's current state. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

[Sean Dague (sdague)]

There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.