Description of problem: When a migration times out and gets cancelled a misleading message is reported. How reproducible: Always Steps to Reproduce: 1. Change migration_max_time_per_gib_mem in VDSM to a smaller value (5) 2. Start a migration 3. When it fails due to timeout you'll find the following message in the event log of the RHEVM Webadmin: > Migration failed due to Error: Migration not in progress (VM: a, Source: host1, Destination: host2). Actual results: The error messages says that the migration failed because it is not in progress. > Migration failed due to Error: Migration not in progress (VM: a, Source: host1, Destination: host2). Expected results: Migration failed due to Error: The migration timed out and has been cancelled. (VM: a, Source: host1, Destination: host2).
A bit more clarification: "When a migration times out and gets cancelled" Should be "When a migration gets cancelled because it timed out"
didn't make 3.5
we still didn't really figure out how to approach this
hopefully wont' happen so much once migration improvements are done in 4.0