cilium: Unable to install Cilium: timeout while waiting for status to become successful
Is there an existing issue for this?
- I have searched the existing issues
What happened?
I was trying to install cilium on Ubuntu20.04 / amd64 in procedure aligned with https://docs.cilium.io/en/stable/gettingstarted/k8s-install-default/#install-the-cilium-cli.
It eventually failed with Error: Unable to install Cilium: timeout while waiting for status to become successful: context deadline exceeded message, and never be succeeded.
Cilium Version
root@edgemaster:~# cilium version
cilium-cli: v0.12.11 compiled with go1.19.3 on linux/amd64
cilium image (default): v1.12.2
cilium image (stable): v1.12.5
cilium image (running): unknown. Unable to obtain cilium version, no cilium pods found in namespace "kube-system"
Kernel Version
root@edgemaster:~# uname -a
Linux edgemaster 5.15.0-56-generic #62~20.04.1-Ubuntu SMP Tue Nov 22 21:24:20 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
root@edgemaster:~# kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.13", GitCommit:"a43c0904d0de10f92aa3956c74489c45e6453d6e", GitTreeState:"clean", BuildDate:"2022-08-17T18:28:56Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.17", GitCommit:"a7736eaf34d823d7652415337ac0ad06db9167fc", GitTreeState:"clean", BuildDate:"2022-12-08T11:42:04Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}
Sysdump
root@edgemaster:~# cilium sysdump
🔍 Collecting sysdump with cilium-cli version: v0.12.11, args: [sysdump]
failed to create sysdump collector: failed to detect Cilium namespace, could not find Cilium installation in namespaces: [kube-system cilium]
Relevant log output
root@edgemaster:~# cilium install
ℹ️ Using Cilium version 1.12.2
🔮 Auto-detected cluster name: kubernetes
🔮 Auto-detected datapath mode: tunnel
🔮 Auto-detected kube-proxy has been installed
ℹ️ helm template --namespace kube-system cilium cilium/cilium --version 1.12.2 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan
ℹ️ Storing helm values file in kube-system/cilium-cli-helm-values Secret
🔑 Found CA in secret cilium-ca
🔑 Generating certificates for Hubble...
🚀 Creating Service accounts...
🚀 Creating Cluster roles...
🚀 Creating ConfigMap for Cilium version 1.12.2...
🚀 Creating Agent DaemonSet...
🚀 Creating Operator Deployment...
⌛ Waiting for Cilium to be installed and ready...
/¯¯\
/¯¯\__/¯¯\ Cilium: 1 errors, 1 warnings
\__/¯¯\__/ Operator: OK
/¯¯\__/¯¯\ Hubble: disabled
\__/¯¯\__/ ClusterMesh: disabled
\__/
Deployment cilium-operator Desired: 1, Ready: 1/1, Available: 1/1
DaemonSet cilium Desired: 1, Unavailable: 1/1
Containers: cilium Pending: 1
cilium-operator Running: 1
Cluster Pods: 0/2 managed by Cilium
Image versions cilium quay.io/cilium/cilium:v1.12.2@sha256:986f8b04cfdb35cf714701e58e35da0ee63da2b8a048ab596ccb49de58d5ba36: 1
cilium-operator quay.io/cilium/operator-generic:v1.12.2@sha256:00508f78dae5412161fa40ee30069c2802aef20f7bdd20e91423103ba8c0df6e: 1
Errors: cilium cilium 1 pods of DaemonSet cilium are not ready
Warnings: cilium cilium-lf6zz pod is pending
↩️ Rolling back installation...
Error: Unable to install Cilium: timeout while waiting for status to become successful: context deadline exceeded
Anything else?
No response
Code of Conduct
- I agree to follow this project’s Code of Conduct
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 21 (21 by maintainers)
@christarazi thank you so much for iterating with me.
/opt/cni/bindirectory access permission should bedrwxr-xr-x, changing it into so can resolve this issue. I am not sure what went wrong to change the permission something like that, but so far no further problems during installation. So i will go ahead to close this one.Without understanding what the underlying error msg for why Cilium pod is stuck pending, it’s very difficult to debug and propose a solution. If you can find this information out, that would be very helpful.
Can you run the installation with
--rollback=false?