Bug 1717411 - improve engine logging when migration fail
Summary: improve engine logging when migration fail
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.4.6
: 4.4.6
Assignee: Shmuel Melamud
QA Contact: Qin Yuan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-05 12:31 UTC by Marian Jankular
Modified: 2024-10-01 16:16 UTC (History)
6 users (show)

Fixed In Version: vdsm-4.40.60.5, ovirt-engine-4.4.6.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-01 13:22:09 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:2179 0 None None None 2021-06-01 13:23:11 UTC
oVirt gerrit 113820 0 master MERGED virt: Add error code for VIR_ERR_OPERATION_FAILED 2021-04-21 16:51:33 UTC
oVirt gerrit 114231 0 master MERGED core: Return migration error message from MigrateStatusVDSCommand 2021-04-13 09:00:47 UTC

Description Marian Jankular 2019-06-05 12:31:33 UTC
Description of problem:
improve engine logging when migration fail

Version-Release number of selected component (if applicable):
ovirt-engine-4.3.3.7-0.1.el7.noarch

How reproducible:
everytime

Steps to Reproduce:
1. create vm with name vmA on hostA
2. rename the vmA to vmA-1 while vm is running
3. create vm with name on vmA on hostB
4. try to migrate vmA from hostB to hostA

Actual results:
migration will fail with error:
"Failed Migrating VM vmA to Host hostA."

Expected results:
engine will notify user that there is already running vm with the same name on the hostA

Additional info:
there is already another rfe open for customer case - https://bugzilla.redhat.com/show_bug.cgi?id=1717399

Comment 1 Michal Skrivanek 2019-06-06 07:40:27 UTC
there is an indication that the name has been changed in the UI. Yes, operations will fail when the old name collide. I think a failure is good enough
we should include the libvit message as an additional detail though, here it would be: 'domain 'XXX' already exists with uuid 0848830e-1939-4add-bafe-a13324cc1169'

Comment 2 Daniel Gur 2019-08-28 13:11:54 UTC
sync2jira

Comment 3 Daniel Gur 2019-08-28 13:16:06 UTC
sync2jira

Comment 5 Lukas Svaty 2019-10-24 09:05:53 UTC
Again this bug was missing assignee. Moving needinfo.

Comment 8 Qin Yuan 2021-04-23 14:02:12 UTC
Verified with:
ovirt-engine-4.4.6.5-0.17.el8ev.noarch
vdsm-4.40.60.5-1.el8ev.x86_64

Steps:
1. Create vm with name vmA on hostA(host name is host_mixed_1 in test env)
2. Rename the vmA to vmA-1 while vm is running
3. Create vm with name vmA on hostB(host name is host_mixed_2 in test env)
4. Try to migrate vmA from hostB to hostA

Results:
There is migration failed message on engine:

2021-04-23 16:33:30,225+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-15689) [75ec3ed5] EVENT_ID: VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed due to an Error: domain 'vmA' already exists with uuid 634df1ca-2793-4852-a4da-f2a758280a97 (VM: vmA, Source: host_mixed_2, Destination: host_mixed_1).

Comment 12 errata-xmlrpc 2021-06-01 13:22:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: RHV Manager security update (ovirt-engine) [ovirt-4.4.6]), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:2179


Note You need to log in before you can comment on or make changes to this bug.