Use sticky bit for init logs containers in t-h-t

[Bogdan Dobrelya]

Let's extend https://review.opendev.org/#/c/681954/ to other services as well

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/rocky
Review: https://review.opendev.org/682007

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/queens
Review: https://review.opendev.org/682009

[OpenStack Infra (hudson-openstack)]

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

commit 4a85b932f4715e521939d04a80884d05ea06ce55
Author: Kevin Carter <email address hidden>
Date: Tue Sep 10 11:31:28 2019 -0500

    Resolve broken zaqar container caused by logging issues

    The zaqar container is broken due to the log file being owned by root. When
    the zaqar-server log file is unabnle to be written to by the zaqar process
    it causes a traceback resulting in 500 errors. This change ensures that the
    zaqar log directory has the proper permissions and that the log file within
    the directory is created when the container is started. A sticky bit is
    being used on the zaqar log directory to ensure all files created within
    the directory retain group expected permissions in almost all circumstances.

    Related-Bug: #1843875

    Change-Id: I63442f0bdec11179c361f503906166f75c5e0355
    Signed-off-by: Kevin Carter <email address hidden>
    (cherry picked from commit 4579d42e8d4e0f651f6c12137fb2c61d002b37ad)

[OpenStack Infra (hudson-openstack)]

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

commit c6752d70ec62ac563db235ebc9ff07898d85da84
Author: Kevin Carter <email address hidden>
Date: Tue Sep 10 11:31:28 2019 -0500

    Resolve broken zaqar container caused by logging issues

    The zaqar container is broken due to the log file being owned by root. When
    the zaqar-server log file is unabnle to be written to by the zaqar process
    it causes a traceback resulting in 500 errors. This change ensures that the
    zaqar log directory has the proper permissions and that the log file within
    the directory is created when the container is started. A sticky bit is
    being used on the zaqar log directory to ensure all files created within
    the directory retain group expected permissions in almost all circumstances.

    Related-Bug: #1843875

    Change-Id: I63442f0bdec11179c361f503906166f75c5e0355
    Signed-off-by: Kevin Carter <email address hidden>
    (cherry picked from commit 4579d42e8d4e0f651f6c12137fb2c61d002b37ad)