composable service resource registry parameters make workflow to fail
Bug #1743575 reported by
Michael Henkel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Michael Henkel |
Bug Description
Description
===========
In case a custom role needs a custom service, the resource_registry is defined in an environment file which is added to the cli:
e.g. role:
ServicesDefault:
- OS::TripleO:
environment file:
resource_registry:
OS::TripleO:
Creating a stack fails because tripleo cannot find the resource registry for the service, even though it is defined in the environment file and the file is added with -e to the openstack overcloud deploy command.
Steps to reproduce
==================
Create a stack with a custom role and service
Environment
===========
tripleo-dev
Changed in tripleo: | |
assignee: | Michael Henkel (mhenkel-3) → Steven Hardy (shardy) |
Changed in tripleo: | |
assignee: | Steven Hardy (shardy) → Michael Henkel (mhenkel-3) |
Changed in tripleo: | |
milestone: | none → queens-3 |
importance: | Undecided → High |
Changed in tripleo: | |
milestone: | queens-3 → queens-rc1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/534337
Review: https:/