Description of problem: This is a -ve case but interesting one. When I try to create a block it fails because I gave block node as google.com to which it says it couldn't create. But when I try to delete it also it fails. So it just stays there: [root@localhost ~]# gluster-block create r3/16 ha 1 192.168.122.143 1GiB IQN: - PORTAL(S): - ROLLBACK ON: 192.168.122.143 RESULT: FAIL [root@localhost ~]# gluster-block create r3/16 ha 1 google.com 1GiB BLOCK with name: '16' already EXIST RESULT:FAIL [root@localhost ~]# gluster-block create r3/17 ha 1 google.com 1GiB IQN: - PORTAL(S): - ROLLBACK ON: google.com RESULT: FAIL [root@localhost ~]# gluster-block delete r3/16 FAILED ON: 192.168.122.143 SUCCESSFUL ON: None RESULT: FAIL [root@localhost ~]# gluster-block delete r3/17 FAILED ON: google.com SUCCESSFUL ON: None RESULT: FAIL [root@localhost ~]# gluster-block info r3/16 NAME: 16 VOLUME: r3 GBID: 219c87f8-d7c1-41ca-a376-de7f173f76df SIZE: 1073741824 HA: 1 PASSWORD: BLOCK CONFIG NODE(S): [root@localhost ~]# Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
https://review.gluster.org/17462
Gluster-block create and delete works fine.In this particular case the create was failing due to invalid host. Now that issue is fixed and we are not having volume create failed. Also verified that delete is happening successfully. With multiple deletes we have vmcore issue but that is tracked in a separate bug. So marking this bug as Verified. gluster-block-0.2.1-1.el7rhgs.x86_64 tcmu-runner-1.2.0-4.el7rhgs.x86_64
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/RHEA-2017:2773