Bug #15707
closed
[arvados-dispatch-cloud] should not include "on hold" containers in "queued" metrics
Description
On qr1hi, we currently have 26 queued containers according to a-d-c. None are running and the situation hasn't changed in many hours.
One example is https://workbench.qr1hi.arvadosapi.com/containers/qr1hi-dz642-ga16kq3tdga8nnn, which is listed as 'on hold' aka priority=0. That is because the matching container request is cancelled (https://workbench.qr1hi.arvadosapi.com/container_requests/qr1hi-xvhdp-t2l3czj8z3c49fj).
a-d-c should not report containers in that state as queued.
Updated by
Updated by Tom Clegg over 4 years ago
- Subject changed from [a-d-c] considers containers 'on hold' as queued to [arvados-dispatch-cloud] should not include "on hold" containers in "queued" metrics
- Description updated (diff)
- Target version set to Arvados Future Sprints
Updated by Tom Clegg over 4 years ago
- Status changed from New to In Progress
- Assigned To set to Tom Clegg
- Target version changed from Arvados Future Sprints to 2019-10-23 Sprint
Updated by Tom Clegg over 4 years ago
15707-dispatch-onhold-metrics @ aea1693cfc6359a7f290797724ee989bc47b09e0 -- https://ci.curoverse.com/view/Developer/job/developer-run-tests/1604/
Updated by Eric Biagiotti over 4 years ago
Tom Clegg wrote:
15707-dispatch-onhold-metrics @ aea1693cfc6359a7f290797724ee989bc47b09e0 -- https://ci.curoverse.com/view/Developer/job/developer-run-tests/1604/
This LGTM, thanks!
Updated by Tom Clegg over 4 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|fed5a79b5852ebf78d660ec8cb169ce512ad6532.
Updated by