Catch InstanceIsLocked exception on server actions

If the server is locked, server actions raise 409 error, and the error
message is like "Instance is in an invalid state for 'pause(action name)'". The
error message is inappropriate, two points:
1. the state is valid for pause
2. the message doesn't tell that the instance is locked

The patch fixes the problem, and will modify on v2 and v3.

Change-Id: I7e21037b9abca5a3fd0f64dd5621e88dcf1a3c21
Closes-Bug: #1256873
Fix lxc rootfs attached two devices in some action

During resizing/rebooting a lxc container, create_domain action
will be called and lxc rootfs will be attached to device again.
So before this action, We need to teardown the container to
make sure lxc_root_device is detached when container is destroyed.

Closes-bug: #1243083
Related-bug: #1208387

Change-Id: Idd1862c7f212dc253b6273b07b020c86a94e658e
Ensure instance action event list in order

For two events also most happening at the same time, e.g. schedule and
run_instance, instance-action may fail to do the correct sorting because
the "create_at" column in db has the same value.

This change fixes this issue by sorting in "create_at" first, and then
in database generated "id" column, both in descending order.

Closes-bug: 1254764

Change-Id: I245a577ef2821fa7f3316bb8a21b7e6370498dd0
VMware: update test file names

The tests files names all had prefix vmwareapi. This is no longer
needed as the test files are now under the vmwareapi directory.

The patch also fixed the permission for the file test_vm_util.py.

Change-Id: I87955a0a4d4d2b2c1dd55203658707ce7c6038f0
Merge "Ensure instance action event list in order"
Merge "Fix lxc rootfs attached two devices in some action"
Merge "VMware: update test file names"
Merge "Catch InstanceIsLocked exception on server actions"