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 <michele@acksyn.org>
Change-Id: I980dfc54b799c6b1d648489a727a590dd26fa502
Closes-Bug: 1918642
(cherry picked from commit c8a828aab2
)
This commit is contained in:
parent
5651573e2d
commit
a6c7ba02a9
|
@ -693,7 +693,7 @@ outputs:
|
|||
- if:
|
||||
- internal_tls_enabled
|
||||
- glance_api_tls_proxy:
|
||||
start_order: 2
|
||||
start_order: 3
|
||||
image: *glance_api_image
|
||||
net: host
|
||||
user: root
|
||||
|
|
|
@ -420,6 +420,7 @@ outputs:
|
|||
- if:
|
||||
- internal_tls_enabled
|
||||
- swift_proxy_tls_proxy:
|
||||
start_order: 3
|
||||
image: *swift_proxy_image
|
||||
net: host
|
||||
user: root
|
||||
|
|
Loading…
Reference in New Issue