← Production Guide · VM lifecycle
PG-22 · Resize not finished?¶

Operational lesson. VERIFY_RESIZE is not stuck. It waits for a decision only the owner can make.
The memo as text¶
Situation. After a resize or a cold migration, the instance sits in VERIFY_RESIZE, RESIZE or ERROR. Three states, three different situations.
First checks (read-only):
- State, task state, fault:
openstack server show <id> -c status -c OS-EXT-STS:task_state -c fault - The migration record:
openstack server migration list --server <id> - Its actions, then the failed step:
openstack server event list <id>, then event show <id> <req-id> - Are both computes up?:
openstack compute service list --service nova-compute
Think before acting:
- 🛑 Destructive. Confirm deletes the old copy on the source. Revert loses what the guest wrote to its local disks since the resize. Both are the owner's call.
- ⛔ Avoid.
server set --state activeon an instance inERROR. It changes the database only: find out where the disks are first.
Go deeper¶
This memo is a memory aid. The procedure, with every command, its risk warning and its limits, is in the runbook:
- Resize or cold migration not finished. Instance in VERIFY_RESIZE, stuck in RESIZE, or in ERROR after a failed resize ·
lab-verifiedon 2026.1 · highest risk in the page: destructive
Where this holds. Written from the Nova 2026.1 source and lab-verified with Kolla-Ansible, two computes and local qcow2 disks: the unconfirmed resize, a service dying part way, SSH between computes and a smaller disk were reproduced; a destination that cannot run the guest was not. Nova does not shrink disks, except a root disk booted from volume. With resize_confirm_window set, resizes older than the window are confirmed without the owner and can no longer be reverted.
LinkedIn kit¶
- Image:
dist/pg-22-resize-not-finished.png(1080 × 1350) - Post title: VERIFY_RESIZE is not a stuck state. It is a pending decision.
After a resize or a cold migration, an instance can sit in three states that mean very different things.
→ VERIFY_RESIZE, no task state: the resize worked. It waits for a confirm or a revert, and can wait for days.
→ RESIZE, with a task state: the operation stopped part way. A service died, or a message was lost.
→ ERROR: a step failed, and the fault says which one.
The first is the one that surprises people. While an instance stays in VERIFY_RESIZE, the old copy is kept on the source and Placement holds resources on both computes. Many of them make hosts look fuller than they are.
And neither way out can be undone: confirm deletes the old copy, revert loses what the guest wrote to its local disks since the resize. That decision belongs to the owner.
Runbook: https://github.com/OzarLand/ozarland-academy/blob/main/docs/runbooks/lifecycle/resize-stuck-in-verify-resize-or-failed.md
More memos: https://github.com/OzarLand/ozarland-academy/tree/main/docs/production
#OpenStack #Nova #Placement #CloudOperations #SRE #OzarLand
Source: resize-not-finished.yml. Found an error, or does your platform behave differently? Open an issue or see CONTRIBUTING.