-
Notifications
You must be signed in to change notification settings - Fork 40
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
Get podname and namespace "unknown" #102
Comments
Hey, I also got this unknown. How did you solve it? |
We see his behaviour here as well (on AWS) any news? |
Hey @Robert-Stam |
I have used the settings from: https://github.com/IBM/core-dump-handler/blob/main/charts/core-dump-handler/values.aws.yaml We are using Kubernetes 1.28 (on Intel hardware, m6i family) with the AMI: amazon-eks-node-1.28-v20240110 Thanks in advance! |
@No9 Hi Anton, any update on this? |
I don't have access to an AWS account to debug.
If there are no errors can you enable debugging by setting |
I tested with k8s v1.29 on AKS (Azure) and GKE (Google), and it all resolves to 'unknown' as namespace.
Hope this helps. |
crictl is already on the host on IKS and others so it isn't a useful test. |
See: #102 (comment) |
Do you have tried k8s v1.29 in the IBM cloud successfully? |
Sorry I missed your log output post for some reason.
where Are you overriding the hostname on the deployed workloads? In the meantime I'll take a look at a 1.29 cluster to confirm.
|
I am not overriding the hostname To make sure we are on the same page, you did test with {namespace} in the filenameTemplate and that is filled out correctly? |
Revalidated with this config composer:
ignoreCrio: false
crioImageCmd: "img"
logLevel: "Warn"
filenameTemplate: "{uuid}-dump-{timestamp}-{hostname}-{exe_name}-{pid}-{signal}-{namespace}" Ran The following output from the container showing the
Can I suggest getting a debug container on the host and establishing what happens when the following is ran:
Thanks |
@No9 Anton, I executed your command in the running container (ibm/core-dump-handler:v8.10.0) on AWS (with k8s v1.29).
And these are the settings applied (based on the log)
|
OK it looks like you are trying to run crictl from the handler container. What I was trying to suggest was setting up a debug session on the node.
With the node name, it doesn't matter which, run
When you have a debug session run something like the following:
Where Expected output:
|
Hi, I set the filenameTemplate: "{uuid}-dump-{timestamp}-{hostname}-{exe_name}-{pid}-{signal}-{podname}-{namespace}", but I get the filename like this: "9a1fc79c-758c-4599-a22d-2e94444a3250-dump-1657867608-segfaulter-segfaulter-1-4-unknown-unknown.zip". How to fix it?
The text was updated successfully, but these errors were encountered: