Im seeing my pipeline getting held up.

[bathina2]

Description of your issue:

Im seeing a job k10-vsphere-staging that blocks the pipeline. When it runs, the job nightly-cloud-volumes-cleanup is stuck as a queued job. Even though we should be able to run 8 parallel jobs.

NOTE: If you are experiencing a build failure, please include:

• Link to the build failure
• Scripts called from the yml (optional)

[bathina2]

Also I should note that the nightly-cloud-volumes-cleanup job triggers the k10-vsphere-staging job

[a-murphy]

I haven't found any reason why k10-vsphere-staging would have anything to do with whether or not nightly-cloud-volumes-cleanup will run. They're configured to use different node pools, so won't use the same allocations. Since k10-vsphere-staging uses a node pool with one static node and it appears that the more recent jobs did not reach a node, I would suggest reinitializing or replacing the static node if you have not already.