nomad UI "couldn't connect to client" when evaluating CPU and Memory for a job

[Justin-DynamicD]

When browsing the new UI in Nomad 0.7.0, if I browse a client and look at the allocation table, both the CPU and Memory report a yellow "!" instead of a value. Hovering over these warnings with the mouse reports "couldn't connect to client".

It's possible I'm missing a setting somewhere but wasn't able to find it. As an FYI nomad alloc-status -stats returns information just fine.

[dadgar]

@Justin-DynamicD Is the UI being accessed within the same network as when alloc-status works? A requirement is that you can contact the client node directly to access stats.

[DingoEatingFuzz]

This is a duplicate of either #3497 or #3527.

[Justin-DynamicD]

"same network" is a bit ambiguous so Ill clarify: all systems in question are route-able, but not necessarily the same subnet.

The Nomad cluster is on 3 separate subnets, all rout-able to the node in question (which shares one of the subnets). I can successfully test from a 4th rout-able subnet in another physical datacenter.

So there is lots of routing involved, but no ACLs, firewall, or otherwise.

[dadgar]

@Justin-DynamicD Thanks for clarifying. Closing as @DingoEatingFuzz points out this has been fixed by #3530 and will be part of 0.7.1! Thanks for reporting!

[github-actions]

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.