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

Error when import two VMs with the same MOREF in OpenNebula from different vCenters #5689

Closed
7 of 10 tasks
OpenNebulaSupport opened this issue Jan 12, 2022 · 2 comments
Closed
7 of 10 tasks

Error when import two VMs with the same MOREF in OpenNebula from different vCenters #5689

OpenNebulaSupport opened this issue Jan 12, 2022 · 2 comments
Assignees
@carloshm91
Labels
Category: vCenter Priority: High Sponsored Type: Bug
Milestone
Release 6.2.2

Comments

@OpenNebulaSupport
Copy link
Collaborator

OpenNebulaSupport commented Jan 12, 2022 •
edited by tinova
Loading

Description
Within a vCenter there is no duplicate MOREF for virtual machines. But when you have two vCenter instances, OpenNebula doesn't cover this use case and sees them as Zombie

To Reproduce

  • Import two clusters from different vCenter instances.
  • Try importing two wild with the same MOREF.
  • The second wild you will see it as a zombie.

Expected behavior

Both wild should imported correctly

Details

  • Affected Component: VMM
  • Hypervisor: vCenter
  • Version: master

Pending Actions

  • Document change of deploy id in compatibility guide
  • Add a note in the upgrade documentation to wait for several monitoring cycles
  • Review doc for reference to deploy id use, change for moref + vcenter_uuid

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation [Need a note in compatiblity]
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches
@tinova tinova added this to the Release 6.2.1 milestone Jan 12, 2022
@paczerny
Copy link
Member

Duplicate of #4720

@paczerny paczerny marked this as a duplicate of #4720 Jan 13, 2022
@tinova tinova modified the milestones: Release 6.2.1, Release 6.4 Feb 8, 2022
@tinova
Copy link
Member

tinova commented Feb 15, 2022

master commit 1fc5b5a

@tinova tinova mentioned this issue Feb 15, 2022
Closed
7 tasks
@tinova tinova modified the milestones: Release 6.4, Release 6.2.2 Feb 21, 2022
rsmontero pushed a commit that referenced this issue Feb 25, 2022
@carloshm91 @tinova
B #5689: allow import wilds with same moref (#1747)
1fc5b5a 
Co-authored-by: Tino Vázquez <cvazquez@opennebula.io>
rsmontero pushed a commit that referenced this issue Feb 25, 2022
@carloshm91
B #5689: fix monitoring issue with POWEROFF state (#1795)
78a6985
rsmontero pushed a commit that referenced this issue Feb 25, 2022
B #5689: fix minor issue with vCenter monitor (#1806)
472893e
@tinova tinova closed this as completed Mar 18, 2022
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: High Sponsored Type: Bug
Projects
None yet
Milestone
Release 6.2.2
Development

No branches or pull requests
4 participants
@tinova @paczerny @OpenNebulaSupport @carloshm91