fix(api): make user-facing condition messages clearer#2558

Merged

Isteb4k merged 25 commits into

mainfrom

fix/api/user-friendly-condition-messages

Jul 1, 2026

Commits on Jun 30, 2026

fix(vm): make condition messages user-friendly
fl64
committed
fix(vmbda): make condition messages user-friendly
fl64
committed
fix(vd): make condition messages user-friendly
fl64
committed
fix(vi): make condition messages user-friendly
fl64
committed
fix(cvi): make condition messages user-friendly
fl64
committed
fix(vdsnapshot): fix grammar in condition messages
fl64
committed
fix(vmsnapshot): fix grammar in condition messages
fl64
committed
fix(vmbda): say the VirtualMachine is not running
fl64
committed
fix(vmbda): keep the node name in the storage-availability message
fl64
committed
fix(vi, cvi): unify image provisioning and image-lost wording
fl64
committed
fix(vd, vi, cvi, vmbda): make storage wording consistent
fl64
committed
fix(vi): name the PersistentVolumeClaim in the bind-wait message
fl64
committed
fix(vm, vd, vi, cvi): align wording across condition messages
fl64
committed
fix(vmbda): do not report a missing volume as not-ready
fl64
committed
fix(vm): add trailing period to provisioning condition messages
fl64
committed
fix(vm, vmclass, vmop, vdsnapshot): clean up condition message text
fl64
committed
fix(vd, vi, vdsnapshot): keep the lost object name in the message
fl64
committed
fix(vmop): describe migration progress accurately, not as node moves
fl64
committed
fix(usb, vmsop, dvcr): make user-facing condition messages clearer
fl64
committed
fix(vi): describe the PersistentVolumeClaim being prepared, not 'image storage'
fl64
committed
fix(vmbda): don't report a running VM as 'not running' on transient instance gap
fl64
committed
fix(vd, vi, vdsnapshot): address PR review comments on condition messages
fl64
committed
fix(vmsop): satisfy staticcheck ST1005 on the secret-nil error
fl64
committed
fix(vm): give actionable guidance in agent and class condition messages
fl64
committed
fix(vm): clarify why live migration is blocked, with applicable guidance
fl64
committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(api): make user-facing condition messages clearer#2558

fix(api): make user-facing condition messages clearer#2558
Isteb4k merged 25 commits into
mainfrom
fix/api/user-friendly-condition-messages

Commits on Jun 30, 2026

fix(vm): make condition messages user-friendly

fix(vmbda): make condition messages user-friendly

fix(vd): make condition messages user-friendly

fix(vi): make condition messages user-friendly

fix(cvi): make condition messages user-friendly

fix(vdsnapshot): fix grammar in condition messages

fix(vmsnapshot): fix grammar in condition messages

fix(vmbda): say the VirtualMachine is not running

fix(vmbda): keep the node name in the storage-availability message

fix(vi, cvi): unify image provisioning and image-lost wording

fix(vd, vi, cvi, vmbda): make storage wording consistent

fix(vi): name the PersistentVolumeClaim in the bind-wait message

fix(vm, vd, vi, cvi): align wording across condition messages

fix(vmbda): do not report a missing volume as not-ready

fix(vm): add trailing period to provisioning condition messages

fix(vm, vmclass, vmop, vdsnapshot): clean up condition message text

fix(vd, vi, vdsnapshot): keep the lost object name in the message

fix(vmop): describe migration progress accurately, not as node moves

fix(usb, vmsop, dvcr): make user-facing condition messages clearer

fix(vi): describe the PersistentVolumeClaim being prepared, not 'image storage'

fix(vmbda): don't report a running VM as 'not running' on transient instance gap

fix(vd, vi, vdsnapshot): address PR review comments on condition messages

fix(vmsop): satisfy staticcheck ST1005 on the secret-nil error

fix(vm): give actionable guidance in agent and class condition messages

fix(vm): clarify why live migration is blocked, with applicable guidance