- Issued:
- 2018-04-05
- Updated:
- 2018-04-05
RHEA-2018:0638 - Product Enhancement Advisory
Synopsis
heketi bug fix and enhancement update
Type/Severity
Product Enhancement Advisory
Red Hat Insights patch analysis
Identify and remediate systems affected by this advisory.
Topic
Updated heketi packages that fix several bugs and add various enhancements
are now available for Container-Native Storage 3.9 and Container Ready
Storage.
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 update fixes the following bugs:
- Previously, deleting an heketi pod while some heketi operation was in progress would result in incomplete entries in the database. With this fix, such entries are marked "pending" until the operation is completed thus leading to a consistent database view. (BZ#1415750)
- Earlier, the 'device info' output displayed the state of the device as 'failed' after a device remove operation was completed. With this fix, the state of the device is changed to 'removed' which matches the operation performed. (BZ#1434668)
- Earlier, it was possible to run multiple device remove operations in parallel on the same device. This led to race conditions and database inconsistencies. With this fix, an error is displayed if another device remove operation on the same device is already in progress. (BZ#1437798, 1449312)
Users of Heketi are advised to upgrade to these updated packages, which fix these bugs.
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:
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 - 1415750 - Heketi DB inconsistent state after heketi pod reboot when some operation in progress
- BZ - 1434668 - After a device is removed from heketi, status of the device reflects as 'failed', which is misleading.
- BZ - 1437798 - when remove device fails in the middle of migration, retrying device remove on the same device fails with error 'Id not found'
- BZ - 1449312 - [GSS] Id not found when removing a device
- BZ - 1485321 - [GSS] Can't remove missing node via heketi-cli
- BZ - 1516288 - [GSS] heketi doesn't remove old pods
- BZ - 1544735 - Gluster-block does not understand PVC's storage unit
- BZ - 1546949 - Remove warning about rebalance being an experimental feature from heketi-log
- BZ - 1547917 - [RFE] Rebase heketi to Heketi v6 upstream source
- BZ - 1548322 - panic: Heketi terminated while performing one or more operations. Server will not start as long as pending operations are present in the db.
- BZ - 1552733 - [Regression]: block device creation request of size greater than blockhosting volume's size should fail with proper error message
- BZ - 1553038 - Failed to start heketi service on CRS setup (heketi outside openshift)
CVEs
(none)
References
(none)
Red Hat Enterprise Linux Server 7
SRPM | |
---|---|
heketi-6.0.0-7.1.el7rhgs.src.rpm | SHA-256: cd8afd148d4fd68fdbae220a5abf190ba42a005e46a6158b6b49a0bb07e36ea4 |
x86_64 | |
heketi-client-6.0.0-7.1.el7rhgs.x86_64.rpm | SHA-256: 69bb73f0eecf38408f01dda500ed6e762bd90494edfabb2a617682fbc01a30a9 |
Red Hat Gluster Storage Server for On-premise 3 for RHEL 7
SRPM | |
---|---|
heketi-6.0.0-7.1.el7rhgs.src.rpm | SHA-256: cd8afd148d4fd68fdbae220a5abf190ba42a005e46a6158b6b49a0bb07e36ea4 |
x86_64 | |
heketi-6.0.0-7.1.el7rhgs.x86_64.rpm | SHA-256: fbd17094f80508f52fa89c4c1f761cca8129b206a482ba6fc24d9c2f893bc107 |
heketi-client-6.0.0-7.1.el7rhgs.x86_64.rpm | SHA-256: 69bb73f0eecf38408f01dda500ed6e762bd90494edfabb2a617682fbc01a30a9 |
python-heketi-6.0.0-7.1.el7rhgs.x86_64.rpm | SHA-256: 87d3b409d2eaecfc135b9ff24450fabf1d666e093e6adb2604e4cbd5d5b331fb |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.