[CI] Failure due to hard coded minio port

[tvernum]

https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.4+multijob-unix-compatibility/os=fedora/20/console

20:21:44 > Task :plugins:repository-s3:startMinio FAILED
20:21:44 Task ':plugins:repository-s3:startMinio' is not up-to-date because:
20:21:44   Task has not declared any outputs despite executing actions.
20:21:44 �7ERROR �8�[6CUnable to start the server: Port :60920 is already in use.
20:21:44 �7      �8�[6C> Please ensure no other program uses the same address/port.
20:21:44 :plugins:repository-s3:startMinio (Thread[Task worker for ':' Thread 13,5,main]) completed. Took 0.018 secs.
20:21:44 * Where:
20:21:44 :plugins:repository-s3:integTestMinioCluster#stop (Thread[Task worker for ':' Thread 13,5,main]) started.
20:21:44 Build file '/var/lib/jenkins/workspace/elastic+elasticsearch+6.4+multijob-unix-compatibility/os/fedora/plugins/repository-s3/build.gradle' line: 245

The tests for minio use a hard-coded port number (60920), which caused a CI failure.

elasticsearch/plugins/repository-s3/build.gradle

Line 135 in 4cbcc1d

final String minioAddress = "127.0.0.1:60920"

[elasticmachine]

Pinging @elastic/es-distributed

[tvernum]

Another:
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/2487/console

05:17:04 > Task :plugins:repository-s3:startMinio FAILED
...
05:17:04 �7ERROR �8�[6CUnable to start the server: Port :60920 is already in use.
05:17:04 �7      �8�[6C> Please ensure no other program uses the same address/port.

[bleskes]

@tlrx can you take a look when you have a moment? Thanks.

[jasontedor]

@ywelsch Might be interested too. If I recall from a past discussion this is a limitation at this time?

[spinscale]

another one: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+matrix-java-periodic/ES_BUILD_JAVA=java10,ES_RUNTIME_JAVA=java10,nodes=virtual&&linux/228/console

had a quick look and minio does not allow for binding to any port and report back, you have to specify a port between 1 and 65535 yourself

[ywelsch]

We can have it retry on a higher port. I'm astonished though that this is causing issues on CI as we have other places in our build with hard-coded ports.

[dnhatn]

Relates #32208