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

vm migration between vCenter clusters warning. #1820

Closed
2 of 26 tasks
Semedi opened this issue Mar 5, 2018 · 1 comment
Closed
2 of 26 tasks

vm migration between vCenter clusters warning. #1820

Semedi opened this issue Mar 5, 2018 · 1 comment
Assignees
@joseangelgm
Labels
Category: Sunstone Category: vCenter Status: Accepted Type: Bug

Comments

@Semedi
Copy link
Contributor

Semedi commented Mar 5, 2018 •
edited
Loading

Bug Report

Version of OpenNebula

  • 5.2.2
  • 5.4.0
  • 5.4.1
  • 5.4.2
  • 5.4.3
  • 5.4.4
  • 5.4.5
  • 5.4.6
  • 5.4.7
  • Development build

Component

  • Authorization (LDAP, x509 certs...)
  • Command Line Interface (CLI)
  • Contextualization
  • Documentation
  • Federation and HA
  • Host, Clusters and Monitorization
  • KVM
  • Networking
  • Orchestration (OpenNebula Flow)
  • Packages
  • Scheduler
  • Storage & Images
  • Sunstone
  • Upgrades
  • User, Groups, VDCs and ACL
  • vCenter

Description

Migrate running (--live) machines from CLI works but you will not notice anything in case of vCenter failure (CLI behaviour).

This bug consist in:

  • Check through cli whenever the vCenter migration fail

    • Its the machine still usable?
    • Check vcenter_attributes (specially VCENTER_CCR_REF)

  • Display through stdout an error telling the user the reason of the failed migration (example: couldn't migrate due to incompatibility)

  • Check vm migration on sunstone.
    - normal migrate (poweroff)
    - live migration (running)

see if the feedback provided by sunstone is good enough (same as cli).

Expected Behavior

Proper messages when you fail to migrate the machine

Actual Behavior

CLI does not tell u anyhing about the failure.

How to reproduce

migrate a vm between clusters with any vCenter error.
@joseangelgm
Copy link
Contributor

Contained in #1837

rsmontero pushed a commit that referenced this issue Mar 3, 2022
@rsmontero
F #5753: Better live mem resize for KVM (#1820)
d787313 
(cherry picked from commit c6965c3)
feldsam pushed a commit to FELDSAM-INC/one that referenced this issue Nov 4, 2024
@feldsam
F OpenNebula#5753: Better live mem resize for KVM (OpenNebula#1820)
cfdc615 
(cherry picked from commit c6965c3)

# Conflicts:
#	src/fireedge/src/client/constants/vm.js
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joseangelgm joseangelgm

Labels
Category: Sunstone Category: vCenter Status: Accepted Type: Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Semedi @joseangelgm