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.
1. Created a datastore cluster of two datastores - sharedVmfs-1 and sharedVmfs-0
2. Put sharedVmfs-1 in 'Maintenance Mode'
3. Then was able to create volume to the datastore - sharedVmfs-1
4. Successfully mounted the volume to a container and was also able to write data to it.
This should not be allowed. Volume creation should not succeed on datastore which is in maintenance mode as user may have put it in maintenance mode to perform some service on it or user may even decide to drop the datastore completely which is in maintenance mode.
ashahi1
changed the title
Volume creation succeeds on a datastore which in maintenance mode
Volume creation succeeds on a datastore which is in maintenance mode
Jul 27, 2017
@lipingxue I tried from VC but I am not able to create VM on a datastore which is in maintenance mode. That particular datastore is not listed among available datastore for vm creation. Datastore maintenance mode is a VC feature.
Also, there is no event generated in hostd logs when datastore is put in maintenance mode. So it looks like ESX side is unaware of datastore maintenance mode.
Dockvols folder on datatore which is in maintenance mode, does show created vmdk.
@ashahi1 Since esx is not aware of datastore in maintenance mode, and still can create vmdk on the datastore, no fix can be done. We should document it as known issue.
Steps:
This should not be allowed. Volume creation should not succeed on datastore which is in maintenance mode as user may have put it in maintenance mode to perform some service on it or user may even decide to drop the datastore completely which is in maintenance mode.
Logs have been attached at the end.
Steps and their output are as follows:
Logs:
docker-volume-vsphere.txt
vmdk_ops.txt
The text was updated successfully, but these errors were encountered: