Use the default flavor name when flavor parameter is not defined
This patch ensures that the default flavor is used when the flavor
parameter (Overcloud{{role.name}}Flavor) is not explicitly defined
in deployment templates and plan, to emulate the behavior in tht
to pick up the defalt flavor to deploy baremetal instances.
Closes-Bug: #1901472
Change-Id: I6970a7fc294305d4fe6ad43b9c2e29090a1ecb37
(cherry picked from commit c0698312ad
)
This commit is contained in:
parent
fc0fa9b5af
commit
d949f0eb51
|
@ -63,7 +63,7 @@ class LookupModule(LookupBase):
|
||||||
return {
|
return {
|
||||||
'name': role['name'],
|
'name': role['name'],
|
||||||
'count': role.get('CountDefault', 0),
|
'count': role.get('CountDefault', 0),
|
||||||
'flavor': None
|
'flavor': role.get('FlavorDefault', 'baremetal')
|
||||||
}
|
}
|
||||||
|
|
||||||
roles = list(map(default_role_data, roles_data))
|
roles = list(map(default_role_data, roles_data))
|
||||||
|
|
Loading…
Reference in New Issue