Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-52982

Fix audit-logs container to properly handle SIGTERM

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.15, 4.16, 4.17, 4.18
    • HyperShift
    • None
    • False
    • Hide

      None

      Show
      None
    • Hide
      *Cause*: Default behavior
      *Consequence*: Audit-logs container does not respect sigterm signal and times out requiring sigkill
      *Fix*: Properly kill the process with correct syntax of PID alias
      *Result*: Bug isn't present anymore.
      Show
      *Cause*: Default behavior *Consequence*: Audit-logs container does not respect sigterm signal and times out requiring sigkill *Fix*: Properly kill the process with correct syntax of PID alias *Result*: Bug isn't present anymore.
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-50523. The following is the description of the original issue:
      —
      Description of problem:

          Audit-logs container was adjusted previously to handle SIGTERM using a trap and cleanup function. However due to behavior described here https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.23/#container-v1-core the `$$` used to grab PID is not properly interpreted. This issue is to fix the script to handle this behavior correctly and make the cleanup be consistent with the changes to apply-bootstrap container for a similar ignored SIGTERM issue.

      Version-Release number of selected component (if applicable):

      How reproducible:

      Steps to Reproduce:

          1. Create a hypershift cluster with auditing enabled
    2. Delete apiserver pods and observe the script does not correctly handle sigterm.
    3.

      Actual results:

      Expected results:

      Additional info:

              Unassigned Unassigned
              openshift-crt-jira-prow OpenShift Prow Bot
              Jie Zhao Jie Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: