You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After deploying the helm Chart found in the Get Started section (https://icinga.com/blog/2024/03/14/introducing-icinga-for-kubernetes/ ) all pods are deployed and running but when browsing in the Icinga Web Interface, the kubernetes module is not working.
An SQL error is thrown: xyz.id not found.
It seems that there was recently a change in the code and "id" was replaced by "uuid" in the database scheme, but the "icinga-kubernetes-web" is still using the old scheme
The text was updated successfully, but these errors were encountered:
F0712 12:14:15.132606 1 main.go:204] can't retry: can't perform "INSERT INTO annotation (uuid, name, value) VALUES (:uuid, :name, :value) ON DUPLICATE KEY UPDATE uuid = VALUES(uuid), name = VALUES(name), value = VALUES(value)": Error 1406 (22001): Data too long for column 'name' at row 31
Affected Chart
icinga-stack
Which version of the app contains the bug?
0.3.0
Please describe your problem
After deploying the helm Chart found in the Get Started section (https://icinga.com/blog/2024/03/14/introducing-icinga-for-kubernetes/ ) all pods are deployed and running but when browsing in the Icinga Web Interface, the kubernetes module is not working.
An SQL error is thrown:
xyz.id not found.
It seems that there was recently a change in the code and "id" was replaced by "uuid" in the database scheme, but the "icinga-kubernetes-web" is still using the old scheme
The text was updated successfully, but these errors were encountered: