[BUG]: After restart Cilium throws errors

[lukapetrovic-git]

Summary

Restarting Cilium causes errors to be thrown, causing the role to fail.

OS: Ubuntu 22.04
Kernel: 5.15.0-94-generic
K8S Distro: RKE2 v1.27.12+rke2r1
Cilium 1.14.9

Ansible Version

ansible [core 2.16.5]
  config file = None
  configured module search path = ['/home/ansibleuser/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.10/dist-packages/ansible
  ansible collection location = /home/ansibleuser/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] (/usr/bin/python3)
  jinja version = 3.1.3
  libyaml = True

Repro Steps

1. Change Cilium config
2. Run the role on a cluster with Cilium already installed.
3. "wait for cilium to be running and ready" task fails after the allotted wait time.

Expected Results

No errors are thrown, and the "wait for cilium to be running and ready" completes successfully.

Actual Results

The following errors occur, and the "wait for cilium to be running and ready" task fails after the allotted wait time.
Errors: cilium cilium-5t9f2 controller sync-lb-maps-with-k8s-services is failing since 10s (8x): Unable to remove service &{hash:�� �Pz� frontend:{L3n4Addr:{AddrCluster:{addr:{addr:{hi:0 lo:281470859366422} z:0xc000132000} clusterID:0} L4Addr:{Protocol:NONE Port:31452} Scope:0} ID:123} backends:[] backendByHash:map[] svcType:NodePort svcExtTrafficPolicy:Cluster svcIntTrafficPolicy:Cluster svcNatPolicy:NONE sessionAffinity:false sessionAffinityTimeoutSec:0 svcHealthCheckNodePort:0 svcName:{Namespace: Name: Cluster:} loadBalancerSourceRanges:[] l7LBProxyPort:0 l7LBFrontendPorts:[] LoopbackHostport:false restoredFromDatapath:true restoredBackendHashes:map[]}: Unable to delete service entry 10.150.80.22:56442: unable to delete element 10.150.80.22:31452 from map cilium_lb4_services_v2: delete: key does not exist

syncing lb maps with k8s services fails