commit 4d0aab16ecac5128a20ab9229d444bc49a9c722b
Author: Matt Riedemann <email address hidden>
Date: Tue Mar 26 09:55:23 2019 -0400
api-ref: add more details to confirmResize troubleshooting
This does a few things:
1. Fixes the "migration_status" wording since that does not
exist and could be confused as a field on the server
resource which it is not, it is referring to the migration
resource status.
2. Fixes the RESIZED status mention since that is not a real
server status, it probably meant VERIFY_RESIZE (RESIZED is
the name of the nova.compute.vm_states variable used in the
code to set the VERIFY_RESIZE status in the API).
3. Adds words about options to correct the server status from
ERROR after confirmResize fails, the most obvious being
an admin resetting the server status to ACTIVE or the user
hard rebooting the server.
Reviewed: https:/ /review. openstack. org/647741 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=4d0aab16eca c5128a20ab9229d 444bc49a9c722b
Committed: https:/
Submitter: Zuul
Branch: master
commit 4d0aab16ecac512 8a20ab9229d444b c49a9c722b
Author: Matt Riedemann <email address hidden>
Date: Tue Mar 26 09:55:23 2019 -0400
api-ref: add more details to confirmResize troubleshooting
This does a few things:
1. Fixes the "migration_status" wording since that does not
exist and could be confused as a field on the server
resource which it is not, it is referring to the migration
resource status.
2. Fixes the RESIZED status mention since that is not a real vm_states variable used in the
server status, it probably meant VERIFY_RESIZE (RESIZED is
the name of the nova.compute.
code to set the VERIFY_RESIZE status in the API).
3. Adds words about options to correct the server status from
ERROR after confirmResize fails, the most obvious being
an admin resetting the server status to ACTIVE or the user
hard rebooting the server.
Change-Id: I7de257ad78031d 137616d724bee3f a1cbf40d6fa
Related-Bug: #1821594