Bug #3976
closed
[API] Non-admin users should see all nodes with crunch_worker_state busy/idle, regardless of ping age.
Added by Abram Connelly over 9 years ago.
Updated 2 months ago.
Description
Desired behavior:
- Show busy and idle nodes regardless of last_ping_at.
Fix:
- In NodesController#index, filter with something like
Node.all.select { |node| ['busy','idle'].includes? node.crunch_worker_state } instead of last_ping_at.
Original bug description below. The actual problem with ping_at not being set on 9tee4 has already been fixed.
Current behavior:
- 'Queued jobs', 'Busy nodes' and 'Idle nodes' all show 0. Screenshot attached.
- Investigation reveals node_ping_at is old (evidently ping stopped working ~Sep3).
Files
Looks like a permissions problem, I can see the numbers fine with an admin account.
- Subject changed from 9tee4 does not have proper 'Compute status' information in workbench to [Workbench] 9tee4 does not have proper 'Compute status' information in workbench
- Subject changed from [Workbench] 9tee4 does not have proper 'Compute status' information in workbench to [Workbench] users do not have permission to see 'compute status' information
- Category set to Workbench
- Assigned To set to Tim Pierce
- Target version changed from Bug Triage to Arvados Future Sprints
Confirmed, non-admin accounts see 0 for all node status information in the Compute status dashboard pane.
- Subject changed from [Workbench] users do not have permission to see 'compute status' information to [API] Non-admin users should see all nodes with crunch_worker_state busy/idle, regardless of ping age.
- Description updated (diff)
- Description updated (diff)
- Assigned To changed from Tim Pierce to Tom Morris
- Target version deleted (
Arvados Future Sprints)
- Target version set to Future
- Status changed from New to Closed
- Release deleted (
60)
- Target version deleted (
Future)
Also available in: Atom
PDF
Updated by 
Updated by Tim Pierce 
Updated by 
Updated by Tom Morris 
Updated by 