Reviewed: https://review.openstack.org/531373 Committed: https://git.openstack.org/cgit/openstack/charm-cinder/commit/?id=6b2363f11eb2870ce0d8828d6d05a0ab6d59bb9f Submitter: Zuul Branch: master
commit 6b2363f11eb2870ce0d8828d6d05a0ab6d59bb9f Author: Seyeong Kim <email address hidden> Date: Fri Jan 5 22:09:18 2018 +0900
Fix ssl config update when api node is split
Currently, if we deploy cinder-api and cinder-volume to different nodes, ssl_key and ssl_cert don't get configured on the api node.
The ApacheSSLContext's __call__ method should gate on the 'api' service being enabled, rather than 'cinder-common'.
Change-Id: I6d5d6710a73f9393ad7c45c3307925b10cda641d Closes-bug: #1741479
Reviewed: https:/ /review. openstack. org/531373 /git.openstack. org/cgit/ openstack/ charm-cinder/ commit/ ?id=6b2363f11eb 2870ce0d8828d6d 05a0ab6d59bb9f
Committed: https:/
Submitter: Zuul
Branch: master
commit 6b2363f11eb2870 ce0d8828d6d05a0 ab6d59bb9f
Author: Seyeong Kim <email address hidden>
Date: Fri Jan 5 22:09:18 2018 +0900
Fix ssl config update when api node is split
Currently, if we deploy cinder-api and cinder-volume to different nodes,
ssl_key and ssl_cert don't get configured on the api node.
The ApacheSSLContext's __call__ method should gate on the 'api' service
being enabled, rather than 'cinder-common'.
Change-Id: I6d5d6710a73f93 93ad7c45c330792 5b10cda641d
Closes-bug: #1741479