Currently the stx-openstack application apply is failing during
the fm-rest-api helm chart, and the pod log indicate a file not
found error while creating the log handler, as it uses a syslog
handler (/dev/log socket) that doesn't exist on the pod.
This change includes an environment variable to indicate that
it is running in a container, so that when in this condition fm
writes it's logs to standard output instead of using the syslog
handler.
Reviewed: https:/ /review. opendev. org/c/starlingx /helm-charts/ +/818454 /opendev. org/starlingx/ helm-charts/ commit/ 4c6bd7423d776a9 14ef6743fcb50a6 f7434d324a
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 4c6bd7423d776a9 14ef6743fcb50a6 f7434d324a
Author: Heitor Matsui <email address hidden>
Date: Thu Nov 18 16:14:06 2021 -0300
Include CONTAINER env var in fm helm chart
Currently the stx-openstack application apply is failing during
the fm-rest-api helm chart, and the pod log indicate a file not
found error while creating the log handler, as it uses a syslog
handler (/dev/log socket) that doesn't exist on the pod.
This change includes an environment variable to indicate that
it is running in a container, so that when in this condition fm
writes it's logs to standard output instead of using the syslog
handler.
Partial-Bug: 1951579 8878843730143bb 1e5f8d6a6fd
Signed-off-by: Heitor Matsui <email address hidden>
Change-Id: Icd853ae34851df