Must have a role named Controller running memcached when using custom roles due to hardcoded ControllerIpListMap
Bug #1632822 reported by
James Slagle
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Unassigned |
Bug Description
In overcloud.j2.yaml there is:
# FIXME(shardy): These require further work to move into service_ips
memcache_
The hardcoded resource name ControllerIpListMap means that a role named "Controller" must be present and it should be running the memcached service given we are adding its ip to memcache_node_ips.
The FIXME is probably meant to address this issue, but I did not see a bug filed, so that's why I'm filing one.
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → ocata-1 |
Changed in tripleo: | |
milestone: | ocata-1 → ocata-2 |
Changed in tripleo: | |
milestone: | ocata-2 → ocata-3 |
Changed in tripleo: | |
milestone: | ocata-3 → ocata-rc1 |
Changed in tripleo: | |
milestone: | ocata-rc1 → ocata-rc2 |
Changed in tripleo: | |
milestone: | ocata-rc2 → 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 |
To post a comment you must log in.
Thanks, yeah I meant to get to this and never did - we'll need to address this in puppet-tripleo in a similar way to how we assemble the ipv6 lists for ceph.