Previously, a condition existed within Heketi where an error running a command on a node failed and was being cleaned up for a volume expand operation that would lead to incorrect used/free space on the devices related to that volume. With this release, this issue has been corrected and Heketi now correctly updates the free space even when the `expand` operation fails.
Yes, we still get this bug as well and want to avoid regularly having to restart tcmu-runner so that free space in heketi and gluster is congruent. Any updates on when this will be resolved?
We got the instructions regarding tcmu-runner restart in support case
https://access.redhat.com/support/cases/#/case/02504998
However, the why is still not clear to us and the error keeps repeating.
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