Comment 9 for bug 1786346

Revision history for this message
Dan Smith (danms) wrote :

Just some further clarification:

- The few hacked up gate jobs we used to test this feature at merge time likely didn't notice the race because the migrations finished before the potential timeout and/or are on systems so loaded that the neutron event came late enough for us to win the race repeatedly.

- The fact that we raise but don't actually cancel the ongoing live migration task means that we log error, report error on the migration object, but the actual migration thread is left running to complete at extremely low speeds for a very long time.