When upgrading the Kubecost helm chart from version 2.9.6 to 3.1.3, the kubecost-aggregator won't start up properly. It fails during database schema upgrades with the following logs:
2026-02-25T17:22:34.290689975Z ERR error opening DB: error executing dynamic sql: code: 1, message: System call renameat2() is not supported
2026-02-25T17:22:34.290733326Z ERR a working database connection is required. please ensure that the DB at the connection parameters provided is working and accepting connections
2026-02-25T17:22:34.290742956Z WRN will retry connection in 30s (try 20/20)...
Meanwhile, the UI shows the following:
When I search the Internet for "System call renameat2() is not supported", I find a bug that has been fixed ages ago in glibc 2.18. Does anyone else have this issue?
System information:
Kubernetes platform: kubeadm v1.35.1 / CentOS 9 Stream (kernel-5.14.0-669.el9.x86_64, glibc-2.34-245.el9.x86_64) / VMware ESXi, 8.0.3, 24784735
from version