* Description of problem: RHCS 3.3.0 release notes say that radosgw beast frontend is now fully supported: "The Beast.Asio web server front end for the Object Store Gateway (RGW) is now GA and a fully supported option." However, to start using Beast the 'experimental-data-corruption-may-happen feature flag' is still required. From RGW logs : -------- 2019-09-05 22:06:21.114174 7fcabb67d000 0 deferred set uid:gid to 167:167 (ceph:ceph) 2019-09-05 22:06:21.114276 7fcabb67d000 0 ceph version 12.2.12-48.el7cp (26388d73d88602005946d4381cc5796d42904858) luminous (stable), process radosgw, pid 43069 2019-09-05 22:06:21.301460 7fcabb67d000 -1 *** experimental feature 'rgw-beast-frontend' is not enabled *** This feature is marked as experimental, which means it - is untested - is unsupported - may corrupt your data - may break your cluster is an unrecoverable fashion To enable this feature, add this to your ceph.conf: enable experimental unrecoverable data corrupting features = rgw-beast-frontend 2019-09-05 22:06:21.301538 7fcabb67d000 0 WARNING: skipping unknown framework: beast ---------- This is documented in our Object Gateway Guide, but this kind of sends conflicting messages to customers if it can be actually used in production or not. Is there any specific reason we need to continue to use this flag or can we remove it in the next release? * Version-Release number of selected component (if applicable): RHCS 3.3 How reproducible: Always
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:3173