docker-puppet tasks can only run on the primary controller role
Bug #1792613 reported by
Steven Hardy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Steven Hardy |
Bug Description
We calculate a global bootstrap_node_id for the docker-puppet tasks:
https:/
This is a problem because if you move e.g Keystone to some role that is not the role tagged primary/controller we fail to run the docker-puppet tasks.
In the past we added per-service bootstrap node IDs for composable HA to avoid similar problems, so we need the docker-puppet bootstrapping/tasks to consider the same data - that should ensure compatibility with composable roles/services.
More information in this downstream bz: https:/
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Steven Hardy (shardy) |
milestone: | none → stein-2 |
tags: | added: tech-debt |
Changed in tripleo: | |
milestone: | stein-2 → stein-3 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/605046
Review: https:/