Closed Hexta closed 1 month ago
With debug logs
2024-07-04T09:50:00.389888655Z DBG No mapping found for aggregate: service
2024-07-04T09:50:00.433023521Z DBG added metric unclaimedVolumes%%High-Availability
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x29bdfe0]
goroutine 177361 [running]:
github.com/kubecost/kubecost-cost-model/pkg/duckdb/asset/db.(*AssetDBQueryService).QueryAssetCTE(0x4000c4af00?, {0x401c2d2108?, 0x401c2d2120?}, {0x401d02c180?, 0x2?, 0x2?}, 0x40159eb600?, {0x692be28?, 0x4033c28240?})
/app/kubecost-cost-model/pkg/duckdb/asset/db/assetquery.go:846 +0xb0
github.com/kubecost/kubecost-cost-model/pkg/duckdb/asset/db.(*AssetDBQueryService).QueryAsset(0x4000c4af00, {0x401c2d2108?, 0x401c2d2120?}, {0x401d02c180, 0x2, 0x2}, 0x40159eb600, {0x692be28, 0x4033c281b0})
/app/kubecost-cost-model/pkg/duckdb/asset/db/assetquery.go:111 +0x414
github.com/kubecost/kubecost-cost-model/pkg/duckdb/asset.(*DuckDBAssetQueryService).QueryAsset.func1(0x1, {0x402286e0c0, 0x18, 0x692be60?}, {0x401c2d2108?, 0x401c2d2120?})
/app/kubecost-cost-model/pkg/duckdb/asset/assetqueryservice.go:133 +0x35c
created by github.com/kubecost/kubecost-cost-model/pkg/duckdb/asset.(*DuckDBAssetQueryService).QueryAsset in goroutine 175911
/app/kubecost-cost-model/pkg/duckdb/asset/assetqueryservice.go:146 +0x570
Hi @Hexta we're looking into this now.
Hello @Hexta we have this resolved and will be released in 2.3.3 patch. Also if you're needing it quickly and willing to take an RC 2.3.3-rc.0 is currently available.
Hi @cliffcolvin Thanks for the quick fix 🙏
We will wait until the v2.3.3 release since we use Helm chart from ECR
We've updated kubecost to v2.3.3, and it still crashes with another stack.
There is an example of the logs. Unfortunately, line order is not preserved.
@Hexta I'll get someone on my team to take a look at this again. Thank you for the additional information here.
We're investigating this now @Hexta
Hello, in an effort to consolidate our bug and feature request tracking, we are deprecating using GitHub to track tickets. If this issue is still outstanding and you have not done so already, please raise a request at https://support.kubecost.com/.
Kubecost Version
2.3.2
Kubernetes Version
1.28.9
Kubernetes Platform
EKS
Description
Aggregator panics with the following stack after random time during Repair ETL Allocation (Daily):
Steps to reproduce
Repair ETL Allocation (Daily)
Expected behavior
Aggregator doesn't panic.
Impact
No response
Screenshots
No response
Logs
No response
Slack discussion
No response
Troubleshooting