It rarely happen, sometimes after run auto case, no egressIP object left, but still having cloudprivateipconfig IP there. 

4.14.0-0.nightly-2023-09-02-132842 

rarely

Run auto case OCP-47028, basically did below steps
1. Label one node as egress node
2. Create egressIP object
3.  Verify the egressIP was assigned to egress node
4. Remove egress label from previous egress node, add label to another node
5. Waiting egressIP to assign to the new egress node
Generally it would take some time for egressIP moving to new node, during this time, 
Delete egressIP object

% oc get egressip      
No resources found
 % oc get cloudprivateipconfig 
NAME         AGE
10.0.1.153   52m

 oc get cloudprivateipconfig  -o yaml
apiVersion: v1
items:
- apiVersion: cloud.network.openshift.io/v1
  kind: CloudPrivateIPConfig
  metadata:
    annotations:
      k8s.ovn.org/egressip-owner-ref: egressip-47028
    creationTimestamp: "2023-09-07T05:01:38Z"
    finalizers:
    - cloudprivateipconfig.cloud.network.openshift.io/finalizer
    generation: 1
    name: 10.0.1.153
    resourceVersion: "42816"
    uid: 63f827f3-cc0a-4a33-8855-c915afbbd480
  spec:
    node: huirwang-0907deb-9kdks-worker-usgovvirginia2-4txl7
  status:
    conditions:
    - lastTransitionTime: "2023-09-07T05:02:42Z"
      message: IP address successfully added
      observedGeneration: 1
      reason: CloudResponseSuccess
      status: "True"
      type: Assigned
    node: huirwang-0907deb-9kdks-worker-usgovvirginia2-4txl7
kind: List
metadata:
  resourceVersion: ""

The cloudprivateipconfig IP should be cleared