collect-flavors-and-verify-profiles validation fails when Overcloud{{role.name}}Flavor is not explicitly defined in templates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Undecided
|
Takashi Kajinami |
Bug Description
Description
===========
collect-
"msg": "Role 'Controller' is in use, but has no flavor assigned\nRole 'Compute' is in use, but has no flavor assigned\nRole..."
It seems that this validation requires that Overcloud{
However this flavor parameter is not required in tripleo-
So we should implement the same logic to pick up the default value automatically, instead of requiring users add these parameters just for validation.
Steps to reproduce
==================
* Deploy overcloud without Overcloud{
* Run collect-
Expected result
===============
The validation fails with the error "Role 'Controller' is in use, but has no flavor assigned"
Actual result
=============
The validation doesn't fail with the above message
Environment
===========
This issue was initially reported in https:/
Logs & Configs
==============
summary: |
- collect-flavors-and-verify-profiles validation fails with the following - message, "msg": "Role 'Controller' is in use, but has no flavor - assigned\nRole 'Compute' is in use, but has no flavor assigned\nRole..." - It seems that this validation requires that Overcloud{{role.name}}Flavor - parameter is explicitly set. However this flavor parameter is not - required in tripleo-heat-templates, and the default flavor (baremetal or - FlavorDefault defined in roles_data.yaml) is used if the parameter is - not defined in deployment templates. So we should implement the same - logic to pick up the default value automatically, instead of requiring - users add these parameters just for validation. + collect-flavors-and-verify-profiles validation fails when + Overcloud{{role.name}}Flavor is not explicitly defined in templates |
description: | updated |
Fix proposed to branch: master /review. opendev. org/759607
Review: https:/