search

canonical / sdcore-udm-k8s-operator

A Charmed Operator for SD-Core's Unified Data Manager (UDM) component.
https://charmhub.io/sdcore-udm-k8s
Apache License 2.0
0 stars 0 forks source link

Charmed-5G breaks after UDM pod crashes #30

Closed ghislainbourgeois closed 5 months ago

ghislainbourgeois commented 9 months ago

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']

gatici commented 9 months ago

UDR still uses old NRF IP after NRF pod restart:

nrf-0 2/2 Running 4 (6h40m ago) 29h 10.1.146.9 gaticipc

2023-11-22T14:30:21.938Z [udm] 2023-11-22T14:30:21Z [INFO][UDM][GRPC] Network Slice Name default 2023-11-22T14:30:21.938Z [udm] 2023-11-22T14:30:21Z [INFO][UDM][GRPC] Network Slice has site name present 2023-11-22T14:30:21.938Z [udm] 2023-11-22T14:30:21Z [INFO][UDM][GRPC] Site name demo 2023-11-22T14:30:21.938Z [udm] 2023-11-22T14:30:21Z [INFO][UDM][GRPC] Plmn mcc 208 2023-11-22T14:30:21.943Z [udm] 2023-11-22T14:30:21Z [INFO][Config5g][GRPC] stream msg recieved 2023-11-22T14:30:21.943Z [udm] 2023-11-22T14:30:21Z [INFO][Config5g][GRPC] First time config Received RestartCounter:1482873020 NetworkSlice:{Name:"default" Nssai:{Sst:"1" Sd:"010203"} DeviceGroup:{Name:"cows" IpDomainDetails:{Name:"pool1" DnnName:"internet" UePool:"172.250.0.0/16" DnsPrimary:"8.8.8.8" Mtu:1450 UeDnnQos:{DnnMbrUplink:2000000 DnnMbrDownlink:2000000 TrafficClass:{Name:"platinum" Qci:8 Arp:6 Pdb:300 Pelr:6}}} Imsi:"208930100007487"} Site:{SiteName:"demo" Gnb:{Name:"demo-gnb1" Tac:1} Plmn:{mcc:"208" mnc:"93"} Upf:{UpfName:"upf-external"}} AppFilters:{PccRuleBase:{FlowInfos:{FlowDesc:"permit out ip from any to assigned" TosTrafficClass:"IPV4" FlowDir:BIDIRECTIONAL} RuleId:"DefaultRule" Qos:{Var5qi:9 Arp:{PL:1 PC:MAY_PREEMPT PV:PREEMPTABLE}} Priority:255}}} ConfigUpdated:1 2023-11-22T14:30:29.619Z [udm] UDM register to NRF Error[Put "https://10.1.146.25:29510/nnrf-nfm/v1/nf-instances/ae049626-b4b1-4b13-a2e8-5b744ed68c16": dial tcp 10.1.146.25:29510: connect: connection timed out] 2023-11-22T14:30:29.619Z [udm] UDM register to NRF Error[Put "https://10.1.146.25:29510/nnrf-nfm/v1/nf-instances/ae049626-b4b1-4b13-a2e8-5b744ed68c16": dial tcp 10.1.146.25:29510: connect: connection timed out] 2023-11-22T14:32:42.739Z [udm] UDM register to NRF Error[Put "https://10.1.146.25:29510/nnrf-nfm/v1/nf-instances/ae049626-b4b1-4b13-a2e8-5b744ed68c16": dial tcp 10.1.146.25:29510: connect: connection timed out] 2023-11-22T14:32:42.739Z [udm] UDM register to NRF Error[Put "https://10.1.146.25:29510/nnrf-nfm/v1/nf-instances/ae049626-b4b1-4b13-a2e8-5b744ed68c16": dial tcp 10.1.146.25:29510: connect: connection timed out] 2023-11-22T14:34:55.859Z [udm] UDM register to NRF Error[Put "https://10.1.146.25:29510/nnrf-nfm/v1/nf-instances/ae049626-b4b1-4b13-a2e8-5b744ed68c16": dial tcp 10.1.146.25:29510: connect: connection timed out] 2023-11-22T14:34:55.859Z [udm] UDM register to NRF Error[Put "https://10.1.146.25:29510/nnrf-nfm/v1/nf-instances/ae049626-b4b1-4b13-a2e8-5b744ed68c16": dial tcp 10.1.146.25:29510: connect: connection timed out] 2023-11-22T14:37:08.983Z [udm] UDM register to NRF Error[Put "https://10.1.146.25:29510/nnrf-nfm/v1/nf-instances/ae049626-b4b1-4b13-a2e8-5b744ed68c16": dial tcp 10.1.146.25:29510: connect: connection timed out] 2023-11-22T14:37:08.983Z [udm] UDM register to NRF Error[Put "https://10.1.146.25:29510/nnrf-nfm/v1/nf-instances/ae049626-b4b1-4b13-a2e8-5b744ed68c16": dial tcp 10.1.146.25:29510: connect: connection timed out]

gruyaume commented 6 months ago

@ghislainbourgeois is this issue still valid?

ghislainbourgeois commented 5 months ago

I think it was fixed upstream. I will close it.