diff --git a/api-ref/source/server-migrations.inc b/api-ref/source/server-migrations.inc index f0d45f2d4442..4a2ac97f4e14 100644 --- a/api-ref/source/server-migrations.inc +++ b/api-ref/source/server-migrations.inc @@ -124,9 +124,11 @@ Specify the ``force_complete`` action in the request body. .. note:: Microversion 2.22 or greater is required for this API. -.. note:: Not all compute back ends support forcefully completing an +.. note:: Not all `compute back ends`_ support forcefully completing an in-progress live migration. +.. _compute back ends: https://docs.openstack.org/nova/latest/user/support-matrix.html#operation_force_live_migration_to_complete + Policy defaults enable only users with the administrative role to perform this operation. Cloud providers can change these permissions through the ``policy.json`` file. @@ -148,9 +150,11 @@ to determine whether the request succeeded. **Troubleshooting** -If the server status remains ``ACTIVE`` for an inordinate amount of time, the -request may have failed. Ensure you meet the preconditions and run the request -again. If the request fails again, investigate the compute back end. +If the server status remains ``MIGRATING`` for an inordinate amount of time, +the request may have failed. Ensure you meet the preconditions and run the +request again. If the request fails again, investigate the compute back end. +More details can be found in the +`admin guide `_. Normal response codes: 202 @@ -215,7 +219,7 @@ using:: **Troubleshooting** -If the server task_state remains ``migrating`` for an inordinate amount of +If the server status remains ``MIGRATING`` for an inordinate amount of time, the request may have failed. Ensure you meet the preconditions and run the request again. If the request fails again, investigate the compute back end. diff --git a/doc/source/admin/configuring-migrations.rst b/doc/source/admin/configuring-migrations.rst index d36e0f23bad3..7c9b737db6f0 100644 --- a/doc/source/admin/configuring-migrations.rst +++ b/doc/source/admin/configuring-migrations.rst @@ -228,9 +228,9 @@ memory-intensive instances succeed. ephemeral storage in GiB is added. The timeout in seconds is the instance size multiplied by the configurable - parameter ``live_migration_completion_timeout``, whose default is 800. For - example, shared-storage live migration of an instance with 8GiB memory will - time out after 6400 seconds. + parameter :oslo.config:option:`libvirt.live_migration_completion_timeout`, + whose default is 800. For example, shared-storage live migration of an + instance with 8GiB memory will time out after 6400 seconds. #. **Instance downtime**