canonical / sdcore-udm-k8s-operator Goto Github PK

Describe the bug

When deploying the UDM, it can get stuck in a waiting state with the message Waiting for home network private key to be available. The issue appears to be in the on_install hook where the keys are generated. If the container is not yet ready for connection, the key will never be generated.

To Reproduce

As this is a race condition on initial deployment, the only way to reproduce is to redeploy until the issue appears.

Expected behavior

The UDM charm should recover once the container is ready and generate the private key.

Screenshots

Logs

Environment

• Charm / library version (if relevant): 1.3/edge revision 53
• Juju version (output from juju --version): 3.4.0
• Cloud Environment: microk8s

Additional context

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update dependency pytest-asyncio to v0.23.5

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Describe the bug

Charmed-5G simulation fails after the UDM pod crashes and restarts.

To Reproduce

1. Deploy Charmed-5G, configure and run a successful simulation
   

2. Delete the pod 'udm-0' and wait for it to come back to Active/Idle
   

3. Run failing simulation
   

Expected behavior

Simulation works

Logs

ERROR test_integration:test_integration.py:84 Failed after deleting udm-0
ERROR test_integration:test_integration.py:85 Successes:
['ausf-0', 'amf-0', 'pcf-0', 'amf-0', 'amf-0']