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.

Sign up for GitHub

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

Jump to bottom

vCenter:snapshot+poweron=disk metadata is corrupted and you have snapshots #3844

Closed
crollorc opened this issue Oct 15, 2019 · 11 comments
Closed

vCenter:snapshot+poweron=disk metadata is corrupted and you have snapshots #3844

crollorc opened this issue Oct 15, 2019 · 11 comments
Assignees
@carloshm91
Labels
Category: vCenter Priority: Normal Status: Accepted Type: Bug
Milestone
Release 5.10.3

Comments

@crollorc
Copy link

I'm using OpenNebula 5.8.5 to provide console and power control to a vCenter cluster.

All VMs are imported from Wilds.

Once imported, I've found that I can take a VM snapshot (Snapshots->Take snapshot).

However, following this it is not possible to poweron the VM from within OpenNebula due to the following error:

Mon Oct 14 14:01:38 2019 [Z0][VMM][I]: Command execution failed (exit code: 255): /var/lib/one/remotes/vmm/vcenter/deploy '/var/lib/one/vms/71/deployment.1' 'vfcc1' 71 vfcc1
Mon Oct 14 14:01:38 2019 [Z0][VMM][E]: deploy: Deploy of VM 71 on vCenter cluster vfcc1 with /var/lib/one/vms/71/deployment.1 failed due to "disk metadata is corrupted and you have snapshots"on the attempt #1.
@tinova
Copy link
Member

tinova commented Oct 17, 2019

Is this happening on more VMs than VM 71?

@crollorc
Copy link
Author

It has happened on both VMs which I tested so far.

The same problem happens for snapshots taken from vCenter and from OpenNebula.

Are there any particular logs or information which might help?

@tinova
Copy link
Member

tinova commented Oct 17, 2019

Can you provide the "onevm show -x" of the VM in a gist?

@crollorc
Copy link
Author

Here you go: onevm show -x 72

@tinova
Copy link
Member

tinova commented Oct 18, 2019

Thanks a lot. We need to check now the .vmx of the VM, can you also provide that?

@crollorc
Copy link
Author

Here is the VMX: colm-ubuntu1.vmx

@tinova
Copy link
Member

tinova commented Oct 23, 2019

The "opennebula.disk.*" attribute is missing from the .vmx, this is what is triggering the error. Can you import a new Wild, and check if the .vmx file has these parameters?

@crollorc
Copy link
Author

I've imported a wild which was turned off and this resulted in the addition of the following attributes to the vmx file:

remotedisplay.vnc.enabled = "TRUE"
remotedisplay.vnc.port = "5974"
remotedisplay.vnc.ip = "0.0.0.0"

If I turn that VM on and off from OpenNebula and check the vmx, I see the addition of the following attributes:

opennebula.vm.running = "yes"
guestinfo.opennebula.context = "IyBDb250ZXh0IHZhcmlhYmxlcyBnZW5lcmF0ZWQgYnkgT3Blbk5lYnVsYQpE|0ASVNLX0lEPScyJwpFVEgwX0NPTlRFWFRfRk9SQ0VfSVBWND0nJwpFVEgwX0RO|0AUz0nJwpFVEgwX0VYVEVSTkFMPScnCkVUSDBfR0FURVdBWT0nJwpFVEgwX0dB|0AVEVXQVk2PScnCkVUSDBfSVA9JycKRVRIMF9JUDY9JycKRVRIMF9JUDZfUFJF|0ARklYX0xFTkdUSD0nJwpFVEgwX0lQNl9VTEE9JycKRVRIMF9NQUM9JzAwOjUw|0AOjU2Ojg0OjZlOmU4JwpFVEgwX01BU0s9JycKRVRIMF9NVFU9JycKRVRIMF9O|0ARVRXT1JLPScnCkVUSDBfU0VBUkNIX0RPTUFJTj0nJwpFVEgwX1ZMQU5fSUQ9|0AJycKRVRIMF9WUk9VVEVSX0lQPScnCkVUSDBfVlJPVVRFUl9JUDY9JycKRVRI|0AMF9WUk9VVEVSX01BTkFHRU1FTlQ9JycKTkVUV09SSz0nWUVTJwpTU0hfUFVC|0ATElDX0tFWT0nJwpUQVJHRVQ9J2hkYicK|0A"
uuid.location = "56 4d ee bd 81 d8 d2 6e-d3 8e df 20 9d d6 97 3b"

No sign of any opennebula.disk.* attributes.

@carloshm91 carloshm91 self-assigned this Nov 11, 2019
carloshm91 added a commit to carloshm91/one that referenced this issue Nov 11, 2019
@carloshm91
B OpenNebula#3844: first approach
bb5f2ca 
Signed-off-by: Carlos J. Herrera Matos <cherrera@opennebula.systems>
@carloshm91
Copy link
Contributor

We believe we have found the error in the code.
We will send you a patch as soon as we can so you can try.

carloshm91 added a commit to carloshm91/one that referenced this issue Nov 18, 2019
@carloshm91
B OpenNebula#3844: create function reference_devices
e73840d 
Signed-off-by: Carlos J. Herrera Matos <cherrera@opennebula.systems>
carloshm91 added a commit to carloshm91/one that referenced this issue Nov 18, 2019
@carloshm91
B OpenNebula#3844: improve small details
2c7a048 
Signed-off-by: Carlos J. Herrera Matos <cherrera@opennebula.systems>
carloshm91 added a commit to carloshm91/one that referenced this issue Nov 18, 2019
@carloshm91
B OpenNebula#3844: adding vm_id
28380c7 
Signed-off-by: Carlos J. Herrera Matos <cherrera@opennebula.systems>
tinova added a commit that referenced this issue Nov 18, 2019
@tinova
B #3844: Refactor to ease bugfix
accddef 
We need to tag disks from Wild VMs. This refactor eases the code
needed to tag Wild VMs for managed and unmanaged disks

Also, address bug in VM shutdown.
tinova added a commit that referenced this issue Nov 19, 2019
@tinova
B #3844: Fix unchanged variables
4dd2b9d 
Also, create correct host object for undeployed VMs on shutdown
carloshm91 added a commit to carloshm91/one that referenced this issue Nov 19, 2019
@carloshm91
B OpenNebula#3844: refactoring some functions
81e4959 
Signed-off-by: Carlos J. Herrera Matos <cherrera@opennebula.systems>
tinova pushed a commit that referenced this issue Nov 19, 2019
@carloshm91
B #3844: refactoring some functions (#3958)
e1a6bf5 
Signed-off-by: Carlos J. Herrera Matos <cherrera@opennebula.systems>
tinova added a commit that referenced this issue Nov 20, 2019
@tinova
Revert "B #3844: refactoring some functions (#3958)"
d4066bf 
This reverts commit e1a6bf5

Keeping changes to reboot and reset, unrelated to changes reverted
in virtual_machine.rb
carloshm91 added a commit to carloshm91/one that referenced this issue Nov 25, 2019
@carloshm91
B OpenNebula#3844: add references when import wild
dd067a1 
Signed-off-by: Carlos J. Herrera Matos <cherrera@opennebula.systems>
carloshm91 added a commit to carloshm91/one that referenced this issue Nov 25, 2019
@carloshm91
B OpenNebula#3844: add references when import wild
b1b30b0 
Signed-off-by: Carlos J. Herrera Matos <cherrera@opennebula.systems>
carloshm91 added a commit that referenced this issue Dec 18, 2019
@carloshm91
B #3844: add references when import wilds
4db65b5 
Signed-off-by: Carlos Herrera <cherrera@opennebula.systems>
tinova pushed a commit that referenced this issue Dec 18, 2019
@carloshm91
B #3844: Add references when import wilds (#4055)
6141ebb 
Signed-off-by: Carlos Herrera <cherrera@opennebula.systems>
tinova pushed a commit that referenced this issue Dec 18, 2019
@carloshm91 @tinova
B #3844: Add references when import wilds (#4055)
9ac5f03 
Signed-off-by: Carlos Herrera <cherrera@opennebula.systems>
(cherry picked from commit 6141ebb)
carloshm91 added a commit that referenced this issue Dec 30, 2019
@carloshm91
B #3844: second phase, sync when deploy
0230be7 
Signed-off-by: Carlos Herrera <cherrera@opennebula.systems>
carloshm91 added a commit that referenced this issue Jan 6, 2020
@carloshm91
B #3844: reconfigure when is needed
039070f 
Signed-off-by: Carlos Herrera <cherrera@opennebula.systems>
carloshm91 added a commit that referenced this issue Jan 8, 2020
@carloshm91
B #3844: refactoring
013e176 
Signed-off-by: Carlos Herrera <cherrera@opennebula.systems>
carloshm91 added a commit that referenced this issue Jan 8, 2020
@carloshm91
B #3844: add comments
6481ee4 
Signed-off-by: Carlos Herrera <cherrera@opennebula.systems>
carloshm91 added a commit that referenced this issue Jan 8, 2020
@carloshm91
B #3844: delete reference to funct temporarily
7cf4628 
Signed-off-by: Carlos Herrera <cherrera@opennebula.systems>
tinova pushed a commit that referenced this issue Jan 8, 2020
@carloshm91
B #3844: Refactor reference_all_function, sync when deploy (#4071)
26b4805 
Signed-off-by: Carlos Herrera <cherrera@opennebula.systems>
Co-authored-by: Tino Vázquez <cvazquez@opennebula.systems>
@tinova tinova modified the milestones: Release 5.12, Release 5.10.2 Feb 3, 2020
@tinova tinova modified the milestones: Release 5.10.2, Release 5.10.3 Feb 12, 2020
@tinova tinova closed this as completed Feb 24, 2020
@tinova tinova reopened this Feb 24, 2020
@tinova
Copy link
Member

tinova commented Feb 24, 2020

Check documentation

@carloshm91
Copy link
Contributor

[ONE]

[DOC]

[DEV]

@tinova tinova closed this as completed Feb 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@carloshm91 carloshm91

Labels
Category: vCenter Priority: Normal Status: Accepted Type: Bug
Projects
None yet
Milestone
Release 5.10.3
Development

No branches or pull requests
3 participants
@tinova @crollorc @carloshm91