On IBM Powervs cluster provided by IBM team, getting "unable to start container process" when trying to execute ovn-nbtrl command on ovnkube-node northd container

    always reproducible especially when running automated case, 

    1. on IBM powervs cluster, ran automated OCP-54647 or follow the steps in the case, https://github.com/openshift/openshift-tests-private/blob/master/test/extended/networking/cloud_egressip_ovn.go#L3025

2. when script checks SNAT,

  STEP: 6. Check SNATs of stateful pod and completed pod on the egressNode before rebooting it.
 04/28/24 09:47:40.612
  Apr 28 09:47:40.612: INFO: Running 'oc --kubeconfig=/home/jechen/kubeconfig-416ec4-wdc07.txt get pods -n openshift-ovn-kubernetes -l app=ovnkube-node --field-selector spec.nodeName=rdr-ipi2-416ec4-aish-g5bb6-worker-jmn8x -o jsonpath='{..metadata.name}''
  Apr 28 09:47:50.875: INFO: Running 'oc --kubeconfig=/home/jechen/kubeconfig-416ec4-wdc07.txt exec -n openshift-ovn-kubernetes ovnkube-node-lpvqw -c northd -- ovn-nbctl lr-nat-list GR_rdr-ipi2-416ec4-aish-g5bb6-worker-jmn8x | grep 192.168.190.235 |awk '{print $3}''
  Apr 28 09:47:51.470: INFO: Error running /usr/local/bin/oc --kubeconfig=/home/jechen/kubeconfig-416ec4-wdc07.txt exec -n openshift-ovn-kubernetes ovnkube-node-lpvqw -c northd -- ovn-nbctl lr-nat-list GR_rdr-ipi2-416ec4-aish-g5bb6-worker-jmn8x | grep 192.168.190.235 |awk '{print $3}':
  time="2024-04-28T13:47:51Z" level=error msg="exec failed: unable to start container process: exec: \"ovn-nbctl lr-nat-list GR_rdr-ipi2-416ec4-aish-g5bb6-worker-jmn8x | grep 192.168.190.235 |awk '{print $3}'\": executable file not found in $PATH"
  command terminated with exit code 255
    

    getting "unable to start container process" when trying to execute ovn-nbctl command on ovnkube-node northd container

    no error, executing ovn-nbctl command should work

    must-gather: https://drive.google.com/file/d/1ZzLcJyLLUQJQI_ZUN52TGHOpL79HpWpB/view?usp=drive_link