Bug 1562485 - device remove operation is hung when the source device is removed from backend
Summary: device remove operation is hung when the source device is removed from backend
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: heketi
Version: cns-3.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: John Mulligan
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-31 04:57 UTC by krishnaram Karthick
Modified: 2019-04-24 15:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-24 15:21:47 UTC
Embargoed:


Attachments (Terms of Use)
heketi logs (503.76 KB, text/plain)
2018-03-31 05:01 UTC, krishnaram Karthick
no flags Details
heketi logs after device remove operation got completed (1.68 MB, text/plain)
2018-03-31 11:14 UTC, krishnaram Karthick
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1435613 0 unspecified CLOSED heketi remove device fails when the source disk being removed is down 2021-02-22 00:41:40 UTC

Internal Links: 1435613

Description krishnaram Karthick 2018-03-31 04:57:20 UTC
Description of problem:
device remove operation hangs on a device which is removed from backend (virtual disk deleted on VMware env).

Refer steps to reproduce for the work flow.

Last successful operation seems to have happened an hour back. But, post this operation, the logs doesn't show any further operation.

[kubeexec] DEBUG 2018/03/31 09:20:52 /src/github.com/heketi/heketi/executors/kubeexec/kubeexec.go:244: Host: dhcp46-51.lab.eng.blr.redhat.com Pod: glusterfs-storage-npvzx Command: gluster --mode=script volume re
place-brick vol_bbef9b1e33a3c7c36552f1af5cd011c1 10.70.46.51:/var/lib/heketi/mounts/vg_12825d714782ee6542f226e69cfaa4f2/brick_026672f0fb485d2fc82e56c9d50a050a/brick 10.70.46.51:/var/lib/heketi/mounts/vg_654fd8c2
36965e6eaf4995a199315a12/brick_c7da79afa99bb587c42d612d7c3cd78c/brick commit force
Result: volume replace-brick: success: replace-brick commit force operation successful
[heketi] INFO 2018/03/31 09:20:52 Deleting brick 026672f0fb485d2fc82e56c9d50a050a


Version-Release number of selected component (if applicable):
rpm -qa | grep 'heketi'
heketi-6.0.0-7.1.el7rhgs.x86_64
python-heketi-6.0.0-7.1.el7rhgs.x86_64
heketi-client-6.0.0-7.1.el7rhgs.x86_64


How reproducible:
1/1

Steps to Reproduce:
1. keep creating volumes in a loop
2. while the creation is in progress, remove a disk on which volume is being created. [I removed the virtual disk from VMware env]
3. volume creation will fail
4. now, try to remove the device[12825d714782ee6542f226e69cfaa4f2] from heketi using heketi-cli device remove

Actual results:
device remove command is hung for more than an hour with no operations being performed by heketi (based on the log entries)

Expected results:
device remove should succeed

Additional info:
heketi logs shall be attached

Comment 3 krishnaram Karthick 2018-03-31 05:01:57 UTC
Created attachment 1415357 [details]
heketi logs

Comment 6 krishnaram Karthick 2018-03-31 11:14:39 UTC
Created attachment 1415472 [details]
heketi logs after device remove operation got completed


Note You need to log in before you can comment on or make changes to this bug.