Weird issue in OpenShift

[emilorol]

When I update the image and the env variables I get the following error:

usage: locust [-h] [-H HOST] [--web-host WEB_HOST] [-P PORT] [-f LOCUSTFILE]
              [--csv CSVFILEBASE] [--csv-full-history] [--master] [--slave]
              [--master-host MASTER_HOST] [--master-port MASTER_PORT]
              [--master-bind-host MASTER_BIND_HOST]
              [--master-bind-port MASTER_BIND_PORT]
              [--heartbeat-liveness HEARTBEAT_LIVENESS]
              [--heartbeat-interval HEARTBEAT_INTERVAL]
              [--expect-slaves EXPECT_SLAVES] [--no-web] [-c NUM_CLIENTS]
              [-r HATCH_RATE] [-t RUN_TIME] [--skip-log-setup] [--step-load]
              [--step-clients STEP_CLIENTS] [--step-time STEP_TIME]
              [--loglevel LOGLEVEL] [--logfile LOGFILE] [--print-stats]
              [--only-summary] [--no-reset-stats] [--reset-stats] [-l]
              [--show-task-ratio] [--show-task-ratio-json] [-V]
              [--exit-code-on-error EXIT_CODE_ON_ERROR] [-s STOP_TIMEOUT]
              [LocustClass [LocustClass ...]]
locust: error: argument -P/--port/--web-port: invalid int value: 'tcp://0.0.0.0:5557'

I was able to debug the container and manually run the locust command adding -P=5557 argument.

Any ideas?

Note: 0.0.0.0 is masking the real IP for obvious reasons.

[emilorol]

I found a simple solution to make it work:

Add to LOCUST_OPTS the option -P=8089 and it worked. I also added the LOCUST_OPTS environment variable to the slave pod and I was able to swarm the attacked host successfully.

Now I am looking for more information about the -P argument.