-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Topology broken in 1.0.1 with a JS error #9702
Comments
Thank you for reporting this, @commarla! Apologies for the delay, but HashiCorp was observing a holiday break. Parsing through that error message is always a bit of a challenge with minified code, but it appears to be that a node is being returned from the API without a The error is thrown here: nomad/ui/app/components/topo-viz.js Lines 55 to 64 in 3f73848
And nomad/ui/app/serializers/node.js Lines 7 to 12 in 3f73848
The easy fix here is to guard against |
With the info you provided I was able to pin down the nodes where NodeResources.Memory is null simply with a api call The faulty nodes are still running nomad 0.8.7. I have to upgrade ! Thanks |
Aha! That'll do it. I'll PR the null check too so the UI won't explode in this scenario. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Operating system and Environment details
Debian 9.13
Issue
Topology UI is not displaying
![image](https://user-images.githubusercontent.com/4509360/102766816-004ebd80-437f-11eb-98eb-b03b170ba288.png)
with this JS error
Maybe related to #9658 and #9617
I have three identical servers clusters, 2 are not working and 1 is working but the last one has only 3 clients and 1 alloc. The non working have 973 allocs / 113 clients and 226 allocs /32 clients
Reproduction steps
Just head to the topology
Nomad Server logs (if appropriate)
Nomad monitor logs in trace
The text was updated successfully, but these errors were encountered: