Must have a role named Controller running memcached when using custom roles due to hardcoded ControllerIpListMap

Bug #1632822 reported by James Slagle on 2016-10-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

In overcloud.j2.yaml there is:

      # FIXME(shardy): These require further work to move into service_ips
      memcache_node_ips: {get_attr: [ControllerIpListMap, net_ip_map, {get_attr: [ServiceNetMap, service_net_map, MemcachedNetwork]}]}

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
Steven Hardy (shardy) wrote :

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.

tags: added: composable-roles
Steven Hardy (shardy) on 2016-11-14
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
Ben Nemec (bnemec) wrote :
Changed in tripleo:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers