Fix migration with configdrive
Fix migration with configdrive

Migration fails with configdrive if there is a configdrive attached
to the instance.

After the container is created on the new host via init API call
the LXD daemon expects the directory that is originated to be on
the host to be present on the new host. Otherwise the container
will not start.

This is not tested by tempest and it should probably be included.

Signed-off-by: Chuck Short <753a8074f04ffd62a8fff7516e3ae689be8e35ad@canonical.com>

tpouyer/nova-lxd,tpouyer/nova-lxd