RHEA-2018:2686 - Product Enhancement Advisory

Topic

Updated heketi packages that fixes several bugs and adds various enhancements are now available for Red Hat OpenShift Container Storage 3.10.

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:

• With this update, Heketi can now create and manage arbitrated volumes. Arbitrated volumes can reduce overall space consumption in the cluster's storage and reduce total transferred data by creating specialized arbiter bricks. (BZ#1459628)
• With this update, heketi offers a metrics REST endpoint from which information about heketi's topology can be retrieved in text-based exposition format consumed by Prometheus. (BZ#1550919)
• Earlier, all block hosting volumes were created only with group gluster-block option set on the Gluster volume. With this update, this feature enables an administrator to define options while creating block hosting volumes by setting block_hosting_volume_options in heketi.json OR by setting environment variable HEKETI_BLOCK_HOSTING_VOLUME_OPTIONS. However, Red Hat recommends not removing the group gluster-block option, but additional options can be added to this option. For example, to make block hosting volumes be of arbiter type, set the option "group gluster-block, user.heketi.arbiter' to true. (BZ#1591624)

These updated heketi packages include numerous bug fixes. Space precludes documenting all of these changes in this advisory. Users are directed to the Red Hat OpenShift Container Storage 3.10 Release Notes for information on the most significant of these changes:

https://access.redhat.com/site/documentation/en-us/red_hat_openshift_container_storage/3.10/html/3.10_release_notes/

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 - 1428654 - Need a better error message when a cluster id with no bricks is provided
• BZ - 1432340 - heketi-cli doesn't output the reason of error
• BZ - 1433614 - cns-deploy fails in case there are "dos" partition signature on devices dedicated for bricks in topology file
• BZ - 1459233 - volume creation fails with insufficient free space error although there is enough free space available
• BZ - 1534850 - blockvolume creation fails for size greater than 1024 GiB
• BZ - 1534953 - Heketi device deletion fails
• BZ - 1541323 - [GSS] Glusterfs pvc bound fail with error creating volume Token used before issued
• BZ - 1548157 - [GSS] heketi db keeps trying to remove thin pool which is already removed
• BZ - 1554796 - [F-QE] heketi-cli node remove command returns Error: Token used before issued
• BZ - 1561680 - [GSS] LVM archives on gluster pod fill up root directory.
• BZ - 1565977 - [stability] error in creating 100gb of arbiter volume from heketi-cli
• BZ - 1566398 - Heketi is not doing rebalance after expanding volume
• BZ - 1568251 - An error message 'invalid log level' is seen in heketi log during heketi startup
• BZ - 1569306 - Standalone heketi unable to rebalance automatically and use the expanded volume size and new bricks
• BZ - 1569486 - need example for creating arbiter volume when we do "heketi-cli volume create --help"
• BZ - 1572561 - Heketi is Failed to allocate new volume even though we have space for arbiter, when one brick is supported and all other bricks are disabled.
• BZ - 1572661 - heketi is not showing actual used and free size of devices
• BZ - 1575899 - heketi is not creating volume everytime when all devices on node is arbiter:disabled and node is tagged as required itself
• BZ - 1575902 - heketi is not creating volume everytime when devices of first and second node is arbiter:disabled and devices of third node is arbiter:supported
• BZ - 1576094 - Using heketi-cli command, attempt to remove non-empty device from a terminated glusterfs pod(glusterfs label removed) fails, even with spare nodes available
• BZ - 1576311 - Volume creation is failing when out of three nodes two of them are taged as arbiter:disabled and one of them is taged as arbiter:supported
• BZ - 1578383 - Heketi is not creating volumes when we give very large average file size
• BZ - 1578658 - volume creation is failing when first node is tagged as arbiter:required
• BZ - 1581864 - CNS: failed to create volume: Token used before issued
• BZ - 1584123 - In a CNS setup, heketi-cli info on a block-hosting volume displays "Free Size" greater than its actual size
• BZ - 1584191 - Heketi topology info shows incorrect used space (not zero for devices which had no bricks)
• BZ - 1590143 - heketi device delete command hanged (as a vgremove command was waiting for an interactive prompt response)
• BZ - 1591437 - Heketi delete of orphaned volume returns error
• BZ - 1591624 - [RFE]: Provide an option to create block hosting volume as arbiter volumes
• BZ - 1592649 - free size in block hosting volume info isn't updated on expansion
• BZ - 1594716 - Block hosting volume is deleted from gluster but still lists from heketi
• BZ - 1595531 - With HA=3, in a 4 node cluster, for all block devices, a fixed set of 3 IPs/Gluster Pods are used as targets, with 1 pod staying unused
• BZ - 1595535 - In a 4 node CNS cluster, need to pass 3 hosts from heketi for gluster-block cli when HA is 3, instead of all 4 IPs
• BZ - 1596018 - Block device creation fails with sufficient space available on the devices
• BZ - 1596022 - heketi-cli topology info returns Error: Id not found
• BZ - 1596035 - On a 4 node setup heketi block volume creation fails when a node is powered off
• BZ - 1596626 - Heketi stops all further operations on finding "Id Not Found" errors due to db inconsistent state
• BZ - 1597349 - Heketi volume deletion fails with error 'Volume does not exist' but heketi lists info of the same volume
• BZ - 1600160 - scalability issue with gluster file on OCP
• BZ - 1601316 - Heketi volume clean up fails while creating and deleting pvs. Mismatch in heketi topology and heketi volume list
• BZ - 1601341 - On a 4 node setup heketi blockvolume creation with HA=3 fails when one node is powered off
• BZ - 1601904 - Creation of file PVC is very slow when scaled up to more than 200
• BZ - 1601907 - [GSS] Free space is not being updated in heketi
• BZ - 1607821 - heketi is creating separate block hosting volume for every block device request
• BZ - 1612049 - Once BZ#1584123 is hit in older heketi-build-6.0.0.7-4, block volume creations failed in latest builds with heketi panic
• BZ - 1612058 - Arbiter brick can contain less files than expected when we specify average file size explicitly
• BZ - 1612782 - creation of block volume is failing, but device storage is getting used
• BZ - 1612784 - after node delete from heketi, mount point,backup-volfile-servers in volumes contains removed node IP
• BZ - 1612786 - Newly created block volume info showing deleted node IP
• BZ - 1613260 - CNS: heketi pod not inready state - Liveness probe failed
• BZ - 1619017 - mismatch in number of block devices between heketi and gluster
• BZ - 1619515 - With Reserved size=2GB, Block PVC count mismatch between heketi and gluster & USED space greater than available space of block hosting vol
• BZ - 1622645 - Block app pods unable to re-mount block pvcs once BHVs have less space - I/O error
• BZ - 1624738 - heketi-cli volume info of Block-hosting volumes lists extra block device IDs which are NOT present

CVEs

(none)

References

(none)