Description of problem: 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. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Deploy overcloud without Overcloud{{role.name}}Flavor 2. Run collect-flavors-and-verify-profiles validation Actual results: The validation fails with "Role '<role name>' is in use, but has no flavor assigned" Expected results: The validation does not fail with the above message Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 16.1.3 bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:5413