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
Encountered a 500 Internal Server Error when attempting to view the status history of a newly connected node in the Nebraska instance list whose update is paused by the update policy and is in Waiting.... status. The backend logs show the error: sql: Scan error on column index 2, name "version": converting NULL to string is unsupported.
Impact
Unable to view the status history of a newly connected node, which impairs the ability to monitor updates and debug potential issues.
Environment and steps to reproduce
Set-up:
Environment: Nebraska running locally on localhost:3000
Spin up flatcar nodes with qemu.
Task:
Try to update two nodes using Nebraska's update management feature. After the first update change the policy to 1/day do pause the update for the second one.
Action(s):
a. Issue an update to one node.
b. Changed the update policy to 1/day to prevent other nodes from updating.
c. Connect a new node to Nebraska.
d. Attempted to view the status history of the new node via the instance list in the Nebraska UI.
Error:
Frontend: HTTP 500 at http://localhost:3000/api/apps/e96281a6-d1af-4bde-9a0a-97b76e56dc57/groups/5b810680-e36a-4879-b98a-4f989e80b899/instances/f9bb8dd0b86141a1b11efd4c59a03db6/status_history
Backend logs include:
sql: Scan error on column index 2, name "version": converting NULL to string is unsupported
Expected behavior
The status history of the newly connected node should display correctly, without generating a 500 Internal Server Error on the frontend or backend.
Relevant backend log excerpt
2025-01-15T16:54:40+02:00 ERR getInstanceStatusHistory - getting status history limit 0 error="sql: Scan error on column index 2, name \"version\": converting NULL to string is unsupported" appID=e96281a6-d1af-4bde-9a0a-97b76e56dc57 context=nebraska groupID=5b810680-e36a-4879-b98a-4f989e80b899 instanceID=f9bb8dd0b86141a1b11efd4c59a03db6
2025-01-15T16:54:43+02:00 ERR getInstanceStatusHistory - getting status history limit 0 error="sql: Scan error on column index 2, name \"version\": converting NULL to string is unsupported" appID=e96281a6-d1af-4bde-9a0a-97b76e56dc57 context=nebraska groupID=5b810680-e36a-4879-b98a-4f989e80b899 instanceID=f9bb8dd0b86141a1b11efd4c59a03db6
2025-01-15T16:55:09+02:00 ERR getInstanceStatusHistory - getting status history limit 0 error="sql: Scan error on column index 2, name \"version\": converting NULL to string is unsupported" appID=e96281a6-d1af-4bde-9a0a-97b76e56dc57 context=nebraska groupID=5b810680-e36a-4879-b98a-4f989e80b899 instanceID=f9bb8dd0b86141a1b11efd4c59a03db6
2025-01-15T16:55:10+02:00 ERR getInstanceStatusHistory - getting status history limit 0 error="sql: Scan error on column index 2, name \"version\": converting NULL to string is unsupported" appID=e96281a6-d1af-4bde-9a0a-97b76e56dc57 context=nebraska groupID=5b810680-e36a-4879-b98a-4f989e80b899 instanceID=f9bb8dd0b86141a1b11efd4c59a03db6
The text was updated successfully, but these errors were encountered:
Description
Encountered a
500 Internal Server Error
when attempting to view the status history of a newly connected node in the Nebraska instance list whose update is paused by the update policy and is inWaiting....
status. The backend logs show the error:sql: Scan error on column index 2, name "version": converting NULL to string is unsupported
.Impact
Unable to view the status history of a newly connected node, which impairs the ability to monitor updates and debug potential issues.
Environment and steps to reproduce
Set-up:
localhost:3000
Task:
Action(s):
a. Issue an update to one node.
b. Changed the update policy to 1/day to prevent other nodes from updating.
c. Connect a new node to Nebraska.
d. Attempted to view the status history of the new node via the instance list in the Nebraska UI.
Error:
http://localhost:3000/api/apps/e96281a6-d1af-4bde-9a0a-97b76e56dc57/groups/5b810680-e36a-4879-b98a-4f989e80b899/instances/f9bb8dd0b86141a1b11efd4c59a03db6/status_history
Expected behavior
The status history of the newly connected node should display correctly, without generating a
500 Internal Server Error
on the frontend or backend.Relevant backend log excerpt
The text was updated successfully, but these errors were encountered: