From c8a828aab297500176d2f9e9e0b05d47d60e4645 Mon Sep 17 00:00:00 2001 From: Giulio Fidente Date: Thu, 11 Mar 2021 11:48:00 +0100 Subject: [PATCH] Fix start order for {swift_proxy,glance_api}_tls_proxy In stack updates adding TLS to Swift would not work because swift_proxy_tls_proxy is started when the pre-existing swift_proxy container is still up and listening on the TCP port which should instead be used by swift_proxy_tls_proxy This change ensures swift_proxy_tls_proxy and glance_api_tls_proxy containers are started after the actual swift_proxy and glance_api containers are started. Co-Authored-By: Michele Baldessari Change-Id: I980dfc54b799c6b1d648489a727a590dd26fa502 Closes-Bug: 1918642 --- deployment/glance/glance-api-container-puppet.yaml | 2 +- deployment/swift/swift-proxy-container-puppet.yaml | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/deployment/glance/glance-api-container-puppet.yaml b/deployment/glance/glance-api-container-puppet.yaml index 3d5583741d..a7b7623df6 100644 --- a/deployment/glance/glance-api-container-puppet.yaml +++ b/deployment/glance/glance-api-container-puppet.yaml @@ -694,7 +694,7 @@ outputs: - if: - internal_tls_enabled - glance_api_tls_proxy: - start_order: 2 + start_order: 3 image: *glance_api_image net: host user: root diff --git a/deployment/swift/swift-proxy-container-puppet.yaml b/deployment/swift/swift-proxy-container-puppet.yaml index badf960112..db88c83a3a 100644 --- a/deployment/swift/swift-proxy-container-puppet.yaml +++ b/deployment/swift/swift-proxy-container-puppet.yaml @@ -410,6 +410,7 @@ outputs: - if: - internal_tls_enabled - swift_proxy_tls_proxy: + start_order: 3 image: *swift_proxy_image net: host user: root