Bug #15014
closed
[Workbench] Hide busy/idle nodes display when crunch1 is not active
Description
The busy/idle nodes display on the dashboard is supposed to be hidden when it would be wrong/misleading, i.e., when info[slurm_state] is not updated in the nodes table because crunch_dispatch.rb is not running.
Currently, it's hidden when the crunch1 APIs are completely disabled (pipeline_instances.index API doesn't exist). This is true for a site that has never used crunch1, but it's not true for a site that has migrated to crunch2, isn't running crunch_dispatch.rb, but still allows users to view their old crunch1 pipelines/jobs.
The condition in source:apps/workbench/app/views/projects/_show_dashboard.html.erb could be changed:
- if !PipelineInstance.api_exists?(:index)
+ if !PipelineInstance.api_exists?(:create)
Related issues
Updated by Tom Clegg over 5 years ago
- Related to Idea #10524: [Crunch2] In Crunch2-only environments, workbench should use "processes" instead of "pipelines and processes" and "workflows" instead of "pipeline templates" as is used in a mixed environment. added
Updated by Tom Clegg over 5 years ago
- Related to deleted (Idea #10524: [Crunch2] In Crunch2-only environments, workbench should use "processes" instead of "pipelines and processes" and "workflows" instead of "pipeline templates" as is used in a mixed environment.)
Updated by Tom Clegg over 5 years ago
- Related to Bug #11014: [Workbench] Hide the "idle/busy nodes" part of the dashboard if crunch1 APIs are disabled added
Updated by Tom Clegg over 5 years ago
- Has duplicate Bug #15036: [Crunch2] Idle/busy node count not accurate if crunch1 not running added
Updated by Tom Clegg over 5 years ago
- Related to Feature #15087: [Workbench] Show number of queued containers on dashboard (instead of busy/idle nodes) added
Updated by Tom Clegg about 5 years ago
- Status changed from New to In Progress
15014-wrong-node-count @ 5fd5bdc0dc0b1d2359b0146db05e7b89e0193f14 -- https://ci.curoverse.com/view/Developer/job/developer-run-tests/1528/
Updated by Tom Clegg about 5 years ago
15014-wrong-node-count @ 22be65d205b40ca0b2cb579b9e49ffec9e260110 -- https://ci.curoverse.com/view/Developer/job/developer-run-tests/1529/
Updated by Tom Clegg about 5 years ago
15014-wrong-node-count @ 4e219991edcf0b626e84b9db9525620ba605cb89 -- https://ci.curoverse.com/view/Developer/job/developer-run-tests/1530/
Updated by Tom Morris about 5 years ago
- Target version set to 2019-09-25 Sprint
Updated by Tom Clegg about 5 years ago
- Assigned To set to Tom Clegg
- Target version changed from 2019-09-25 Sprint to 2019-10-09 Sprint
Updated by Tom Clegg about 5 years ago
15014-wrong-node-count @ e7eb231e0442870e624388ccaf95751684cb1636 -- https://ci.curoverse.com/view/Developer/job/developer-run-tests/1546/
Updated by Tom Clegg about 5 years ago
15014-wrong-node-count @ e7eb231e0442870e624388ccaf95751684cb1636 -- https://ci.curoverse.com/view/Developer/job/developer-run-tests/1548/
Updated by Tom Clegg about 5 years ago
15014-wrong-node-count @ 18b8c3b584a9337977df997624176b5a66b256e9 -- https://ci.curoverse.com/view/Developer/job/developer-run-tests/1566/
Updated by Peter Amstutz about 5 years ago
Tom Clegg wrote:
15014-wrong-node-count @ 18b8c3b584a9337977df997624176b5a66b256e9 -- https://ci.curoverse.com/view/Developer/job/developer-run-tests/1566/
LGTM
Updated by Tom Clegg about 5 years ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|b4be060bb0ee42281fc3a044c60d2b55c74475f8.