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

Wild VM monitoring should not return datastores that contain only swap files #1699

Closed
2 tasks
OpenNebulaSupport opened this issue Jan 30, 2018 · 3 comments
Closed
2 tasks

Comments

@OpenNebulaSupport
Copy link
Collaborator

Bug Report

Version of OpenNebula

  • Development build

Component

  • vCenter

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

@tinova
Copy link
Member

tinova commented Feb 6, 2018

Quick workaround (in virtual_machine.rb, vcenter vmm driver)

<         str << "VCENTER_DS_REF = \"#{@vm_info["datastore"].last._ref}\"\n"
---
>         str << "VCENTER_DS_REF = \"#{@vm_info["datastore"].first._ref}\"\n"

@tinova
Copy link
Member

tinova commented Feb 6, 2018

Correct solution would be to add as datastore the one that holds the VM disk that boots the VM

@tinova
Copy link
Member

tinova commented Apr 24, 2018

Added workaround ,postponing for 5.8

@tinova tinova modified the milestones: Release 5.6, Release 5.8 Apr 24, 2018
tinova pushed a commit that referenced this issue Feb 6, 2019
* B #1699: Do not return datastores containing only SWAP

* B #1699: Function, rescue block and comment

* Update vm_template.rb
Semedi pushed a commit to Semedi/one that referenced this issue Feb 8, 2019
@tinova tinova closed this as completed Feb 11, 2019
tinova pushed a commit that referenced this issue Feb 15, 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
Projects
None yet
Development

No branches or pull requests

3 participants