-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
4.15.z, 4.16.z
-
None
-
False
-
-
-
-
-
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.
- duplicates
-
OCPBUGS-37763 iptables-alerter logs spurious events under heavy load
- Closed