Symptoms:
Upon manual restart of the VMS (via vcenter) Pod Rollout became stuck in the ContainerCreating status.
Possibility 1: kubectl describe <pod_name>
Error will look like this:
Warning FailedCreatePodSandBox 1m (x12 over 1m) kubelet, ########-########-##########-######## Failed create pod sandbox: rpc error: code = Unknown desc = NetworkPlugin cni failed to set up pod "nginx-c58f88dd6-hqszg_default" network: "cni0" already has an IP address different from 10.200.##.#/24
Possibility 2: When I run ifconfig on a worker node I can see that flannel and cni are on different subnets
worker/xxxx:/var/lib/cni/networks# ifconfig cni0 Link encap:Ethernet HWaddr 4e:d5:14:c4:c8:f3 inet addr:10.200.##.# Bcast:10.200.##.### Mask:255.255.255.0 flannel.1 Link encap:Ethernet HWaddr 2e:e3:38:5b:d5:69 inet addr:10.200.##.# Bcast:0.0.0.0 Mask:255.255.255.255
Currently this issue is not fixed in TKGI 1.9. This is fixed in TKGI 1.9.3.
Here are the workaround steps:
Note: Only to be used if resolution 1 does not work.