Bug #3976: [API] Non-admin users should see all nodes with crunch_worker_state busy/idle, regardless of ping age. - Arvados

Actions

Bug #3976

closed

Status:

Closed

Priority:

Normal

Assigned To:

Tom Morris

Category:

Workbench

Target version:

Story points:

0.5

Description

Desired behavior:

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

comput_status_0.jpg (59.1 KB) comput_status_0.jpg

Abram Connelly, 09/24/2014 03:41 PM

Actions

Looks like a permissions problem, I can see the numbers fine with an admin account.

Actions

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

Actions

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.

Actions

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)

Actions