Description of problem: Options to set to be derived from https://access.redhat.com/solutions/3458751 does not get applied when user / customer performs an upgrade from OCS3.11.3 to OCS3.11.4 Version-Release number of selected component (if applicable): sh-4.2# rpm -qa | grep heketi heketi-client-9.0.0-7.el7rhgs.x86_64 heketi-9.0.0-7.el7rhgs.x86_64 How reproducible: Always Steps to Reproduce: 1. Install OCS3.11.3 2. Upgrade setup to OCS3.11.4 3. Actual results: Do not see the options set on heketidbstorage volume which tunes heketidbstorage for safer workloads. sh-4.2# gluster volume get heketidbstorage performance.readdir-ahead Option Value ------ ----- performance.readdir-ahead off sh-4.2# gluster volume get heketidbstorage user.heketi.dbstoragelevel volume get option: failed sh-4.2# gluster volume get heketidbstorage performance.io-cache Option Value ------ ----- performance.io-cache on sh-4.2# gluster volume get heketidbstorage performance.write-behind Option Value ------ ----- performance.write-behind on sh-4.2# gluster volume get heketidbstorage performance.open-behind Option Value ------ ----- performance.open-behind on sh-4.2# gluster volume get heketidbstorage performance.quick-read Option Value ------ ----- performance.quick-read on sh-4.2# gluster volume get heketidbstorage performance.strict-o-direct Option Value ------ ----- performance.strict-o-direct off sh-4.2# gluster volume get heketidbstorage performance.read-ahead Option Value ------ ----- performance.read-ahead on sh-4.2# gluster volume get heketidbstorage performance.io-cache Option Value ------ ----- performance.io-cache on sh-4.2# gluster volume get heketidbstorage performance.readdir-ahead Option Value ------ ----- performance.readdir-ahead off sh-4.2# gluster volume get heketidbstorage user.heketi.dbstoragelevel volume get option: failed Expected results: Options which tunes heketidbstorage for safer workloads should be present after an upgrade as well to avoid any data corruptions. Additional info:
Post https://github.com/heketi/heketi/pull/1680
Doc text has been modified.
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:0621