Bug 49909 - The uvmm-migrate command should show, if a machine is not successfully migrated
The uvmm-migrate command should show, if a machine is not successfully migrated
Status: CLOSED WONTFIX
Product: UCS
Classification: Unclassified
Component: Virtualization - UVMM
UCS 4.4
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-07-23 11:12 CEST by Christina Scheinig
Modified: 2023-06-28 10:46 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019071921000342
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christina Scheinig univentionstaff 2019-07-23 11:12:51 CEST
The customer would be very pleased, if the command "uvmm migrate" would show, if a machine could not be successfully migrated. Also a continuous progress bar like it is used in "virsh migrate" would be very helpful.

The reason for this wish is that the machines got stuck twice or were not started at all for migration. However, this was not visible or transparent.

While the migration was running, (the customer uses a script to migrate all machines of one host at once, one machine after an other) there was a traceback shown in /var/log/univention/virtual-machine-manager-daemon.log which seems to have interrupted the migration process.

2019-07-19 14:12:12,372 - uvmmd.node - WARNING - Failed to query job status 197388e2-d0de-4fad-a04a-27bd49f2e076: Requested operation is not valid: domain is not running
2019-07-19 14:12:12,374 - uvmmd.node - WARNING - 'qemu://kvm05.schein.ig/system' broken? next check in 0:00:30.000. Domain not found: no domain with matching uuid '197388e2-d0de-4fad-a04a-27bd49f2e076' (slave43-183)
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/univention/uvmm/node.py", line 842, in update_autoreconnect
    self.update()
  File "/usr/lib/pymodules/python2.7/univention/uvmm/node.py", line 1128, in update
    domStat.update(dom)
  File "/usr/lib/pymodules/python2.7/univention/uvmm/node.py", line 377, in update
    self.update_expensive(domain)
  File "/usr/lib/pymodules/python2.7/univention/uvmm/node.py", line 383, in update_expensive
    cache_id = hash(dom.inactive_xml)
  File "/usr/lib/pymodules/python2.7/univention/uvmm/node.py", line 260, in inactive_xml
    self._inactive_xml = self.domain.XMLDesc(libvirt.VIR_DOMAIN_XML_SECURE | libvirt.VIR_DOMAIN_XML_INACTIVE)
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 492, in XMLDesc
    if ret is None: raise libvirtError ('virDomainGetXMLDesc() failed', dom=self)
libvirtError: Domain not found: no domain with matching uuid '197388e2-d0de-4fad-a04a-27bd49f2e076' (slave43-183) 
2019-07-19 14:12:42,404 - uvmmd.node - INFO - Connected to 'qemu://kvm05.schein.ig/system'
Comment 1 Philipp Hahn univentionstaff 2019-07-23 12:47:23 CEST
/usr/sbin/uvmm is an internal command and is neither documented in the main UCS manual nor in the extended manual. As such it is not supported.

There already is a feature request for displaying migration progress: Bug #48858

*** This bug has been marked as a duplicate of bug 48858 ***
Comment 2 Oliver Bohlen 2019-07-24 16:31:13 CEST
As in Ticket#2019072421000556 described uvmm is supportet by univention.
Please reopen and fix the issue (python traceback).
Would be great if the feature is being added too.
Comment 3 Philipp Hahn univentionstaff 2023-06-28 10:44:08 CEST
UVMM and virtualization with UCS is deprecated and will no longer be developed in UCS 4.4; they have already been removed from UCS 5.0.