glance_api_tls_proxy logs are not persisted

[Michele Baldessari]

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

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/696520

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/696520
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=f22dce44779a3b2d0f08c991d388b2c55829664a
Submitter: Zuul
Branch: master

commit f22dce44779a3b2d0f08c991d388b2c55829664a
Author: Michele Baldessari <email address hidden>
Date: Thu Nov 28 12:16:05 2019 +0100

    Make sure glance_api_tls_proxy logs are persisted on the host

    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

    Change-Id: Id4f24e171867adc445eca55b3908360c8f3f6f30
    Closes-Bug: #1854343

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/696640
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=a764b832e2fc17bd3087d08c129a3b53d2bf083b
Submitter: Zuul
Branch: stable/train

commit a764b832e2fc17bd3087d08c129a3b53d2bf083b
Author: Michele Baldessari <email address hidden>
Date: Thu Nov 28 12:16:05 2019 +0100

    Make sure glance_api_tls_proxy logs are persisted on the host

    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 f22dce44779a3b2d0f08c991d388b2c55829664a)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/stein
Review: https://review.opendev.org/696705

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/696705
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=53465f7f298af33bd0404ed10af09f76b7eab0d8
Submitter: Zuul
Branch: stable/stein

commit 53465f7f298af33bd0404ed10af09f76b7eab0d8
Author: Michele Baldessari <email address hidden>
Date: Thu Nov 28 12:16:05 2019 +0100

    Make sure glance_api_tls_proxy logs are persisted on the host

    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 f22dce44779a3b2d0f08c991d388b2c55829664a)
    (cherry picked from commit a764b832e2fc17bd3087d08c129a3b53d2bf083b)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/696904

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/696904
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=cc98ad60ef1181bf0c0582c081022fa4b4592ec2
Submitter: Zuul
Branch: stable/rocky

commit cc98ad60ef1181bf0c0582c081022fa4b4592ec2
Author: Michele Baldessari <email address hidden>
Date: Thu Nov 28 12:16:05 2019 +0100

    Make sure glance_api_tls_proxy logs are persisted on the host

    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 f22dce44779a3b2d0f08c991d388b2c55829664a)
    (cherry picked from commit a764b832e2fc17bd3087d08c129a3b53d2bf083b)
    (cherry picked from commit 53465f7f298af33bd0404ed10af09f76b7eab0d8)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/queens
Review: https://review.opendev.org/699355

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/699355
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=05e7406a2b346e9b84cf0c6cd605cc26935997f6
Submitter: Zuul
Branch: stable/queens

commit 05e7406a2b346e9b84cf0c6cd605cc26935997f6
Author: Michele Baldessari <email address hidden>
Date: Thu Nov 28 12:16:05 2019 +0100

    Make sure glance_api_tls_proxy logs are persisted on the host

    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 f22dce44779a3b2d0f08c991d388b2c55829664a)
    (cherry picked from commit a764b832e2fc17bd3087d08c129a3b53d2bf083b)
    (cherry picked from commit 53465f7f298af33bd0404ed10af09f76b7eab0d8)
    (cherry picked from commit cc98ad60ef1181bf0c0582c081022fa4b4592ec2)

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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