If there are multiple slices, subscribers data could not be deleted from the MongoDB.

[gatici]

Describe the bug

We have more than one slice using the same MCC, MNC, UPF and gNodeB but the names are different. Then we created a subscriber using one of the slices. When we delete the subscriber using NMS, we got the TypeError: i.imsis is null error in the console logs. The subscriber disappear from the NMS but it still exists in the MongoDB.

If we delete the slice directly through the webui using the following command, it deleted from the database properly.

curl -X DELETE ${WEBUI_IP}:5000/api/subscriber/imsi-208930100007487

To Reproduce

Follow the tutorial to install the SD-Core:https://canonical-charmed-5g.readthedocs-hosted.com/en/1.3-beta_a/tutorials/getting_started/
Access the NMS and create 2 slices and 1 subscribers.

1. Delete the subscriber using the NMS
2. Check the console logs in the browser
3. Check the webui logs and see that delete operation is not performed
4. Check the mongodb database and you will see the subscriber data still exists in the DB: authentication collection: subscriptionData.authenticationData.authenticationSubscription.
5. Delete the subsriber using a request to the webui:
   curl -X DELETE ${WEBUI_IP}:5000/api/subscriber/imsi-208930100007487
6. Check the webui logs and database again. You will see that subscriber is removed from the DB.

Expected behavior

Screenshots

Logs

Environment

• Charm / library version (if relevant):
• Juju version (output from juju --version): 3.4.0
• Cloud Environment:
• Kubernetes version (output from kubectl version --short): v1.27.11

Additional context

The test is done using 1.3/edge release of SD-Core (NMS).