RHEA-2019:0286 - Product Enhancement Advisory

Topic

Updated heketi packages that fix several bugs and adds various enhancements are now available for OpenShift Container Storage 3.11.1.

Description

Heketi provides the Red Hat Gluster Storage volume lifecycle management. It creates the Red Hat Gluster Storage volumes dynamically and supports multiple Red Hat Gluster Storage clusters.

This advisory adds the following enhancements:

• Previously, an ongoing operation interrupted by a server restart or failure was not immediately recoverable and would leave a stale operation in the heketi database. These stale and failed operations captured the state of the system which had to be manually resolved. With this fix, Heketi supports an automatic clean up feature that can also be activated offline or on demand. (BZ#1641668)
• This release introduces two diagnostics features in Heketi:
• a new command `heketi-cli db check` and its offline server variant `heketi db check` check the consistency of heketi's database.
• a new command `heketi-cli server state examine gluster` and its server counterpart `heketi offline state examine gluster` compare data from Gluster with that in heketi's database to detect out-of-sync situations. (BZ#1641680)

This advisory also fixes the following bugs:

• Previously, heketi executed gluster commands with no timeout specification. As a consequence, when glusterd was busy with more requests it lead to the default timeout (120 seconds) of CLI. Heketi considered this as a command failure while glusterd continued to complete the request. With this fix, gluster commands are now specified with a higher timeout value of 600 seconds by default, giving glusterd more time to complete the request. This default value 600 seconds for the timeout seems to be sufficient for all known cases where glusterd takes longer due to system load. If needed, the value can be reconfigured with the `gluster_cli_timeout` config-file variable and the `HEKETI_GLUSTER_CLI_TIMEOUT` environment variable. (BZ#1651041)
• Previously, device size metrics did not use the prescribed base unit of bytes and hence, incorrect values were interpreted. With this fix, the device size metric sizes are correctly published in bytes. (BZ#1640027)

Users of Heketi are advised to upgrade to these updated packages, which fixes these bugs and adds enhancements.

Solution

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

For details on how to apply this update, refer to:

https://access.redhat.com/articles/11258

Affected Products

• Red Hat Enterprise Linux Server 7 x86_64
• Red Hat Gluster Storage Server for On-premise 3 for RHEL 7 x86_64

Fixes

• BZ - 1434685 - heketi delete device should not delete the device when the device is online
• BZ - 1634745 - Used space in BHV exceeds the size of the total block devices when tcmu-runner is DOWN on 1 node , during pvc creation
• BZ - 1635736 - Free space of a BHV used up by "Spurious" BV IDS(seen from heketi dump) on bringing down 2 bricks during pvc creation
• BZ - 1636409 - df -kh lists an extra brick when gluster pod was re-spinned during pvc creation activity
• BZ - 1636477 - killing gluster-blockd during pvc-creation leads to spurious BV IDs using up complete free space of the BHV
• BZ - 1640027 - heketi metrics displayed for disk parameters in prometheus graph and console are incorrect.
• BZ - 1641668 - [RFE] Add ability for heketi server to automatically resolve stale or failed operations
• BZ - 1641680 - [RFE] Add ability to heketi server to output diagnostics information for OCS
• BZ - 1647016 - Rebase heketi to version 8
• BZ - 1651041 - Higher gluster cli timeout value in all gluster cli commands
• BZ - 1661517 - heketi-cli volume list returns Error: Id not found
• BZ - 1662141 - On scaling gluster pods to '2' and deleting pvcs, heketi intermittently lists fewer volumes than the total volumes present with Error: Id not found

CVEs

(none)

References

(none)