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
I get a spinning wheel when accessing Hubble UI. The developer console shows this error:
stream.ts:223 Unknown error: Error: cannot convert to safe number
at si.toNumber (pb-long.js:50:19)
at t.value (observer_pb.ts:1340:56)
at t.value (observer_pb.ts:1263:45)
at t.value (status_pb.ts:126:54)
at t.value (notifications_pb.ts:141:51)
at t.value (ui_pb.ts:1609:52)
at t.fromBinary (message-type.js:84:21)
at control-stream.ts:42:50
at emitter.ts:82:33
at Set.forEach (<anonymous>)
Running into the same issue with cililum/hubble v1.16.1. Can be worked around by setting the query param on the url manually: https://<host>/?namespace=kube-system
For us, it always seems to error on these lines in observer_pb.ts (1339 in the debugger) suggesting that some data is invalid.
case /* uint64 uptime_ns */ 6:
message.uptimeNs = reader.uint64().toNumber();`
We're running karpenter on EKS and most of our nodes have version: v1.30.9-eks-5d632ec except for 1-2 nodes used to bootstrap the cluster which are on v1.30.4-eks-a737599 and have large uptimes (120d) etc. When I look at the value of message.name in the debugger it always corresponds to one of these old nodes.
When I recycle these old nodes, hubble starts working again suggesting that the uptime of the node doesn't convert nicely to a unint64.
However 120 days to Ns is roughly an e+16 and the max uint64 is roughly an e+19 I believe so this is likely an error in parsing the number somewhere.
I get a spinning wheel when accessing Hubble UI. The developer console shows this error:
Backend logs:
Hubble UI: v0.13.1
Hubble Relay: v1.15.7
The text was updated successfully, but these errors were encountered: