Get podname and namespace "unknown"

[wsszh]

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?

[joaogbcravo]

Hey, I also got this unknown. How did you solve it?

[Robert-Stam]

We see his behaviour here as well (on AWS) any news?
I see the issue is set the closed, however it doesn't seems to be resolved?

[No9]

Hey @Robert-Stam
Can you confirm which aws.values.xxx.yaml you have used in the deployment and which version of EKS you are using.
It's likely that the version of crio is now outdated as this hasn't been updated for a while.

[Robert-Stam]

Hey @Robert-Stam Can you confirm which aws.values.xxx.yaml you have used in the deployment and which version of EKS you are using. It's likely that the version of crio is now outdated as this hasn't been updated for a while.

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
See: https://github.com/awslabs/amazon-eks-ami/releases/tag/v20240110

Thanks in advance!

[Robert-Stam]

@No9 Hi Anton, any update on this?

[No9]

I don't have access to an AWS account to debug.
Can you log into an agent container that has processed a core dump and provide the output of

cat /var/mnt/core-dump-handler/composer.log

If there are no errors can you enable debugging by setting
https://github.com/IBM/core-dump-handler/blob/main/charts/core-dump-handler/values.yaml#L27
to Debug

[Robert-Stam]

I tested with k8s v1.29 on AKS (Azure) and GKE (Google), and it all resolves to 'unknown' as namespace.
This is the output from the composer log on AKS

ERROR - 2024-04-05T09:41:43.149688332+00:00 - failed to create pod at index 0
ERROR - 2024-04-05T09:41:47.803435709+00:00 - Failed to get pod id

Hope this helps.

[Robert-Stam]

@No9 I tried to create a small PR to update the packages and crictr version, however without luck.
FYI, here is my PR: #158

Do you have tried k8s v1.29 in the IBM cloud successfully?

[No9]

crictl is already on the host on IKS and others so it isn't a useful test.
Did you look for the compose logs as per this comment?
#102 (comment)

[Robert-Stam]

crictl is already on the host on IKS and others so it isn't a useful test.

Did you look for the compose logs as per this comment?

#102 (comment)

See: #102 (comment)