After RHOCP upgrade to v4.16 iptables-alerter pods are stuck in CreateContainerError state

Issue

• After RHOCP cluster upgrade, network operator stuck in progressing state.

• iptables-alerter pods in the openshift-network-operator namespace are stuck in a CreateContainerError state with below error,

  $ oc get pod <pod-name> -o yaml -n openshift-network-operator
  
  - image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:dec071164a68d135905f27e593b42be7ac14002c938fb08613c59c629c6c4f80
  imageID: ""
  lastState:
    terminated:
      exitCode: 137
      finishedAt: null
      message: The container could not be located when the pod was deleted.  The
        container used to be Running
      reason: ContainerStatusUnknown                                               <======= 
      startedAt: null
  name: iptables-alerter
  ready: false
  restartCount: 1
  started: false
  state:
    waiting:
      message: context deadline exceeded                                           <=======
      reason: CreateContainerError                                                 <=======