-
-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Stuck at "waiting for the condition on deployments/system-upgrade-controller" (cilium pod stuck) #1147
Comments
I am able to successfully run Yesterday this still worked for me. Last night's auto update resulted in this issue. (re-)creating nodes did not fix this. |
I managed to fix my cilium issues by tricking kube-hetnzer into reinstalling the Cilium CRDs (that is where the cilium pods were stuck at). In my case, I toggled the cilium egress gateway. Not sure this is feasible solution for you, as your |
Ok, it's selinux. Working on a fix now. sudo ausearch -m AVC
----
time->Fri Jan 5 23:03:02 2024
type=AVC msg=audit(1704495782.399:1158): avc: denied { map_create } for pid=3952 comm="cilium-operator" scontext=system_u:system_r:container_t:s0:c629,c815 tcontext=system_u:system_r:container_t:s0:c629,c815 tclass=bpf permissive=0
----
time->Fri Jan 5 23:03:06 2024
type=AVC msg=audit(1704495786.659:1167): avc: denied { map_create } for pid=4047 comm="cilium" scontext=system_u:system_r:container_t:s0:c709,c825 tcontext=system_u:system_r:container_t:s0:c709,c825 tclass=bpf permissive=0 |
@byRoadrunner @bverhagen This was fixed in v2.11.5, but also using the kube.tf setup above, the control plane need to be at least cx21 as cpx11 with 2GB was not enough to allocate bpf memory for cilium, only +500MB was free and it was not enough, when you upgrade the node it works well, and this was only needed for the control-plane. Maybe with less options (like no smb etc). This was on top of the selinux issue. |
@mysticaltech : Thx! I use cax11 nodes for the control plane, so I can certainly live with that limitation! |
Description
When creating a completely new cluster with version 2.11.3 the cluster installation keeps failing at:
I sshed to cp1 and checked the status of the pods in kube-system namespace
So it seems like cilium is not starting correctly.
These are the only error/warning things i find in the logs.
System upgrade controller had the following events in kubectl describe:
If needed I can provide more logs of specific pods. I just wanted to ask first whether and if so which additional logs are required, because I first need to go through and remove private information.
Thanks in advance. If you need any more information feel free to ask.
Kube.tf file
Screenshots
No response
Platform
macOS 14.2.1
The text was updated successfully, but these errors were encountered: