redis_tls_proxy container is missing from tls-e deployments

Bug #1916873 reported by Michele Baldessari
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
High
Michele Baldessari

Bug Description

When we merged I5ce8367363d535b71b01395b0bef4cf17c8935b5 and moved pcs on host commands we erroneously also removed the redis_tls_proxy container which is needed for tls-e.
The reason for not noticing this is that redis will come up on the master node and will be functional. What is broken is the slave replication which is why this was not noticed at the time.

Revision history for this message
Michele Baldessari (michele) wrote :
Changed in tripleo:
milestone: wallaby-3 → wallaby-rc1
Changed in tripleo:
status: Triaged → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 13.2.0

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 11.5.0

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 12.4.3

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 14.1.0

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers