Looks like we customize the ephemeral port range on the swift hosts to 1024-65535, maybe we can push up the range swift-proxy chooses source ports from to help prevent this?

Change 808040 had a related patch set uploaded (by Herron; author: Herron):

[operations/puppet@production] swift: update ephemeral port range from 1024-65535 to 10240-65535

https://gerrit.wikimedia.org/r/808040

This issue seems to be related to deploying ipmi-exporter fleetwide for the first while the host/swift were already running for a while and thus the exporter port was in use as an ephemeral port.

Under normal operations AFAIK on reboot the exporters start and grab the port, and we haven't seen this issue (exporters unable to start) on thanos/swift hosts on a regular basis at least. Technically the issue can still happen if we're restarting exporters and the kernel assigns the ephemeral ports in the meantime, though it is a pretty small window. Given the above IMHO we're good to leave things as is, also given that we don't deploy new exporters fleetwide that often anymore

Change 808040 abandoned by Herron:

[operations/puppet@production] swift: update ephemeral port range from 1024-65535 to 10240-65535

Reason:

didn't move forward with this please see task

https://gerrit.wikimedia.org/r/808040