[Bug 1139800] New: Cillium not working in Kubic
http://bugzilla.suse.com/show_bug.cgi?id=1139800 Bug ID: 1139800 Summary: Cillium not working in Kubic 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: jason.evans@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I am testing this on the latest Snapshot20190627. Init worked well:
master:~ # kubicctl init --pod-network cilium Initializing kubernetes master can take several minutes, please be patient. Initialize Kubernetes control-plane Deploy cilium Deploy Kubernetes Reboot Daemon (kured) Kubernetes master was succesfully setup.
cilium-etcd-operator pod is still not coming up:
master:~ # kubectl get pods -n kube-system NAME READY STATUS RESTARTS AGE cilium-5fdrl 0/1 PodInitializing 0 73s cilium-etcd-operator-5f9468cf8c-6b5bn 0/1 ImagePullBackOff 0 73s cilium-operator-cb87f5c57-d8qwz 0/1 Pending 0 73s coredns-fb8b8dccf-c7f8n 0/1 Pending 0 73s coredns-fb8b8dccf-wl5rg 0/1 Pending 0 73s etcd-master 1/1 Running 0 30s kube-apiserver-master 1/1 Running 0 40s kube-controller-manager-master 1/1 Running 0 37s kube-proxy-jgttd 1/1 Running 0 73s kube-scheduler-master 1/1 Running 0 37s
Can not pull the image from registry.opensuse.org/kubic/cilium-etcd-operator:2.0
Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 4m28s default-scheduler Successfully assigned kube-system/cilium-etcd-operator-5f9468cf8c-6b5bn to master Normal Pulling 103s (x4 over 4m25s) kubelet, master Pulling image "registry.opensuse.org/kubic/cilium-etcd-operator:2.0" Warning Failed 103s (x4 over 4m11s) kubelet, master Failed to pull image "registry.opensuse.org/kubic/cilium-etcd-operator:2.0": rpc error: code = Unknown desc = Error reading manifest 2.0 in registry.opensuse.org/kubic/cilium-etcd-operator: name unknown Warning Failed 103s (x4 over 4m11s) kubelet, master Error: ErrImagePull Normal BackOff 89s (x6 over 4m10s) kubelet, master Back-off pulling image "registry.opensuse.org/kubic/cilium-etcd-operator:2.0" Warning Failed 78s (x7 over 4m10s) kubelet, master Error: ImagePullBackOff
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139800 Jason Evans <jason.evans@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason.evans@suse.com Found By|--- |Community User -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139800 http://bugzilla.suse.com/show_bug.cgi?id=1139800#c2 Thorsten Kukuk <kukuk@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kubic-bugs@opensuse.org |mrostecki@suse.com --- Comment #2 from Thorsten Kukuk <kukuk@suse.com> --- I submitted the missing container image to Factory now, I hope that's all what's missing. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139800 http://bugzilla.suse.com/show_bug.cgi?id=1139800#c3 --- Comment #3 from Michał Rostecki <mrostecki@suse.com> --- (In reply to Andreas Färber from comment #1)
Same problem on aarch64 with snapshot 20190607.
That's because there are no Cilium packages or images for aarch64. I still need to fix build of few dependencies. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139800 http://bugzilla.suse.com/show_bug.cgi?id=1139800#c6 --- Comment #6 from Jason Evans <jason.evans@suse.com> --- re: Thorsten I don't know how long it takes for a container image in factory to be available in the container registry, but so far we are having the same issue. This is from the latest build: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 113s default-scheduler Successfully assigned kube-system/cilium-etcd-operator-5585fb77d4-9dztf to master Normal Pulling 31s (x3 over 112s) kubelet, master Pulling image "registry.opensuse.org/kubic/cilium-etcd-operator:2.0" Warning Failed 30s (x3 over 111s) kubelet, master Failed to pull image "registry.opensuse.org/kubic/cilium-etcd-operator:2.0": rpc error: code = Unknown desc = Error reading manifest 2.0 in registry.opensuse.org/kubic/cilium-etcd-operator: name unknown Warning Failed 30s (x3 over 111s) kubelet, master Error: ErrImagePull Normal BackOff 7s (x4 over 110s) kubelet, master Back-off pulling image "registry.opensuse.org/kubic/cilium-etcd-operator:2.0" Warning Failed 7s (x4 over 110s) kubelet, master Error: ImagePullBackOff -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139800 http://bugzilla.suse.com/show_bug.cgi?id=1139800#c7 --- Comment #7 from Guillaume GARDET <guillaume.gardet@arm.com> --- cilium-proxy fails to build for all archs: https://build.opensuse.org/package/show/devel:kubic/cilium-proxy I tried older bazel, without success. The maintainer can probably have a look. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139800 http://bugzilla.suse.com/show_bug.cgi?id=1139800#c8 --- Comment #8 from Michał Rostecki <mrostecki@suse.com> --- (In reply to Guillaume GARDET from comment #7)
cilium-proxy fails to build for all archs: https://build.opensuse.org/package/show/devel:kubic/cilium-proxy
I tried older bazel, without success. The maintainer can probably have a look.
I will try to fix it by updating Envoy to the newest version. Which depends on Bazel 0.25 though. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139800 http://bugzilla.suse.com/show_bug.cgi?id=1139800#c9 --- Comment #9 from Thorsten Kukuk <kukuk@suse.com> --- (In reply to Jason Evans from comment #6)
re: Thorsten I don't know how long it takes for a container image in factory to be available in the container registry, but so far we are having the same issue. This is from the latest build:
You can check the registry yourself, enter "^kubic" in the search field, and all official released images for Kubic are shown. How long it takes with openSUSE to get an image released depends on in which staging project the image ends, some are fast, some other are really slow if there are problems with other packages. But it should work now, all images are now released. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139800 http://bugzilla.suse.com/show_bug.cgi?id=1139800#c10 --- Comment #10 from Jason Evans <jason.evans@suse.com> --- While the image is now available, Cillium is still not working. The main cillium pod "cillium-xxxxx" is in a repeating CrashLoopBackOff Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 4m3s default-scheduler Successfully assigned kube-system/kured-2klhw to worker10 Warning FailedCreatePodSandBox 2m31s kubelet, worker10 Failed create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_kured-2klhw_kube-system_e65460cd-c824-40e2-872f-2b9a6e69ec42_0(fca46fe4ffc72e146befc14d19c036a1beed6fb8918f5e0dbaaed33319cd58c7): Unable to create endpoint: Put http:///var/run/cilium/cilium.sock/v1/endpoint/cilium-local:0: context deadline exceeded Warning FailedCreatePodSandBox 55s kubelet, worker10 Failed create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_kured-2klhw_kube-system_e65460cd-c824-40e2-872f-2b9a6e69ec42_0(9745ea80f03bb52293b43733b87eade1e94f762e7aac75dbc34010033cd5c926): Unable to create endpoint: Put http:///var/run/cilium/cilium.sock/v1/endpoint/cilium-local:0: EOF Also the kured-xxxxx pod are stuck in a "ContainerCreating" mode. Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 5m8s default-scheduler Successfully assigned kube-system/kured-2klhw to worker10 Warning FailedCreatePodSandBox 3m36s kubelet, worker10 Failed create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_kured-2klhw_kube-system_e65460cd-c824-40e2-872f-2b9a6e69ec42_0(fca46fe4ffc72e146befc14d19c036a1beed6fb8918f5e0dbaaed33319cd58c7): Unable to create endpoint: Put http:///var/run/cilium/cilium.sock/v1/endpoint/cilium-local:0: context deadline exceeded Warning FailedCreatePodSandBox 2m kubelet, worker10 Failed create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_kured-2klhw_kube-system_e65460cd-c824-40e2-872f-2b9a6e69ec42_0(9745ea80f03bb52293b43733b87eade1e94f762e7aac75dbc34010033cd5c926): Unable to create endpoint: Put http:///var/run/cilium/cilium.sock/v1/endpoint/cilium-local:0: EOF Warning FailedCreatePodSandBox 14s kubelet, worker10 Failed create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_kured-2klhw_kube-system_e65460cd-c824-40e2-872f-2b9a6e69ec42_0(7f86af61f02880035e8d3915ded95cda717306724ad1a31d70c75387d6f01e21): Unable to create endpoint: Put http:///var/run/cilium/cilium.sock/v1/endpoint/cilium-local:0: context deadline exceeded -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1139800 http://bugzilla.suse.com/show_bug.cgi?id=1139800#c11 --- Comment #11 from Guillaume GARDET <guillaume.gardet@arm.com> --- @Jason, cilium-proxy is still failing for all archs: https://build.opensuse.org/package/show/devel:kubic/cilium-proxy So, we probably need to get it build properly? And kubic-cilium-image is still unresolvable for aarch64: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/kubic-cilium-im... -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com