error: argument --master-port: invalid int value bug

Describe the bug

locust: error: argument --master-port: invalid int value: ‘tcp://172.30.44.4:8089’

Expected behavior

Locust runs correctly without producing this error. As --master-port wasn’t even supplied.

Actual behavior

When invoking locust in master mode using the following: locust -f /scripts/locust-script.py --master the following error occurs locust: error: argument --master-port: invalid int value: 'tcp://172.30.44.4:8089'

Steps to reproduce

Start locust in the container using the command: locust -f /scripts/locust-script.py --master Error occurs.

Environment settings

• OS: RHEL
• Python version: Python 3.6 from image registry.redhat.io/rhel8/python-36
• Locust version: Using latest.

[cyberw]

This should not happen any more now that we have renamed the env var for master port to LOCUST_MASTER_NODE_PORT (the original issue I mean, some of the followup discussion here might still apply, but that should be a separate ticket)

[cjbehm]

ahh ok. i see what’s happening; it’s a clash between auto-populated ENV variables that come from creating “Service” objects in k8s. It only clicked now, but naming a Service “locust-master” in k8s results in an environment value that is “LOCUST_MASTER_SERVICE” (and a bunch of other values). And those auto names happen to overlap some of the names that locust looks at.

I’m not sure what the best solution is; documentation could help but that’s always fragile. Obviously short-term I can just just different names for the k8s objects.