Description of problem:
When specifying a port with --rgw-frontends="beast port=80", port 80 is bound as ipv4 only. It should also bind to ipv6.
When specifying an ipv6 address with --rgw-frontends="beast endpoint=[::]:80", port 80 is bound as ipv6. If /proc/sys/net/ipv6/bindv6only is 0, it also binds to ipv4. It should only bind to the provided address family, regardless of the value of /proc/sys/net/ipv6/bindv6only.
Steps to Reproduce: (using port)
1. Start radosgw with: rgw frontends = beast port=80
2. Query socket statistics: $ ss -ntl '( sport = 80 )'
Actual results:
LISTEN 0 128 0.0.0.0:8000 *:*
Expected results:
LISTEN 0 128 *:8000 *:*
Steps to Reproduce: (using ipv6 endpoint)
1. Start radosgw with: rgw frontends = beast endpoint=[::]:80
2. Query socket statistics: $ ss -ntl '( sport = 80 )'
Actual results:
LISTEN 0 128 *:8000 *:*
Expected results:
LISTEN 0 128 [::]:8000 *:*
Comment 1Giridhar Ramaraju
2019-08-05 13:08:20 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate.
Regards,
Giri
Comment 2Giridhar Ramaraju
2019-08-05 13:09:50 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate.
Regards,
Giri
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:0312