Investigate pipeline jobs not running on shards

Description

Normally, the platform python pipeline job should collect a bunch of IP addresses (for workers) and shard the tests out onto them. You will see something like this in the Console logs:

Jeremy saw this, in which no IP addresses were collected and the test all ran on one shard:

Link to offending build: https://build.testeng.edx.org/job/edx-platform-python-pipeline-pr/9739/

This causes the job to run for very long and times out.

Steps to Reproduce

None

Current Behavior

None

Expected Behavior

None

Reason for Variance

None

Release Notes

None

User Impact Summary

None

Assignee

Unassigned

Reporter

Stuart Young

Labels

None

Reach

None

Impact

None

Platform Area

None

Customer

None

Partner Manager

None

URL

None

Contributor Name

None

Groups with Read-Only Access

None

Actual Points

None

Category of Work

None

Platform Map Area (Levels 1 & 2)

None

Platform Map Area (Levels 3 & 4)

None

Priority

Unset
Configure