fix errors in revert resize api docs

The revert resize action's documentation appears to have been copied
from the documentation for confirm resize, and missed replacing the
word 'confirm' with 'revert' in one case. This fixes that.

It also gives incorrect information about the states involved through
the revert process. This also corrects that.

Change-Id: Ib2436da238a4a7b71454ecfee81ede4054b3018e
Closes-Bug: #1593295
This commit is contained in:
Matthew Edmonds 2016-06-16 12:14:42 -04:00
parent 95ed8cdb4c
commit ce01ef30e3

View File

@ -615,24 +615,26 @@ Cancels and reverts a pending resize action for a server.
Specify the ``revertResize`` action in the request body.
After you make this request, you typically must keep polling the server status
to determine whether the request succeeded. A successfully reverting resize
operation shows a status of ``ACTIVE`` or ``SHUTOFF`` and a migration_status
of ``reverted``. You can also see the reverted server in the compute node
that OpenStack Compute manages.
Preconditions
You can only confirm the resized server where the status is
``VERIFY_RESIZE`` and the vm_status is ``RESIZED``.
You can only revert the resized server where the status is
``VERIFY_RESIZE`` and the OS-EXT-STS:vm_state is ``resized``.
If the server is locked, you must have administrator privileges to revert
the resizing.
Asynchronous Postconditions
After you make this request, you typically must keep polling the server status
to determine whether the request succeeded. A reverting resize operation shows
a status of ``REVERT_RESIZE`` and a task_state of ``resize_reverting``. If
successful, the status will return to ``ACTIVE`` or ``SHUTOFF``. You can also
see the reverted server in the compute node that OpenStack Compute manages.
Troubleshooting
If the server status remains ``RESIZED``, the request failed. Ensure you meet
the preconditions and run the request again. If the request fails again,
If the server status remains ``VERIFY_RESIZE``, the request failed. Ensure you
meet the preconditions and run the request again. If the request fails again,
investigate the compute back end.
The server is not reverted in the compute node that OpenStack Compute manages.