I tested this review in my environment, and with this code in place I could no longer reproduce the issue raised in bug 1769131
Note: In this bug images_type is default (ceph is not being used)
Similar to above, when cold migrating an instance from compute02 to compute01, at the step where it's awaiting confirmation for resize/migrate, the following files can be found:
I tested this review in my environment, and with this code in place I could no longer reproduce the issue raised in bug 1769131
Note: In this bug images_type is default (ceph is not being used)
Similar to above, when cold migrating an instance from compute02 to compute01, at the step where it's awaiting confirmation for resize/migrate, the following files can be found:
compute01 kolla/var/ lib/nova/ instances/ 54bd-4e39- b57d-fdbaa05a31 db
/var/lib/
\-- 0d548887-
\-- console.log
compute02 kolla/var/ lib/nova/ instances/ 54bd-4e39- b57d-fdbaa05a31 db_resize
1 directory, 1 file
/var/lib/
\-- 0d548887-
\-- console.log
After confirming the migrate/resize, this becomes:
/var/lib/ kolla/var/ lib/nova/ instances/ 54bd-4e39- b57d-fdbaa05a31 db
\-- 0d548887-
\-- console.log
1 directory, 1 file kolla/var/ lib/nova/ instances/
/var/lib/
0 directories, 0 files
Excellent !
No disk.info file is present on the source host (and the instance dir is also gone, which it should be)
For example, I was then able to live-migrate the instance (from compute01 back to compute02) since the pre_live_migration checks pass.