Skip to content
This repository has been archived by the owner on Jul 6, 2023. It is now read-only.

after node delete from heketi, backup-volfile-servers in volumes contains removed node IP #1274

Closed
Madhu-1 opened this issue Jul 18, 2018 · 0 comments · Fixed by #1294
Closed
Labels
Milestone

Comments

@Madhu-1
Copy link
Contributor

Madhu-1 commented Jul 18, 2018

Kind of issue

Bug

Observed behavior

after node delete from heketi, the volumes present in the heketi is having backup-volfile-servers as removed node IP

Expected/desired behavior

once the node is deleted from heketi, heketi should refresh volume info as it should not point out to deleted node IP

Details on how to reproduce (minimal and precise)

1)load topology in heketi (it has 3 nodes)
2)create 4 volumes
3)add a new node to heketi
4)disable one old node in heketi
5)remove the same node
6)remove devices
7)delete the node from heketi
8)check volume info on old volumes

Information about the environment:

  • Heketi version used (e.g. v6.0.0 or master):
  • Operating system used:
  • Heketi compiled from sources, as a package (rpm/deb), or container:
  • If container, which container image:
  • Using kubernetes, openshift, or direct install:
  • If kubernetes/openshift, is gluster running inside kubernetes/openshift or outside:
  • If kubernetes/openshift, how was it deployed (gk-deploy, openshift-ansible, other, custom):

Other useful information

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
2 participants