You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I keep seem messages like when running on minikube. Not sure if they are a bug because the cgroup that they are trying to enrich isn't from a container. Thought it gives the wrong message to a user, it seems like something is not working. Does it make sense to keep logging them as errors? Maybe change the severity? Anything else?
{
"level":"error",
"ts":1708089649.258455,
"msg":"error enriching container in control plane",
"error":"containers.(*Containers).EnrichCgroupInfo: cgroup 74730: no containerId (path /user.slice/user-1000.slice/user@1000.service/app.slice/snap.kubectl.kubectl-186be11b-11d3-462e-821c-83ce6d742804.scope)",
"cgroup_id":74730
}
The text was updated successfully, but these errors were encountered:
Seems to me there's a bug here, as this pattern should not match to a container but to a pod.
So the log did its work in identifying the bug. I'll add this to the milestone and likely self assign later.
I keep seem messages like when running on minikube. Not sure if they are a bug because the cgroup that they are trying to enrich isn't from a container. Thought it gives the wrong message to a user, it seems like something is not working. Does it make sense to keep logging them as errors? Maybe change the severity? Anything else?
The text was updated successfully, but these errors were encountered: