Closed patriciareinoso closed 10 months ago
Seem to be the same behavior as https://github.com/canonical/sdcore-amf-operator/issues/45
The expected behaviour is that the charm should use the internal UPF hostname whenever external hostname from MetalLB is not available. It already does that when MetalLB is enabled but without hostname; it does not handle the case in which MetalLB is not enabled at all.
Describe the bug We are getting a hook failed error when relating UPF to NMS (n4 interface) whenever all the metallb IP addresses has been assigned.
Expected behavior Charm should go to blocked status.
Logs
The
EXTERNAL-IP
for theupf-external
service stays aspending
.How to reproduce Disable metallb should be enough (?). Or make sure that all the IPs on its range has already been assigned. Deploy SD Core Deploy NMS
juju integrate sdcore-nms:sdcore-management sdcore-webui:sdcore-management
Environment Juju version: 3.1.6 Cloud Environment: MicroK8s Kubernetes version: v1.27.6