UPF locked in ContainerCreating Status

[Duaran]

Hello everyone,

I tried to deploy the free5gc network with the help of your documentation and this tutorial :

https://medium.com/rahasak/deploying-5g-core-network-with-free5gc-kubernets-and-helm-charts-29741cea3922

However during the deploying phase the UPF pod stay at the ContainerCreating status like below :

It seems to be due to this error :

I read other closed issues which could be compared to this kind of error. That's why I run ip a on other components of free5gc like the smf, amf and udr. (with the result below)

Does this error happen from the fact that I have only eth0 as network interface and creating a 2nd interface eth1 is needed? Or it is because "Nx" interface aren't renamed eth1 ? (Or maybe something else)

Thank you and have a nice day !

[raoufkh]

Hello

It seems that Multus cannot provide the network N6 to the UPF. I recall that by default, the N6 interface is bound to the interface eth1 on the host. So, is this interface available on your host? If not please see Networks configuration

[ritokispingvin]

Hi @raoufkh, I'm experiencing exactly the same issue with the UPF pod while having 2 NAT interfaces (enp0s3 and enp0s8) + 1 Host only interface (enp0s9) set up in VirtualBox. They are not named eth0 and eth1 most of the pods are up so I don't think naming is an issue. I'm following this tutorial https://medium.com/rahasak/deploying-5g-core-network-with-free5gc-kubernets-and-helm-charts-29741cea3922 so I'm using Minikube right now but I've tried with kubeadm and ran into same issue.

Can you please help us how you are created the eth0 and eth1 interfaces? My /etc/netplan/00-installer-config.yaml file looks like this. Can you show us yours please?

Thank you and best regards, Tamas

[raoufkh]

Hello @ritokispingvin

Network interfaces name is important to consider when you configure the free5gc helm charts. You should seee this section. with the defaul values of the chart and no eth0 and eth1 present on your worker nodes, AMF and SMF should not be created. Can you show the kubectl describe pod command for AMF and SMF pods please?

[ritokispingvin]

Hi @raoufkh ,

kubectl describe pod for AMF:

kubectl describe pod for SMF:

I found out that I was using eth0 as NAT network and eth1 as host-only network while I think eth1 should have been the NAT network. So I changed it, but issue still there :( My current network config:

Error for UPF pod is still exactly same. I've tried minikube, kubeadm with flannel, calio but all has this same issue:

Do I need to modify some IP in the free5gc charts to match my NAT network IP?

Many Thanks and BRs, Tamas

[ritokispingvin]

Hi, I don't know what happened but when I deployed kubeadm again and again it started working. It is still really strange and I can not explain why I had this issue with UPF, the only difference is that I make everything slower and waited all pods to be ready before going to next steps. BRs, Tamas

[raoufkh]

Hi @ritokispingvin

Good news

Maybe because UPF N6 configuration was wrong, because the descritpion of UPF pod says that the CNI cannot attach the pod to n6network

Bests Raouf