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

Iptables-alert pod restart automatically

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • 09/09 customer is Nokia; may be fixed. BQI:Poor

      Description of problem:

      We can see the restart of iptables-alert pods automatically. Upon checking the last logs.
      
      ~~~
      The Event "iptables-alert-5rz9s" is invalid: involvedObject.namespace: Invalid value: "": does not match event.namespace
      ~~~

      How reproducible:

          Unable to reproduce manually, however, it automatically reproduced in my test cluster

      Actual results:

          There should not be any error.

      Additional info:

          The reason I can see here is, there is a `null` value in pod_namespace in the iptables-alert script.
      
      ~~~
      pod_namespace=$(crictl inspectp "${id}" | jq -r .status.metadata.namespace)
      ~~~
      
      There comes a situation here, when it is unable to fetch the namespace of the pod from crio and we are receiving null.

       

              dwinship@redhat.com Dan Winship
              rhn-support-nbhatt Neeraj Bhatt
              Anurag Saxena Anurag Saxena
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: