Description of problem: As per my discussion with engineering team, the documentation at [1], mentions customizing the "live_migration_uri" for the use of a dedicated network for live block migration traffic. This customization is an unsupported one as it does not work with live block migration and it is something that nova never had any intentional support for. Please mark this appropriately in the documentation i.e to the max as a temporary workaround. There is a new parameter which was introduced in RHOSP 9 i.e "live_migration_inbound_addr" which can used for specifying the network to be used for the purpose of moving live block migration traffic. This setting can be made in nova.conf file. Below is the section in the documentation which needs to be edited: +++ Lastly, the use of a dedicated network for the live migration is an option. If you can take advantage of this solution, first add the -lm suffix to the hostname template in the live_migration_uri option by running the following command: # openstack-config --set /etc/nova/nova.conf libvirt live_migration_uri qemu+tcp://nova@%s-lm/system Then make sure your DNS servers resolve host names with this suffix to IP addresses in the dedicated network. +++ [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/migrating_instances/how_to_migrate_a_live_instance#migrate_a_live_instance Please take a note that the same in mentioned in the below versions of RHOSP: RHOSP 7 RHOSP 8 RHOSP 9 RHOSP 10 RHOSP 11 Please address this in the docs ASAP as this may affect a lot of customers. Thanks.
This cannot be used with live migration over SSH (the default now). It is currently blocked by https://bugs.launchpad.net/nova/+bug/1671288.
The guide against which this bug was raised was flagged as outdated, and has been retired. As such, the content identified in this bug as problematic has been removed. The up-to-date documentation for live instance migration is available here: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/director_installation_and_usage/#sect-Migrating_VMs_from_an_Overcloud_Compute_Node Moving to CLOSED.