-
Sub-task
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
None
-
Description of problem:
When a snapshot fails, the status shows "not ready" even though it is in error state
Version-Release number of selected component (if applicable):
4.20
How reproducible:
Steps to Reproduce:
1. create a vm snapshot - set the deadline to 1s 2. 3.
Actual results:
vm status appears as "Not ready" - taken from type: Ready condition
Expected results:
vm status should be Failed with the relevant reason
Additional info:
status: conditions: - lastProbeTime: null lastTransitionTime: "2025-10-29T14:06:12Z" reason: Operation failed status: "False" type: Progressing - lastProbeTime: null lastTransitionTime: "2025-10-29T14:06:11Z" reason: Not ready status: "False" type: Ready - lastProbeTime: null lastTransitionTime: "2025-10-29T14:06:12Z" reason: snapshot deadline exceeded status: "True" type: Failure indications: - GuestAgent - Online phase: Failed readyToUse: false sourceUID: c8a4681e-1cdd-485a-acdc-72a5860cfd1f virtualMachineSnapshotContentName: vmsnapshot-content-ec928d53-63df-40ae-885d-b1d8cc8605b4