Bug 1749754
| Summary: | [GSS]When using Beast in RHCS 3.3, 'experimental-data-corruption-may-happen feature' flag is still required even though it is GA | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Karun Josy <kjosy> |
| Component: | RGW | Assignee: | Matt Benjamin (redhat) <mbenjamin> |
| Status: | CLOSED ERRATA | QA Contact: | RUDRA PRATAP <rpratap> |
| Severity: | high | Docs Contact: | Bara Ancincova <bancinco> |
| Priority: | medium | ||
| Version: | 3.3 | CC: | assingh, cbodley, ceph-eng-bugs, ceph-qe-bugs, kbader, mbenjamin, mkasturi, rpratap, sweil, tchandra, tserlin, vumrao |
| Target Milestone: | z1 | ||
| Target Release: | 3.3 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-12.2.12-50.el7cp Ubuntu: ceph_12.2.12-47redhat1 | Doc Type: | Bug Fix |
| Doc Text: |
.Enabling the `enable_experimental_unrecoverable_data_corrupting_features` flag is no longer required when using the Beast web server
To use the Beast web server, it was required to enable the `enable_experimental_unrecoverable_data_corrupting_features` flag even though Beast was fully supported and not a Technology Preview anymore. With this update, enabling `enable_experimental_unrecoverable_data_corrupting_features` is no longer required to use Beast.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-22 13:29:30 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1726135 | ||
|
Description
Karun Josy
2019-09-06 11:24:54 UTC
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 |