Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

vFile: when failed to create the internal vDVS volume, should not create a local volume instead #1903

Closed
luomiao opened this issue Sep 25, 2017 · 2 comments

Comments

@luomiao
Copy link
Contributor

luomiao commented Sep 25, 2017

In current version of vFile plugin, when there is an error creating the internal vDVS volume, such as, the maximum supported number of vDVS volumes is reached, vFile plugin will go ahead create a local volume instead.
This is not an expected action since users are expecting the volumes from required internal plugin only. A local volume instead of vDVS volume can result in unexpected errors or results with user application.
vFile plugin should be updated to return error only without creating the local volume.

@shuklanirdesh82
Copy link
Contributor

correctness issue so adding mustfix kw.

@luomiao
Copy link
Contributor Author

luomiao commented Oct 17, 2017

This is not valid. The local volumes are created when "docker run" with an non-existing volume. This is an expected action.

@luomiao luomiao closed this as completed Oct 17, 2017
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Projects
None yet
Development

No branches or pull requests

2 participants