You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.
Currently, GC removed orphan service and orphan internal volume. It will cause some issue.
For example: two ESX shared 1 datastore, one each ESX, we have a swarm cluster running. When the first swarm cluster create a volume "aaa", an internal volume "_vf_aaa" will be created on the shared datastore. Then for the second swarm cluster, only internal volume "_vf_aaa" is visible, and it think "_vf_aaa" is an orphan volume and try to delete volume "aaa", which is wrong.
So we should remove the code to cleanup orphan internal volume.
The text was updated successfully, but these errors were encountered:
Currently, GC removed orphan service and orphan internal volume. It will cause some issue.
For example: two ESX shared 1 datastore, one each ESX, we have a swarm cluster running. When the first swarm cluster create a volume "aaa", an internal volume "_vf_aaa" will be created on the shared datastore. Then for the second swarm cluster, only internal volume "_vf_aaa" is visible, and it think "_vf_aaa" is an orphan volume and try to delete volume "aaa", which is wrong.
So we should remove the code to cleanup orphan internal volume.
The text was updated successfully, but these errors were encountered: