Description of problem: When a privileged port number is given with rgw_frontends=beast, the frontend fails to bind with EACCES because radosgw has already dropped its permissions with setuid/setgid. Version-Release number of selected component (if applicable): RHCS 3.1 How reproducible: Always Steps to Reproduce: 1. Start radosgw with --rgw_frontends "beast port=80" Actual results: Radosgw fails to start with an error message: > 2018-10-30 07:28:35.451529 7fe6b7badfc0 0 starting handler: beast > 2018-10-30 07:28:35.452356 7fe6b7badfc0 -1 failed to bind address 10.8.128.74:443: Permission denied Expected results: Radosgw should defer its calls to setuid/setgid until the beast frontend is able to bind to these priveleged ports. Additional info:
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-2019:0020