ChanceScheduler doesn't return properly the nodename attribute
Bug #1692521 reported by
Sylvain Bauza
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Low
|
Unassigned |
Bug Description
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.
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Low |
assignee: | nobody → Sylvain Bauza (sylvain-bauza) |
tags: | added: ironic scheduler |
Changed in nova: | |
assignee: | Sylvain Bauza (sylvain-bauza) → Chris Dent (cdent) |
Changed in nova: | |
assignee: | Chris Dent (cdent) → Sylvain Bauza (sylvain-bauza) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/466725
Review: https:/