Back to bug 1756861

Who When What Removed Added
RHEL Program Management 2019-09-30 07:05:00 UTC Keywords ZStream
John Mulligan 2019-11-08 19:40:32 UTC Summary options which tunes heketidbstorage for safer workloads does not get updated during an upgrade from 3.11.3 to 3.11.4 Automatically tune heketidbstorage for safer workloads (on container start)
Prasanth 2019-11-14 07:06:57 UTC QA Contact pprakash knarra
Patric Uebele 2019-11-14 11:27:54 UTC CC puebele
RHEL Program Management 2019-11-14 11:28:01 UTC Target Release --- OCS 3.11.z Batch Update 5
Yaniv Kaul 2019-11-17 11:49:44 UTC Priority unspecified urgent
Severity high urgent
Raghavendra Talur 2019-12-10 22:00:50 UTC Status NEW POST
CC rtalur
Raghavendra Talur 2019-12-11 10:01:20 UTC Status POST MODIFIED
errata-xmlrpc 2019-12-11 11:28:40 UTC Status MODIFIED ON_QA
Arun Kumar 2019-12-12 06:20:07 UTC CC arukumar
QA Contact knarra arukumar
Arun Kumar 2019-12-16 09:10:20 UTC CC jmulligan
Flags needinfo?(jmulligan)
John Mulligan 2019-12-16 15:31:35 UTC Fixed In Version rhgs3/rhgs-volmanager-rhel7:3.11.5-1
Flags needinfo?(jmulligan)
Raghavendra Talur 2019-12-17 14:39:54 UTC Doc Type If docs needed, set a value Bug Fix
Arun Kumar 2019-12-20 10:46:57 UTC Status ON_QA VERIFIED
John Mulligan 2020-02-20 18:37:35 UTC Doc Text Previously, new installations using Heketi had tuned the self-provisioned heketidbstorage gluster volumes for db workloads but did nothing to volumes created by older installs. Now, when a container hosting Heketi is first started a built-in tool will attempt to automatically tune the settings of an existing heketidbstorage volume.
Amrita 2020-02-26 05:52:05 UTC CC asakthiv
Doc Text Previously, new installations using Heketi had tuned the self-provisioned heketidbstorage gluster volumes for db workloads but did nothing to volumes created by older installs. Now, when a container hosting Heketi is first started a built-in tool will attempt to automatically tune the settings of an existing heketidbstorage volume. .New installations using Heketi tunes the settings of an existing heketidbstorage volume

Previously, new installations using Heketi had tuned the self-provisioned heketidbstorage gluster volumes for db workloads but did nothing to volumes created by older installs. Now, when a container hosting Heketi is first started a built-in tool will attempt to automatically tune the settings of an existing heketidbstorage volume.
Anjana Suparna Sriram 2020-02-26 19:07:42 UTC CC asriram
Doc Text .New installations using Heketi tunes the settings of an existing heketidbstorage volume

Previously, new installations using Heketi had tuned the self-provisioned heketidbstorage gluster volumes for db workloads but did nothing to volumes created by older installs. Now, when a container hosting Heketi is first started a built-in tool will attempt to automatically tune the settings of an existing heketidbstorage volume.
Previously, new installations using Heketi had tuned the self-provisioned heketidbstorage gluster volumes for db workloads but did nothing to volumes created by older installs. Now, when a container hosting Heketi is first started a built-in tool will attempt to automatically tune the settings of an existing heketidbstorage volume.
Anjana Suparna Sriram 2020-02-26 19:08:31 UTC Doc Text Previously, new installations using Heketi had tuned the self-provisioned heketidbstorage gluster volumes for db workloads but did nothing to volumes created by older installs. Now, when a container hosting Heketi is first started a built-in tool will attempt to automatically tune the settings of an existing heketidbstorage volume. Previously, new installations using Heketi had tuned the self-provisioned heketidbstorage gluster volumes for db workloads but did nothing to volumes created by older installs. Now, when a container hosting Heketi is first started and a built-in tool attempts to automatically tune the settings of an existing heketidbstorage volume.
errata-xmlrpc 2020-02-26 19:39:25 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2020-02-26 20:05:00 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2020-02-26 20:05:00 UTC
errata-xmlrpc 2020-02-26 20:05:23 UTC Link ID Red Hat Product Errata RHBA-2020:0621

Back to bug 1756861