[BUG] Wrong IP allocation make pods to crash

[oglok]

What happened:

Following instructions on microshift.io for containerized deployment (not AIO) on Podman, some of the pods like service-ca and kubevirt hostpath provisioner get wrong IP addresses:

[vagrant@fedora ~]$ oc get pod -A -o wide                                                                                                                                                                      
NAMESPACE                       NAME                                   READY   STATUS             RESTARTS   AGE     IP                NODE     NOMINATED NODE   READINESS GATES                               
default                         edge-app-deployment-7bfb5d9cc7-5qk4q   1/1     Running            0          69s     10.42.0.4         fedora   <none>           <none>                                        
default                         edge-app-deployment-7bfb5d9cc7-ljxvq   1/1     Running            0          69s     10.42.0.3         fedora   <none>           <none>                                        
kube-system                     kube-flannel-ds-x7sfk                  1/1     Running            0          3m39s   192.168.122.154   fedora   <none>           <none>                                        
kubevirt-hostpath-provisioner   kubevirt-hostpath-provisioner-qcc4k    1/1     Running            0          3m28s   10.85.0.2         fedora   <none>           <none>                                        
openshift-dns                   dns-default-7swq4                      2/2     Running            0          3m38s   10.42.0.2         fedora   <none>           <none>                                        
openshift-dns                   node-resolver-xsg2n                    1/1     Running            0          3m39s   192.168.122.154   fedora   <none>           <none>                                        
openshift-ingress               router-default-6c96f6bc66-nfvp8        1/1     Running            0          3m42s   192.168.122.154   fedora   <none>           <none>                                        
openshift-service-ca            service-ca-7bffb6f6bf-mml2f            0/1     CrashLoopBackOff   2          3m44s   10.85.0.3         fedora   <none>           <none>   

What you expected to happen:

All pods that are not using the host network, must get IPs from the pod network indicated by flannel CNI:

[vagrant@fedora ~]$ oc get pod -A -o wide 
NAMESPACE                       NAME                                   READY   STATUS    RESTARTS   AGE   IP                NODE     NOMINATED NODE   READINESS GATES
default                         edge-app-deployment-7bfb5d9cc7-5qk4q   1/1     Running   0          29m   10.42.0.4         fedora   <none>           <none>
default                         edge-app-deployment-7bfb5d9cc7-ljxvq   1/1     Running   0          29m   10.42.0.3         fedora   <none>           <none>
kube-system                     kube-flannel-ds-x7sfk                  1/1     Running   0          31m   192.168.122.154   fedora   <none>           <none>
kubevirt-hostpath-provisioner   kubevirt-hostpath-provisioner-wlcqh    1/1     Running   0          21m   10.42.0.6         fedora   <none>           <none>
openshift-dns                   dns-default-7swq4                      2/2     Running   0          31m   10.42.0.2         fedora   <none>           <none>
openshift-dns                   node-resolver-xsg2n                    1/1     Running   0          31m   192.168.122.154   fedora   <none>           <none>
openshift-ingress               router-default-6c96f6bc66-nfvp8        1/1     Running   0          31m   192.168.122.154   fedora   <none>           <none>
openshift-service-ca            service-ca-7bffb6f6bf-lcq5c            1/1     Running   0          27m   10.42.0.5         fedora   <none>           <none>

How to reproduce it (as minimally and precisely as possible):

1. Follow instructions in microshift.io for Podman deployments.

Anything else we need to know?:

This is a test on a Fedora Vagrant VM.

Environment:

• Microshift version (use microshift version):
  [vagrant@fedora ~]$ sudo podman exec -it microshift microshift version
  MicroShift Version: 4.8.0-0.microshift-2022-02-04-005920
  Base OKD Version: 4.8.0-0.okd-2021-10-10-030117

• Hardware configuration:

• OS (e.g: cat /etc/os-release):
  NAME=Fedora
  VERSION="34 (Cloud Edition)"
  ID=fedora
  VERSION_ID=34
  VERSION_CODENAME=""
  PLATFORM_ID="platform:f34"
  PRETTY_NAME="Fedora 34 (Cloud Edition)"
  ANSI_COLOR="0;38;2;60;110;180"
  LOGO=fedora-logo-icon
  CPE_NAME="cpe:/o:fedoraproject:fedora:34"
  HOME_URL="https://fedoraproject.org/"
  DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/34/system-administrators-guide/"
  SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
  BUG_REPORT_URL="https://bugzilla.redhat.com/"
  REDHAT_BUGZILLA_PRODUCT="Fedora"
  REDHAT_BUGZILLA_PRODUCT_VERSION=34
  REDHAT_SUPPORT_PRODUCT="Fedora"
  REDHAT_SUPPORT_PRODUCT_VERSION=34
  PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
  VARIANT="Cloud Edition"
  VARIANT_ID=cloud

• Kernel (e.g. uname -a):
  Linux fedora 5.11.12-300.fc34.x86_64 Init #1 SMP Wed Apr 7 16:31:13 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

• Others:

Relevant Logs

[oglok]

The following file is not included in the containerized environment:

https://github.com/redhat-et/microshift/blob/main/packaging/crio.conf.d/microshift.conf