Bug ID | 1122024 |
---|---|
Summary | [Build20190112] Podman containers have no network after CNI configured for kubeadm cluster |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Kubic |
Assignee | kubic-bugs@opensuse.org |
Reporter | rbrown@suse.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
https://openqa.opensuse.org/tests/831669#step/podman/24 After installing kubeadm and setting up flannel CNI using the https://en.opensuse.org/Kubic:kubeadm approach, podman containers should inherit that CNI config and use it with a CNI network Instead, there seems to be some form of incompatibility between the kubeadm flannel CNI and Podmans expectations Error message from a "podman container run hello-world" error parsing CNI plugin result "IP4:{IP:{IP:10.244.0.3 Mask:ffffff00} Gateway:10.244.0.1 Routes:[{Dst:{IP:10.244.0.0 Mask:ffff0000} GW:10.244.0.1} {Dst:{IP:0.0.0.0 Mask:00000000} GW:10.244.0.1}]}, DNS:{Nameservers:[] Domain: Search:[] Options:[]}": cannot convert version ["" "0.1.0" "0.2.0"] to 0.4.0: cannot convert version ["" "0.1.0" "0.2.0"] to 0.4.0 Suspicion is that podman requires a CNI config of version 0.4.0 but flannel is providing a version 0.1.0/0.2.0