importnat to note is the VM is paused due to EIO, which should indeed be blocked. However that NPE is not nice… Also the current code check for paused state (introduced in 9e7a6163034152ecf9a846c151c7dc95cfcb0e62 by rgolan) is not correct as the user-paused VMs should be able to migrate, only when the reason is EIO we should block
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=4c2bf2c84c38da296132060c6da0a1b90c67f249
Verified on is35, checked that nullPointerException not appear under engine.log
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=1055ffaef68b4f5d729a8c764384597f6f428bae
Checked on av9 Scenarion: Run Once vm with "Start in pause mode" enabled, wait until vm state is paused, and migrate it, first migration works fine, but if you migrate it second time it failed, because that: <status> <state>paused</state> <detail>none</detail> </status> detail none, so from you patch it will no migrate again, so you or need to save reason why vm paused or change if statement and add possibility to migrate paused vm when <detail>none</detail>
well the code change is still not entirely correct. The only reason when we should not migrate is EIO, all other reasons including other errors, like ENOSPACE are ok Though we shouldn't "lose" the reason after migration anyway
Verified on rhevm-3.5.0-0.4.master.el6_5.noarch Migrate paused vm three times from host to host
Description of original problem: Customer has stated that when he tries to migrate a VM that is paused, it fails and he notices a NullPointerException in the logs
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, 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://rhn.redhat.com/errata/RHSA-2015-0158.html
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days