Comment 3 for bug 1883599

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (master)

Reviewed: https://review.opendev.org/736246
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=cbf5837fb0238612fc7837980892bda3e1aa4f7b
Submitter: Zuul
Branch: master

commit cbf5837fb0238612fc7837980892bda3e1aa4f7b
Author: Andy Ning <email address hidden>
Date: Wed Jun 17 10:21:32 2020 -0400

    Set up /var/run/sysinv as sysinv's default temp files location

    sysinv call the k8s python client to perform a number of operations.
    The k8s python client creates temp files under /tmp and continues to
    use these tmp files for the life-cycle of the processes.

    However systemd-tmpfiles-clean.service will run every day to clean up
    files in /tmp dir that are older than 10 days. If the k8s client code
    is not triggered for more than 10 days (thus its temp files are not
    accessed for more than 10 days), these temp files will be removed as
    part of the cleanup. Certain sysinv operations then starts to fail with
    an error that the tmp file is no longer there.

    This is a known issue of kubernetes python client:
    https://github.com/kubernetes-client/python/issues/765

    The commit fixes this issue by setting TMPDIR to /var/run/sysinv when
    sm starts sysinv-conductor and sysinv-inv.

    Change-Id: I365d637abd080bd03b65758e4e8db9203d6bfa4d
    Closes-Bug: 1883599
    Signed-off-by: Andy Ning <email address hidden>