Description of problem:

When using profiles/flavors, the capabilities of the node are considered for filtering only if they are present in the flavor of the node. For example, looking athe control flavor on the undercloud we see
| properties                 | capabilities:boot_option='local'

and thereforce this property would need to be present in the ironic node for it to be scheduled as a controller. However, when using shceduler hints to tag each node with node like, u'capabilities': u'node:controller-1; 

boot_option: local is still being expected. Ideally this shouldn't be needed, like i nthe case of flavor/profile matching, we could easily remove this from capabilities of the ironic node an dalso the properties of the flavor to successfully deploy. 



Version-Release number of selected component (if applicable):
12

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: