Bug 1490182

Summary:	boot_option:local is being expected in capabilities when using scheduler hints
Product:	Red Hat OpenStack	Reporter:	Sai Sindhur Malleni <smalleni>
Component:	openstack-ironic	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED DUPLICATE	QA Contact:	mlammon
Severity:	low	Docs Contact:
Priority:	low
Version:	12.0 (Pike)	CC:	bfournie, mburns, rhel-osp-director-maint, srevivo
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-02 10:54:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sai Sindhur Malleni 2017-09-11 03:37:54 UTC

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:

Comment 1 Bob Fournier 2017-09-20 14:22:02 UTC

This is covered in https://bugzilla.redhat.com/show_bug.cgi?id=1373476, although its not explicit.

Marking this for inclusion in OSP-13.

Comment 2 Dmitry Tantsur 2017-10-02 10:54:48 UTC

Hi! It's working as designed as of now, because we have to overwrite the default boot option. Marking as a duplicate of 1373476, as that's where we're going to fix it.

*** This bug has been marked as a duplicate of bug 1373476 ***