Bug 1352562

Summary: heketi-cli node / cluster delete fails with conflict error
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Bhaskarakiran <byarlaga>
Component: heketiAssignee: Luis Pabón <lpabon>
Status: CLOSED NOTABUG QA Contact: Jonathan Holloway <jholloway>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: madam, mliyazud, mzywusko, rcyriac
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-05 09:55:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bhaskarakiran 2016-07-04 10:45:30 UTC 
Description of problem:
=======================
I tried to create a topology of 4 nodes for second TSP and while adding the second node it failed with "Transport endpoint not connected". I tried deleting the nodes and cluster, it fails with conflict error. No way to get out of this ??

Here is the output :

[root@dhcp43-179 ~]# export HEKETI_CLI_SERVER=http://deploy-heketi-aplo.cloudapps.myaplo.com
[root@dhcp43-179 ~]# heketi-cli topology load --json=topology.json
Creating cluster ... ID: a78c0d7301e706daef060f9e3ab5231e
	Creating node dhcp42-43.lab.eng.blr.redhat.com ... ID: a61d1473fd068db7dd62ceb1e3a14b5c
		Adding device /dev/vdb ... OK
	Creating node dhcp43-45.lab.eng.blr.redhat.com ... Error: Unable to execute command on glusterfs-dc-dhcp42-43.lab.eng.blr.redhat.com-1-aamxd: peer probe: failed: Probe returned with Transport endpoint is not connected


[root@dhcp43-179 ~]# heketi-cli topology load --json=topology.json
Creating cluster ... ID: c58a4a7c4089229bf47188bd4c00d09c
	Creating node dhcp42-43.lab.eng.blr.redhat.com ... Error: Hostname dhcp42-43.lab.eng.blr.redhat.com already used by node with id a61d1473fd068db7dd62ceb1e3a14b5c


[root@dhcp43-179 ~]# heketi-cli node delete a61d1473fd068db7dd62ceb1e3a14b5c
Error: Conflict

[root@dhcp43-179 ~]# heketi-cli cluster delete a78c0d7301e706daef060f9e3ab5231e
Error: Conflict


[root@dhcp43-179 ~]# heketi-cli cluster list 
Clusters:
a78c0d7301e706daef060f9e3ab5231e
d561e0cb2cc034250cf528b2012c6843
[root@dhcp43-179 ~]# heketi-cli cluster info a78c0d7301e706daef060f9e3ab5231e
Cluster id: a78c0d7301e706daef060f9e3ab5231e
Nodes:
a61d1473fd068db7dd62ceb1e3a14b5c
Volumes:
[root@dhcp43-179 ~]# 


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Bhaskarakiran 2016-07-05 09:55:17 UTC 
Closing this bug as it was a problem with syntax.