Activity log for bug #1811819

Date Who What changed Old value New value Message
2019-01-15 12:45:47 Oz Tiram bug added bug
2019-01-15 12:46:20 Oz Tiram description The kernel built with this packages does have VXLAN compiled. It would be nice if this could be fixed since VXLAN is used Flannel and maybe other CNI plugins for Kubernetes. $ grep -i vxlan /boot/config-4.4.0-1039-kvm # CONFIG_VXLAN is not set The kernel built with this packages does have VXLAN compiled. It would be nice if this could be fixed since VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes. $ grep -i vxlan /boot/config-4.4.0-1039-kvm # CONFIG_VXLAN is not set
2019-01-16 11:36:36 Oz Tiram description The kernel built with this packages does have VXLAN compiled. It would be nice if this could be fixed since VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes. $ grep -i vxlan /boot/config-4.4.0-1039-kvm # CONFIG_VXLAN is not set The kernel built with this packages does have VXLAN compiled. It would be nice if this could be fixed since VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes. $ grep -i vxlan /boot/config-4.4.0-1039-kvm # CONFIG_VXLAN is not set When running a kubernetes cluster with Flannel with this image: $ kubectl logs kube-flannel-ds-amd64-jfkc8 -n kube-system --kubeconfig=case1-admin.conf I0116 11:35:34.176962 1 main.go:475] Determining IP address of default interface I0116 11:35:34.177231 1 main.go:488] Using interface with name ens3 and address 10.32.192.14 I0116 11:35:34.177259 1 main.go:505] Defaulting external address to interface address (10.32.192.14) I0116 11:35:34.191358 1 kube.go:131] Waiting 10m0s for node controller to sync I0116 11:35:34.273844 1 kube.go:294] Starting kube subnet manager I0116 11:35:35.274075 1 kube.go:138] Node controller sync successful I0116 11:35:35.274106 1 main.go:235] Created subnet manager: Kubernetes Subnet Manager - node-1-case1 I0116 11:35:35.274113 1 main.go:238] Installing signal handlers I0116 11:35:35.274233 1 main.go:353] Found network config - Backend type: vxlan I0116 11:35:35.274292 1 vxlan.go:120] VXLAN config: VNI=1 Port=0 GBP=false DirectRouting=false E0116 11:35:35.275803 1 main.go:280] Error registering network: operation not supported I0116 11:35:35.275860 1 main.go:333] Stopping shutdownHandler...
2019-07-01 03:49:01 Po-Hsu Lin linux-kvm (Ubuntu): status New Incomplete
2019-07-01 03:49:07 Po-Hsu Lin bug added subscriber Po-Hsu Lin
2019-08-06 02:37:44 Po-Hsu Lin nominated for series Ubuntu Xenial
2019-08-06 02:37:44 Po-Hsu Lin bug task added linux-kvm (Ubuntu Xenial)
2019-08-15 01:02:21 Jeffrey Forman bug added subscriber Jeffrey Forman
2019-08-15 11:20:30 Po-Hsu Lin nominated for series Ubuntu Bionic
2019-08-15 11:20:30 Po-Hsu Lin bug task added linux-kvm (Ubuntu Bionic)
2019-08-15 11:20:43 Po-Hsu Lin linux-kvm (Ubuntu Xenial): assignee Po-Hsu Lin (cypressyew)
2019-08-16 10:04:49 Po-Hsu Lin nominated for series Ubuntu Disco
2019-08-16 10:04:49 Po-Hsu Lin bug task added linux-kvm (Ubuntu Disco)
2019-08-19 06:14:14 Po-Hsu Lin description The kernel built with this packages does have VXLAN compiled. It would be nice if this could be fixed since VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes. $ grep -i vxlan /boot/config-4.4.0-1039-kvm # CONFIG_VXLAN is not set When running a kubernetes cluster with Flannel with this image: $ kubectl logs kube-flannel-ds-amd64-jfkc8 -n kube-system --kubeconfig=case1-admin.conf I0116 11:35:34.176962 1 main.go:475] Determining IP address of default interface I0116 11:35:34.177231 1 main.go:488] Using interface with name ens3 and address 10.32.192.14 I0116 11:35:34.177259 1 main.go:505] Defaulting external address to interface address (10.32.192.14) I0116 11:35:34.191358 1 kube.go:131] Waiting 10m0s for node controller to sync I0116 11:35:34.273844 1 kube.go:294] Starting kube subnet manager I0116 11:35:35.274075 1 kube.go:138] Node controller sync successful I0116 11:35:35.274106 1 main.go:235] Created subnet manager: Kubernetes Subnet Manager - node-1-case1 I0116 11:35:35.274113 1 main.go:238] Installing signal handlers I0116 11:35:35.274233 1 main.go:353] Found network config - Backend type: vxlan I0116 11:35:35.274292 1 vxlan.go:120] VXLAN config: VNI=1 Port=0 GBP=false DirectRouting=false E0116 11:35:35.275803 1 main.go:280] Error registering network: operation not supported I0116 11:35:35.275860 1 main.go:333] Stopping shutdownHandler... == SRU Justification == VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes, it will be great to enable the support in KVM kernels. == Fix == Enable the CONFIG_VXLAN in the config file. CONFIG_NET_UDP_TUNNEL=m and other configs were added automatically with updateconfigs. CONFIG_OPENVSWITCH_VXLAN supprt was excluded intentionally as this is not requested (and to reduce the binary size). == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1811819-vxlan/ Kernel smoke tested. User has also verified that all the patched kernels are working as expected. == Regression Potentail == Low, this enables the support for VXLAN module on KVM kernels, we might see some related bugs in the future. Since we already have this in the generic kernel so the impact should be small. == Original Bug Report == The kernel built with this packages does have VXLAN compiled. It would be nice if this could be fixed since VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes. $ grep -i vxlan /boot/config-4.4.0-1039-kvm # CONFIG_VXLAN is not set When running a kubernetes cluster with Flannel with this image: $ kubectl logs kube-flannel-ds-amd64-jfkc8 -n kube-system --kubeconfig=case1-admin.conf I0116 11:35:34.176962 1 main.go:475] Determining IP address of default interface I0116 11:35:34.177231 1 main.go:488] Using interface with name ens3 and address 10.32.192.14 I0116 11:35:34.177259 1 main.go:505] Defaulting external address to interface address (10.32.192.14) I0116 11:35:34.191358 1 kube.go:131] Waiting 10m0s for node controller to sync I0116 11:35:34.273844 1 kube.go:294] Starting kube subnet manager I0116 11:35:35.274075 1 kube.go:138] Node controller sync successful I0116 11:35:35.274106 1 main.go:235] Created subnet manager: Kubernetes Subnet Manager - node-1-case1 I0116 11:35:35.274113 1 main.go:238] Installing signal handlers I0116 11:35:35.274233 1 main.go:353] Found network config - Backend type: vxlan I0116 11:35:35.274292 1 vxlan.go:120] VXLAN config: VNI=1 Port=0 GBP=false DirectRouting=false E0116 11:35:35.275803 1 main.go:280] Error registering network: operation not supported I0116 11:35:35.275860 1 main.go:333] Stopping shutdownHandler...
2019-08-19 06:17:30 Po-Hsu Lin linux-kvm (Ubuntu Bionic): assignee Po-Hsu Lin (cypressyew)
2019-08-19 06:17:31 Po-Hsu Lin linux-kvm (Ubuntu Disco): assignee Po-Hsu Lin (cypressyew)
2019-08-19 06:17:34 Po-Hsu Lin linux-kvm (Ubuntu Xenial): status New In Progress
2019-08-19 06:17:35 Po-Hsu Lin linux-kvm (Ubuntu Bionic): status New In Progress
2019-08-19 06:17:37 Po-Hsu Lin linux-kvm (Ubuntu Disco): status New In Progress
2019-08-19 06:17:47 Po-Hsu Lin linux-kvm (Ubuntu): status Incomplete In Progress
2019-09-03 14:50:20 Kleber Sacilotto de Souza linux-kvm (Ubuntu Xenial): status In Progress Fix Committed
2019-09-03 14:55:40 Kleber Sacilotto de Souza linux-kvm (Ubuntu Bionic): status In Progress Fix Committed
2019-09-03 14:57:27 Kleber Sacilotto de Souza linux-kvm (Ubuntu Disco): status In Progress Fix Committed
2019-09-30 22:04:32 Launchpad Janitor linux-kvm (Ubuntu Bionic): status Fix Committed Fix Released
2019-09-30 22:04:32 Launchpad Janitor cve linked 2018-20976
2019-10-04 09:56:34 Launchpad Janitor linux-kvm (Ubuntu Disco): status Fix Committed Fix Released
2019-10-14 12:39:44 Launchpad Janitor linux-kvm (Ubuntu): status In Progress Fix Released
2019-10-14 12:39:44 Launchpad Janitor cve linked 2019-15098
2019-10-14 12:39:44 Launchpad Janitor cve linked 2019-17052
2019-10-14 12:39:44 Launchpad Janitor cve linked 2019-17053
2019-10-14 12:39:44 Launchpad Janitor cve linked 2019-17054
2019-10-14 12:39:44 Launchpad Janitor cve linked 2019-17055
2019-10-14 12:39:44 Launchpad Janitor cve linked 2019-17056