commit 87b16ddbfc19263e81bf49a5c643855c98ffb240
Author: Steven Hardy <email address hidden>
Date: Thu Dec 13 17:56:44 2018 +0000
run docker_puppet_tasks on any role
Currently this assumes all tasks will run on the primary controller
but because of composable roles, that may not be the case.
An example is if you deploy keystone on any role other than the
role tagged primary e.g Controller by default, we don't create
any of the users/endpoints because the tasks aren't written to
the role unless keystone actually runs there.
Conflicts:
common/deploy-steps-tasks.yaml
Closes-Bug: #1792613
Change-Id: Ib6efd03584c95ed4ab997f614aa3178b01877b8c
(cherry picked from commit a0a09d29aac1ad44fa48dae5d1db72e3905aeb69)
Reviewed: https:/ /review. openstack. org/632714 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=87b16ddbfc1 9263e81bf49a5c6 43855c98ffb240
Committed: https:/
Submitter: Zuul
Branch: stable/rocky
commit 87b16ddbfc19263 e81bf49a5c64385 5c98ffb240
Author: Steven Hardy <email address hidden>
Date: Thu Dec 13 17:56:44 2018 +0000
run docker_puppet_tasks on any role
Currently this assumes all tasks will run on the primary controller
but because of composable roles, that may not be the case.
An example is if you deploy keystone on any role other than the
role tagged primary e.g Controller by default, we don't create
any of the users/endpoints because the tasks aren't written to
the role unless keystone actually runs there.
Conflicts: deploy- steps-tasks. yaml
common/
Closes-Bug: #1792613 d4ab997f614aa31 78b01877b8c 4fa48dae5d1db72 e3905aeb69)
Change-Id: Ib6efd03584c95e
(cherry picked from commit a0a09d29aac1ad4