-
Notifications
You must be signed in to change notification settings - Fork 3.8k
cilium monitor broken on AKS 1.15 (engine 0.47) #12070
Copy link
Copy link
Closed
Labels
area/monitorImpacts monitoring, access logging, flow logging, visibility of datapath traffic.Impacts monitoring, access logging, flow logging, visibility of datapath traffic.kind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.kind/regressionThis functionality worked fine before, but was broken in a newer release of Cilium.This functionality worked fine before, but was broken in a newer release of Cilium.
Metadata
Metadata
Assignees
Labels
area/monitorImpacts monitoring, access logging, flow logging, visibility of datapath traffic.Impacts monitoring, access logging, flow logging, visibility of datapath traffic.kind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.kind/regressionThis functionality worked fine before, but was broken in a newer release of Cilium.This functionality worked fine before, but was broken in a newer release of Cilium.
While testing the AKS guide, I discovered that
cilium monitordoes not work with Cilium 1.8@f3b474ad3. As soon as I startcilium monitor(or enable Hubble), the agent crashes withfailed to create perf ring for CPU 2: can't create perf event: can't create perf event: no such device. The crash itself will be addressed in #12068, butcilium monitorremains nonfunctional:cilium monitor does not display any trace or drop events
Cilium 1.7.5 works fine on the exact same cluster.
Note: The machine does not have 128 cpus, it has 2.
aksEngineVersion: v0.47.0-aks-gomod-55-aks
kubernetes: 1.15.11
zone: westeurope
os image: Ubuntu 16.04.6 LTS
kernel:
Linux aks-ssh 4.15.0-1083-azure #93~16.04.1-Ubuntu SMP Thu May 7 18:39:44 UTC 2020 x86_64 GNU/Linux