deployed-server doesn't work with overcloud ssl in ocata

[James Slagle]

In ocata (and newton), a custom role in place of the default controller
didn't work, b/c not all of the controller specific resources were
represented in role.role.j2.yaml, such as NodeTLSData and the hieradata tripleo::haproxy::service_certificate

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/547249

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/547249
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=eb8de76ad05d1df678a2a18fecb3f43be5b26f2b
Submitter: Zuul
Branch: stable/ocata

commit eb8de76ad05d1df678a2a18fecb3f43be5b26f2b
Author: James Slagle <email address hidden>
Date: Thu Feb 22 21:16:07 2018 -0500

    Handle NodeTLSData resources for controller roles

    In ocata (and newton), a custom role in place of the default controller
    didn't work, b/c not all of the controller specific resources were
    represented in role.role.j2.yaml.

    This patch makes it so that at least overcloud SSL configuration is
    handled by checking to see if the string "controller" is in the role
    name. This fixes the issue of using deployed-server with ssl for ocata.

    Change-Id: I7e8487208cc71a0780abc167d06902b9f3d3c983
    Closes-Bug: #1751179

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 6.2.11 release.