@Yong, I have tested again this scenario following the comments:
Block Migration option selected when the VM has been booted from an image. Live Migration option directly, when the VM has been booted from a volume.
Both cases where successfully.
I have executed this operation back and forth several times, with the same result. So I believe you can ask for this bug to be closed.
All the experiments were performed using this StarlingX image version:
controller-0:~$ cat /etc/build.info ### ### StarlingX ### Built from master ###
OS="centos" SW_VERSION="19.01" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="20190802T013000Z"
JOB="STX_build_master_master" <email address hidden>" BUILD_NUMBER="200" BUILD_HOST="starlingx_mirror" BUILD_DATE="2019-08-02 01:30:00 +0000" controller-0:~$
@Yong, I have tested again this scenario following the comments:
Block Migration option selected when the VM has been booted from an image.
Live Migration option directly, when the VM has been booted from a volume.
Both cases where successfully.
I have executed this operation back and forth several times, with the same result. So I believe you can ask for this bug to be closed.
All the experiments were performed using this StarlingX image version:
controller-0:~$ cat /etc/build.info
###
### StarlingX
### Built from master
###
OS="centos" "20190802T01300 0Z"
SW_VERSION="19.01"
BUILD_TARGET="Host Installer"
BUILD_TYPE="Formal"
BUILD_ID=
JOB="STX_ build_master_ master" "starlingx_ mirror" "2019-08- 02 01:30:00 +0000"
<email address hidden>"
BUILD_NUMBER="200"
BUILD_HOST=
BUILD_DATE=
controller-0:~$