When running automated regression VRF SRIOV DHCP test cases Looks like a degradation bug. DHCP client pod stuck in ContainerCreating state.  The the server and client pods are configured with secondary VRF interfaces. The two VRFs have overlapping IP address ranges. It takes up to 7 mins for both server and client pods to recieve IP allocation from the dhcp server.

OCP 4.13.11

Run cnf-gotest 

1. BM cluster running OCP 4.13.11
2. Run VRF sriov cnf-gotests
3.

Pod with overlapping VRF IP addresses is stuck in ContainerCreating
Timed out after 120.001s.
Expected
    <v1.PodPhase>: Pending
to equal
    <v1.PodPhase>: Running

Container is meant to receive an IP address from the dhcp server and go to running state.

status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2023-09-12T11:35:49Z"
    status: "True"
    type: Initialized
  - lastProbeTime: null
    lastTransitionTime: "2023-09-12T11:35:49Z"
    message: 'containers with unready status: [test]'
    reason: ContainersNotReady
    status: "False"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2023-09-12T11:35:49Z"
    message: 'containers with unready status: [test]'
    reason: ContainersNotReady
    status: "False"
    type: ContainersReady
  - lastProbeTime: null
    lastTransitionTime: "2023-09-12T11:35:49Z"
    status: "True"
    type: PodScheduled
  containerStatuses:
  - image: quay.io/ocp-edge-qe/cnf-gotests-client:v4.13
    imageID: ""
    lastState: {}
    name: test
    ready: false
    restartCount: 0
    started: false
    state:
      waiting:
        reason: ContainerCreating
  hostIP: 10.46.186.39
  phase: Pending
  qosClass: BestEffort
  startTime: "2023-09-12T11:35:49Z"