Description of problem: novacontrol.yaml is missing in https://github.com/openstack/tripleo-heat-templates/tree/master/roles
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. Deploy RHOS-12 with 1 undercloud, 1 compute, 1 controller and 1 novacontrol
2. Generate openstack roles with the above mentioned topology
[stack@undercloud-0 roles]$ openstack overcloud roles generate -o /home/stack/composable_roles/roles/roles_data.yaml \
> Novacontrol \
> Controller \
> Compute \
Invalid roles requested: Novacontrol
Expected results: Deploment runs successfully
I'm not sure what is Novacontrol (probably a custom role that you created) but not something that exists upstream, hence, I'm not sure about the bug. Feel free to re-open if you have more details about the actual problem. I think your roles_data is wrong and doesn't contain your custom role.
(In reply to Emilien Macchi from comment #1)
> I'm not sure what is Novacontrol (probably a custom role that you created)
> but not something that exists upstream, hence, I'm not sure about the bug.
> Feel free to re-open if you have more details about the actual problem. I
> think your roles_data is wrong and doesn't contain your custom role.
I believe Novacontrol is the standalone role hosting the Nova control plane services(the 'Nova' role as advertised in the supported custom roles by the product docs). THT doesn't provide such predefined role but it is required for testing. Given that we want to use the new way of generating roles_data starting with OSP12 and not build the roles_data manually then we need this role to be available in $THT/roles.
Opening this back up as a Compute DFG RFE to track the novacontrol role into THT and ensure it is tested ahead of the OSP 13 release.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.