EgressIP configuration at Openshift cluster hosted on AWS failing due to missing annotation

Issue

• EgressIP is not being assigned to the primary interface of the node as per hostsubnet definition.

• cloud.network.openshift.io/egress-ipconfig annotation is missing from the custom resource definition of the node and that causing problems while cloud-network-config-controller is trying to assign Egress IP to the primary interface of the node.

  E0916 11:50:59.868220 2217 egressip.go:254] Ignoring invalid HostSubnet ip-x-x-x-x.ap-southwest-1.compute.internal (host: "ip-x-x-x-x.ap-southwest-1.compute.internal", ip: "x.x.x.x", subnet: "10.128.0.0/23"): related node object "ip-x-x-x-x.ap-southwest-1.compute.internal" has an incomplete annotation "cloud.network.openshift.io/egress-ipconfig", CloudEgressIPConfig: <nil>
  

• EgressIP is not being assigned to the primary interface of the node while using Manual CredentialsMode.