Vladimir Sementsov-Ogievskiy <vsement...@yandex-team.ru> wrote: > 1. Otherwise failed migration just drops guest-panicked state, which is > not good for management software. > > 2. We do keep different paused states like guest-panicked during > migration with help of global_state state. > > 3. We do restore running state on source when migration is cancelled or > failed. > > 4. "postmigrate" state is documented as "guest is paused following a > successful 'migrate'", so originally it's only for successful path > and we never documented current behavior. > > Let's restore paused states like guest-panicked in case of cancel or > fail too. Allow same transitions like for inmigrate state. > > This commit changes the behavior that was introduced by commit > 42da5550d6 "migration: set state to post-migrate on failure" and > provides a bit different fix on related > https://bugzilla.redhat.com/show_bug.cgi?id=1355683 > > Signed-off-by: Vladimir Sementsov-Ogievskiy <vsement...@yandex-team.ru>
Reviewed-by: Juan Quintela <quint...@redhat.com>
