Issue with reusing same disk image with newer version

[amarts]

I have used a device which was used with a previous kadalu install (both used for testing), and when I try to use it again get below error:

[2020-01-13 09:36:06.149709] E [MSGID: 113063] [posix-common.c:663:posix_init] 0-storage-pool-1-posix: mismatching volume-id (1e67ddba-35e8-11ea-945f-0242ac110004) received. already is a part of volume 06be7d4a-31ec-11ea-9ed3-0242ac110004 
[2020-01-13 09:36:06.149789] E [MSGID: 101019] [xlator.c:626:xlator_init] 0-storage-pool-1-posix: Initialization of volume 'storage-pool-1-posix' failed, review your volfile again
[2020-01-13 09:36:06.149801] E [MSGID: 101066] [graph.c:361:glusterfs_graph_init] 0-storage-pool-1-posix: initializing translator failed

We should have an understanding how to use the data which has different glusterfs volume before. This may be expected behavior, but took some time for me to resolve. At least it would be great to add a check like these in kubectl_kadalu scripts so, users using that would get best experience.

[amarts]

Thinking more about it, this may not be a good idea. If it was used by a different volume, it may mean there may be a pod using it. This may cause problems.

Closing.

[c-seeger]

for reference if others come accross this can be fixed see Recreation of storage-pool with existing Volume ID by adding volume_id from the error message to the creation yaml