roles list action parses root template to bring list of roles, this is not compatible with custom roles
Bug #1637308 reported by
Toure Dunnon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
roles list action should return json version of roles_data.yaml, enhance roles_data.yaml to include role identifier (used for nodes and flavor tagging, e.g. 'block-storage') role name ('BlockStorage'), role title ('Block Storage') and role description.
tags: | added: workflows |
tags: | added: tripleo-common |
Changed in tripleo: | |
milestone: | ocata-1 → ocata-2 |
Changed in tripleo: | |
milestone: | ocata-2 → ocata-3 |
Changed in tripleo: | |
milestone: | ocata-3 → pike-1 |
Changed in tripleo: | |
milestone: | pike-1 → pike-2 |
Changed in tripleo: | |
milestone: | pike-2 → pike-3 |
Changed in tripleo: | |
milestone: | pike-3 → pike-rc1 |
Changed in tripleo: | |
milestone: | pike-rc1 → queens-1 |
To post a comment you must log in.
Actually I think it will work fine because the role list logic looks at the ResourceGroup names (which are still generated for custom roles), but we should still look at reworking this as it's a fragile and indirect relationship which we currently use (instead we should simply parse the list of names from the roles_data.yaml in the plan.