-
Notifications
You must be signed in to change notification settings - Fork 489
Infinite loading (only header shown), error "crd conversion failed: cannot convert int64 to float64" #72
Comments
@hjacobs would you be able to provide the list of CRDs installed for this cluster? |
Here the complete YAML dump: https://gist.github.com/hjacobs/9876005c325e18930992aa2bd2eaf7da |
I get the same SIGSEGV with v0.5.1 on a cluster that has CRDs installed on it. Same errors and stacktrace, though different CRDs. Full output when I start octant:
|
A partial fix (#124) for this was merged in that will allow octant to continue, similar to the previous fix. If you have time and are willing, you can build from the latest master and octant should not crash anymore. This fix does not address the conversion error itself, you will still see those errors logged out to the console. |
Ditto for me as well. The offending CRD's Octant complains about seem to be these:
This was on a cluster provisioned by PKS v1.4.1 |
Same happens for me on version 0.5.1
|
Fails with the spark operator CRD too in version
|
install on my Mac and got the same issue
|
I'll add that I'm using a Mac as well. Confirmed with coworker using Windows that he does not see the same issue while using the same version of Octant and targeting the same cluster. I also confirmed that building from the latest master resolved the immediate crash and allowed me to use Octant. The offending CRD's from before are missing from the list within the UI. |
I suspect that this is due to the CRDs in question specifying
|
Seems totally reasonable. I'm throwing cephclusters out into the list.
|
I'm no Go expert but following @munnerz suspicion I had a look at the crd.go files for the Spark Operator we have deployed and can confirm it contains lots of float64 values in the spec. One example: |
closing in favor of #143 |
Octant 0.4 does not load for me:
Console is full of these errors:
The text was updated successfully, but these errors were encountered: