Sunstone: spurious "server exception" during VM migrate

When I try to migrate the VM in Sunstone, I get the following error pop-up after clicking to the green “Migrate” button:

It appears there was a server exception. Please check server's log.

However, the VM in question gets migrated correctly and there is no error message in <vmid>.log nor in oned.log. The <vmid>.log file says:

Thu Apr 14 17:14:14 2016 [Z0][LCM][I]: New VM state is SAVE_MIGRATE
Thu Apr 14 17:14:15 2016 [Z0][VMM][I]: ExitCode: 0
Thu Apr 14 17:14:15 2016 [Z0][VMM][I]: Successfully execute virtualization driver operation: save.
Thu Apr 14 17:14:15 2016 [Z0][VMM][I]: ExitCode: 0
Thu Apr 14 17:14:15 2016 [Z0][VMM][I]: Successfully execute network driver operation: clean.
Thu Apr 14 17:14:15 2016 [Z0][LCM][I]: New VM state is PROLOG_MIGRATE
Thu Apr 14 17:14:17 2016 [Z0][LCM][I]: New VM state is BOOT
Thu Apr 14 17:14:17 2016 [Z0][VMM][I]: ExitCode: 0
Thu Apr 14 17:14:17 2016 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Thu Apr 14 17:14:17 2016 [Z0][VMM][I]: ExitCode: 0
Thu Apr 14 17:14:17 2016 [Z0][VMM][I]: Successfully execute virtualization driver operation: restore.
Thu Apr 14 17:14:18 2016 [Z0][VMM][I]: ExitCode: 0
Thu Apr 14 17:14:18 2016 [Z0][VMM][I]: Successfully execute network driver operation: post.
Thu Apr 14 17:14:18 2016 [Z0][LCM][I]: New VM state is RUNNING

Is the exception real? As far as I can see, the VM is migrated correctly. Where can I look for the details?

I see this in various other operations, for example VM undeploy, user quota set, etc. The red message about the “server exception” appears, but the operation itself is executed as expected.

FWIW, this is on ONe 4.14 (which I have upgraded to from 4.!2 I have been running before).

Hi,

It could be that the sunstone server crashes while processing the operation reply, after it completes successfully in the core.
Next time please take a look in /var/log/one/sunstone.log and /var/log/one/sunstone.error

The following line is added to /var/log/one/sunstone.log when I chown the image:

Thu Apr 21 13:15:45 2016 [I]: 127.0.0.1 - - [21/Apr/2016:13:15:45 +0200] “POST /image/58/action HTTP/1.1” 204 - 0.1248

Is code 204 OK?

And I don’t have /var/log/one/sunstone.error file - how do I enable it? “ls -lt /var/log/one” suggests that recently written files are only oned.log and sunstone.log.

I don’t know what happened, but I don’t see the exceptions for the operations mentioned above anymore. Maybe upgrade to 4.14 and flushing the browser cache did it. Interesting.