beast: multiple v4 and v6 endpoints with the same port will cause failure
currently the following combinations are known to fail:
rgw frontends = beast endpoint=[::]:8000 endpoint=0.0.0.0:8000
rgw frontends = beast port=8000 endpoint=[::]:8000
with something like:
2019-03-29 17:22:29.728 7f15db9e9900 4 frontend listening on 0.0.0.0:8000 2019-03-29 17:22:29.728 7f15db9e9900 -1 failed to bind address [::]:8000: Address already in use
As the systemflag for bindv6only (cat /proc/sys/net/ipv6/bindv6only to check) is usually true for many Linux systems, specifying both v4 and v6 addresses will mean that configuration has to be aware of the flag and set only v6 for eg. A better behaviour here would be to be explicit here and only bind to v4 or v6 addresses as configured so that configuration remains explicit.
#2 Updated by Abhishek Lekshmanan about 2 years ago
- Backport changed from nautilus to nautilus, mimic
for luminous the only thing was beast was an experimental feature, otherwise I can mark it for l as well, given that people upgrading from luminous -> nautilus then can get by without needing to change the configuration.