Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1436397

Summary:	Migration failed while Host is in 'preparing for maintenance' state - ...Destination: <UNKNOWN>
Product:	[oVirt] ovirt-engine	Reporter:	Jiri Belka <jbelka>
Component:	General	Assignee:	Sharon Gratch <sgratch>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Israel Pinto <ipinto>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.1.1.5	CC:	amureini, bugs, laravot, michal.skrivanek, mperina, stirabos, tjelinek
Target Milestone:	ovirt-4.1.3	Flags:	rule-engine: ovirt-4.1? tjelinek: planning_ack? rule-engine: devel_ack+ rule-engine: testing_ack+
Target Release:	4.1.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-06 13:14:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiri Belka 2017-03-27 20:33:17 UTC

Description of problem:

I can't migrate long-time running 3.5 VMs in 4.0 cluster in 4.1 engine between 4.1 vdsm hosts. Engine surprisingly reports that a host is in preparing to maintenance, it is - i clicked 'Maintenance' and expected the engine to migrate VMs for me.

(this is strange issue, in fact destination host got somehow mysteriously 'localhost.localdomain' fqdn and it was preventing running the VMs there. but this BZ is about useless events - of course src host was in preparing to maintence... and why 'UNKNOWN'? there are odd things inside engine.)

2017-03-27 22:04:33,624+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-46) [89e83135-d1c7-44a9-be0b-c06ab581e982] EVENT_ID: VM_MIGRATION_FAILED_DURING_MOVE_TO_MAINTENANCE(140), Correlation ID: 27a45332, Job ID: 6db9118d-ca51-4ede-b501-7854c39063dc, Call Stack: null, Custom Event ID: -1, Message: Migration failed while Host is in 'preparing for maintenance' state.
Consider manual intervention: stopping/migrating Vms as Host's state will not
turn to maintenance while VMs are still running on it.(VM: STAYING_ALIVE-8, Source: dell-r210ii-13, Destination: <UNKNOWN>).

Version-Release number of selected component (if applicable):
rhevm-4.1.1.6-0.1.el7.noarch

How reproducible:
just happened

Steps to Reproduce:
1.
2.
3.

Actual results:
engine oddly informs about host in preparing in maintenance when src host was switching to maintenance and engine should have migrate the VMs; also there's odd 'UNKNOWN' in events.

Expected results:
show me usefull events

Additional info:

Comment 2 Martin Perina 2017-03-30 15:58:42 UTC

Tomasi, could you please take a look as the main issue here is around migrations?

Comment 3 Tomas Jelinek 2017-03-31 06:38:39 UTC

While I understand that it is unpleasant if the warning messages are not informative enough, I don't think they should be blocking anything. 

Removing blocker flag and restoring severity from Jiri.

Comment 4 Tomas Jelinek 2017-03-31 07:04:14 UTC

The message itself is not wrong. It says:

"
Message: Migration failed  while Host is in 'preparing for maintenance' state.
  Consider manual intervention: stopping/migrating Vms as Host's state will not
  turn to maintenance while VMs are still running on it.(VM: STAYING_ALIVE-8, Source: dell-r210ii-13, Destination: <UNKNOWN>)
"

e.g. it informs you that this migration was done due to the fact that the host is in preparing for maintenance and that you should try to do some manual intervention because otherwise the host will not turn into maintenance.

The only problem here is with the <UNKNOWN> destination.

Comment 5 Sharon Gratch 2017-05-17 13:33:37 UTC

(In reply to Tomas Jelinek from comment #4)
> The only problem here is with the <UNKNOWN> destination.

The <UNKNOWN> destination appears in log for the following scenario:
if migration started due to changing the source host to MAINTENANCE, 
and after re-run migration on on all allowed hosts in cluster, the migration failed on all and no more hosts left to re-run on. In that case the destination vds is set to NULL and appears in log as UNKNOWN.

Comment 6 Israel Pinto 2017-06-21 14:49:49 UTC

Verify with:
Red Hat Virtualization Manager Version: 4.1.3.4-0.1.el7
Host/s:
OS Version:RHEL - 7.4 - 11.el7
Kernel Version:3.10.0 - 327.28.3.el7.x86_64
KVM Version:2.9.0 - 12.el7
LIBVIRT Version:libvirt-3.2.0-4.el7
VDSM Version:vdsm-4.19.19-1.el7ev
SPICE Version:0.12.8 - 2.el7

Steps:
ENV with 3 hosts:
1. Create VM in 3.5  
2. Upgrade the env till 4.1 while keeping the VM running, setting hosts to maintenance to between versions. 

Results:
PASS