Description of problem:
	
#heketi-cli node disable 513a2e3cd7d61df6d41259590ee31e9b

#heketi-cli node remove 513a2e3cd7d61df6d41259590ee31e9b

Current topology:


Node Id: 513a2e3cd7d61df6d41259590ee31e9b
	State: failed
	Cluster Id: 24b9bdc3348be97789ef658ce32d527f
	Zone: 1
	Management Hostname: 192.168.35.5
	Storage Hostname: 192.168.35.5
	Devices:
		Id:1b3e759d7dbaa9caf8cea834b0602d78   Name:/dev/vdd            State:failed    Size (GiB):499     Used (GiB):0       Free (GiB):499     
			Bricks:
		Id:7a60c1ed433a646fbdcb3d7760810a20   Name:/dev/vdf            State:failed    Size (GiB):499     Used (GiB):0       Free (GiB):499     
			Bricks:
		Id:ec128143868cc926ba14c44ad266478f   Name:/dev/vde            State:failed    Size (GiB):499     Used (GiB):0       Free (GiB):499     
			Bricks:


# heketi-cli node enable 513a2e3cd7d61df6d41259590ee31e9b
Error: Cannot move a failed/removed node to online state
^^
If above is expected, 

# heketi-cli node add --zone=1 --cluster=24b9bdc3348be97789ef658ce32d527f  --management-host-name=192.168.35.5 --storage-host-name=192.168.35.5
Error: Hostname 192.168.35.5 already used by node with id 513a2e3cd7d61df6d41259590ee31e9b


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: