-
Notifications
You must be signed in to change notification settings - Fork 479
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
Wild VM monitoring should not return datastores that contain only swap files #1699
Milestone
Comments
Quick workaround (in virtual_machine.rb, vcenter vmm driver)
|
Correct solution would be to add as datastore the one that holds the VM disk that boots the VM |
tinova
pushed a commit
that referenced
this issue
Apr 24, 2018
Added workaround ,postponing for 5.8 |
sergiojvg
added a commit
that referenced
this issue
Feb 5, 2019
sergiojvg
added a commit
that referenced
this issue
Feb 5, 2019
tinova
pushed a commit
that referenced
this issue
Feb 6, 2019
Semedi
pushed a commit
to Semedi/one
that referenced
this issue
Feb 8, 2019
tinova
pushed a commit
that referenced
this issue
Feb 8, 2019
rsmontero
pushed a commit
that referenced
this issue
Jan 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Version of OpenNebula
Component
Description
If a vCenter VM features a swap file on a datastore, it is returned as the VCENTER_DS_REF (the first element of the datastore array is returned
Expected Behavior
Datastore with non swap disk only should be returned
Actual Behavior
How to reproduce
Create VM in vCenter with one disk in one datastore (ds1), and swap disk in another (ds2). Import only ds1 in OpenNebula. Try to import the Wild VM in OpenNebula
The text was updated successfully, but these errors were encountered: