Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

image store is in wrong directory if datastore already has directory with same name #3365

Open
emlin opened this issue Nov 29, 2016 · 6 comments
Labels
component/portlayer/storage kind/defect Behavior that is inconsistent with what's intended priority/p4

Comments

@emlin
Copy link
Contributor

emlin commented Nov 29, 2016

If the datastore already has one directory has same name with vch, but that directory does not have a vm, which can be a left over of previous vm.
vic-machine will create vch correctly with a changed vm folder, e.g. "test_1" with vch name "test". The kvstore is located in "test_1" folder correctly, but image files are still in "test" directory.

@emlin
Copy link
Contributor Author

emlin commented Nov 29, 2016

@hickeng @mhagen-vmware do we need to mention this in user doc?

@stuclem
Copy link
Contributor

stuclem commented Nov 29, 2016

@emlin I think that we probably should.

@mhagen-vmware mhagen-vmware added the impact/doc/note Requires creation of or changes to an official release note label Nov 30, 2016
@mdubya66 mdubya66 added this to the v0.9.0 milestone Dec 3, 2016
@npakrasi
Copy link
Contributor

npakrasi commented Dec 8, 2016

Added to 0.8 release notes:

  • Image store is in the wrong directory if the datastore already has a directory with the same name. #3365
    If the datastore already has a directory with the same name as the VCH, and the directory does not have a VM, vic-machine creates the VCH correctly names the folder a slightly different name. Example, folder "test_1" with vch named "test". The kvstore is located in "test_1" folder correctly, but image files are still in the "test" directory.

@stuclem
Copy link
Contributor

stuclem commented Dec 8, 2016

Moving this back to To Do because this is the engineering issue. Removing the kind/note tag because this is in the RNs now.

@stuclem stuclem removed the impact/doc/note Requires creation of or changes to an official release note label Dec 8, 2016
@emlin emlin added component/portlayer/storage priority/p4 kind/defect Behavior that is inconsistent with what's intended labels Jan 17, 2017
@mhagen-vmware mhagen-vmware modified the milestones: Sprint 1, v0.9.0 Jan 18, 2017
@corrieb
Copy link
Contributor

corrieb commented Jul 19, 2017

@emlin I believe we have other open issues to cover this problem. Please close if you think this is now stale.

@emlin
Copy link
Contributor Author

emlin commented Oct 30, 2017

@corrieb do you know which issue is same with this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/portlayer/storage kind/defect Behavior that is inconsistent with what's intended priority/p4
Projects
None yet
Development

No branches or pull requests

6 participants