Cluster stuck in inconsistent state when nlb is deleted out of lifecycle.

[sindhusri16]

What happened:
User manually deleted the nlb hosting the control plane of the cluster from console. Deletion of this cluster is stuck in an inconsistent state as nlb reconciler is always hitting a 404 not found when searching for this nlb.

What you expected to happen:
Cluster should not be stuck in 'deleting' phase, it could reconcile the nlb as deleted and go forward with deletion.

How to reproduce it (as minimally and precisely as possible):
Create a cluster and delete the nlb-apiserver from console, then delete the cluster.

Anything else we need to know?:
Logs:
kubectl get events -A | grep oke-amaaaaaakdrwrhiamr4gonrrnvrts6bs
oke 14m Normal FailureDomainsReady ocicluster/oke-amaaaaaakdrwrhiamr4gonrrnvrts6bs FailureDomain is in ready state
oke 48m Warning ReconcileError ocicluster/oke-amaaaaaakdrwrhiamr4gonrrnvrts6bs failed to reconcile Api Server Network Loadbalancer: Error returned by NetworkLoadBalancer Service. Http Status Code: 404. Error Code: NotAuthorizedOrNotFound. Opc request id: . Message: Authorization failed or requested resource not found....
oke 31m Warning ReconcileError ocicluster/oke-amaaaaaakdrwrhiamr4gonrrnvrts6bs failed to reconcile Api Server Network Loadbalancer: Error returned by NetworkLoadBalancer Service. Http Status Code: 404. Error Code: NotAuthorizedOrNotFound. Opc request id: . Message: Authorization failed or requested resource not found....
oke 14m Warning ReconcileError ocicluster/oke-amaaaaaakdrwrhiamr4gonrrnvrts6bs failed to reconcile Api Server Network Loadbalancer: Error returned by NetworkLoadBalancer Service. Http Status Code: 404. Error Code: NotAuthorizedOrNotFound. Opc request id: . Message: Authorization failed or requested resource not found.

Environment:

• CAPOCI version: v0.11.5
• Cluster-API version (use clusterctl version):
• Kubernetes version (use kubectl version):
• Docker version (use docker info):
• OS (e.g. from /etc/os-release):

[sindhusri16]

Could the team please confirm the ETA for this fix.

[shyamradhakrishnan]

Approx ETA: 28/Feb/2024