Description of problem:
On running device delete after performing a successful device removal, the device deletion hangs.
[root@dhcp46-180 ~]# heketi-cli device info 063a2e602443dba541f56e14cb505e4f
Device Id: 063a2e602443dba541f56e14cb505e4f
Size (GiB): 19
Used (GiB): 0
Free (GiB): 19
[root@dhcp46-180 ~]# heketi-cli device delete 063a2e602443dba541f56e14cb505e4f
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Device deletion hangs
Device Deletion should be successful
(In reply to Rachael from comment #0)
> Description of problem:
> On running device delete after performing a successful device removal, the
> device deletion hangs.
> [root@dhcp46-180 ~]# heketi-cli device info 063a2e602443dba541f56e14cb505e4f
> Device Id: 063a2e602443dba541f56e14cb505e4f
> Name: /dev/sdd
> State: failed
> Size (GiB): 19
> Used (GiB): 0
> Free (GiB): 19
> [root@dhcp46-180 ~]# heketi-cli device delete
> Version-Release number of selected component (if applicable):
> How reproducible:
> Steps to Reproduce:
> Actual results:
> Device deletion hangs
> Expected results:
> Device Deletion should be successful
> Additional info:
Heketi logs: http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1534953/
Hi Rachael, did this happen once, or is it easy reproducible?
The logs do not contain much detail, it shows the job being stuck, but no reason why. If it is possible to reproduce, we may be able to debug a little more. I do not expect we have time to troubleshoot this soon, moving it to cns-3.11 for now. If you expect this problem to (almost) always to happen, we might be able to increase the priority.
Hi Niels, this issue was hit more than once, in this version: heketi-5.0.0-19.el7rhgs.x86_64, but it is not easily reproducible. However, I have not seen this behaviour in the latest version of Heketi.
Thanks Rachael! In that case it is good possible that the improved database operation framework within Heketi prevents this problem from happening.
Re-adding to cns-3.10.0 as the fix is most likely included already. This will be a QE verification effort.
As Niels pointed out in comment 5, improved database operation in heketi 6 and above prevents this from happening. Moving it to ON_QA
Verification of this bug is blocked due to https://bugzilla.redhat.com/show_bug.cgi?id=1584639
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.