![]() The logs for the glance_api_tls_proxy containers are not persisted on
the host and hence get lost at the restart of the container. Said
container has httpd inside of it so we need to make sure that the httpd
logs are persisted on the host just like the other containers that use
httpd.
Tested this review and I correctly get the logs persisted on a
TLS-everywhere environment:
[root@controller-0 ~]# ls -l /var/log/containers/httpd/glance/
total 1040
-rw-r--r--. 1 root root 5864 Nov 28 10:07 error_log
-rw-r--r--. 1 root root 544043 Nov 28 11:17 glance-api-proxy_access_ssl.log
-rw-r--r--. 1 root root 4360 Nov 28 10:07 glance-api-proxy_error_ssl.log
NB: Slight conflict on deployment/glance/glance-api-logging-file-container.yaml
Change-Id: Id4f24e171867adc445eca55b3908360c8f3f6f30
Closes-Bug: #1854343
(cherry picked from commit
|
||
---|---|---|
.. | ||
glance-api-container-puppet.yaml | ||
glance-api-logging-file-container.yaml | ||
glance-api-logging-stdout-puppet.yaml |