The output from "ocluster-admin show" is sometimes cryptic

The registered section shows:

registered:
  i7-worker-01 (0): [] (1 running)
  i7-worker-02 (10): [opam-repo-ci:macos-homebrew-ocaml-4.14-tezos-injector-016-PtMumbai.16.0~rc1-f280a0f2882102032292266c928080f782a1c0aa@4585m(10+urgent)] (1 running)
  i7-worker-03 (0): [] (1 running)
  i7-worker-04 (10): [opam-repo-ci:macos-homebrew-ocaml-4.14-tezos-layer2-utils-016-PtMumbai.16.0~rc1-f280a0f2882102032292266c928080f782a1c0aa@4565m(10+urgent)] (1 running)

to me i interpret this as:

• i7-worker-02 and i7-worker-04 are currently building tezos-injector-016-PtMumbai and tezos-layer2-utils-016-PtMumbai respectively
• i7-worker-01 and i7-worker-04 are doing ??? (something) but nothing is shown on the nature of the work

a similar output that is as perplexing is:

queue: (backlog) [... <a huge backlog>]
registered:
  m1-worker-02 (0): [] (1 running)
  m1-worker-03 (0): [] (1 running)
  m1-worker-04 (0): [] (1 running)

where without sshing into the machines themselves you wouldn't be able to know what they are doing.

Start with the ocluster-admin show entry point and trace how the registered worker entries and their running jobs are formatted. Compare the shown output with the worker activity it is intended to represent; done means the command identifies what workers with running jobs are doing without SSH access.