Crash Report: Expected "name" to be defined

[mpalu]

Crash Summary

Error loading Cluster
Expected "name" to be defined

Error Stack

TypeError: Expected "name" to be defined
    at file:///Applications/Headlamp.app/Contents/Resources/frontend/assets/index-D68s4_Sf.js:18:25395
    at pl (file:///Applications/Headlamp.app/Contents/Resources/frontend/assets/index-D68s4_Sf.js:25:6811)
    at as (file:///Applications/Headlamp.app/Contents/Resources/frontend/assets/index-D68s4_Sf.js:1195:35861)
    at kg.getDetailsLink (file:///Applications/Headlamp.app/Contents/Resources/frontend/assets/index-D68s4_Sf.js:888:11966)
    at knn (file:///Applications/Headlamp.app/Contents/Resources/frontend/assets/index-D68s4_Sf.js:1195:237436)
    at xd (file:///Applications/Headlamp.app/Contents/Resources/frontend/assets/vendor-mui-1viqCYs3.js:38:17652)
    at Nh (file:///Applications/Headlamp.app/Contents/Resources/frontend/assets/vendor-mui-1viqCYs3.js:40:44746)
    at Eh (file:///Applications/Headlamp.app/Contents/Resources/frontend/assets/vendor-mui-1viqCYs3.js:40:40337)
    at Ek (file:///Applications/Headlamp.app/Contents/Resources/
... (truncated)

Headlamp Version

0.39.0

Git Commit

ec014c5

System Information

• User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Headlamp/0.39.0 Chrome/126.0.6478.127 Electron/31.2.0 Safari/537.36
• Platform: MacIntel
• Language: en-US

Additional Context

This happens when I access the "Clusters" page, only for one out of the 23 clusters I have, named "arn:aws:eks:eu-west-1:XXXXXXXXXXXX:cluster--xxx-xxxxxx-xxxx"

[Sagar-6203620715]

Hi @illume,
I investigated the crash by tracing the stack trace to getDetailsLink(). Found that metadata.name was undefined for AWS EKS ARN-formatted clusters, causing generatePath() to throw. Added null check with early return to prevent the crash while logging context for debugging.

It is only about 10 lines and fixes a critical bug. Please review it. I have tested it thoroughly.

[sniok]

hi @mpalu is this still an issue for you? I'm having trouble reproducing this error

[mpalu]

hey @sniok I can confirm that the issue is solved. Thanks for your effort on this!