docker_puppet_tasks won't run unless service is in primary node

Bug #1767972 reported by Juan Antonio Osorio Robles on 2018-04-30
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
High
Juan Antonio Osorio Robles

Bug Description

Actions in docker_puppet_tasks will only run in the bootstrap node. However, there isn't any logic to enforce that these tasks actually get written to the primary node.
So, for instance, you if deploy keystone in a role that's not the primary, nothing will create the users and endpoints.

We need to have the bootstrap node have the docker_puppet_tasks written to it so it can execute them.

Changed in tripleo:
status: New → Triaged
importance: Undecided → High
milestone: none → rocky-2

Fix proposed to branch: master
Review: https://review.openstack.org/565172

Changed in tripleo:
assignee: nobody → Juan Antonio Osorio Robles (juan-osorio-robles)
status: Triaged → In Progress

Change abandoned by Juan Antonio Osorio Robles (<email address hidden>) on branch: master
Review: https://review.openstack.org/565172

Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Changed in tripleo:
milestone: stein-2 → stein-3
Changed in tripleo:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers