-
Notifications
You must be signed in to change notification settings - Fork 2
fix(vd): fail with error on insufficient PVC size #1295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
When importing VirtualDisk from VirtualImage or ClusterVirtualImage, if PVC size is insufficient, set phase to Failed with error message in Ready condition instead of hanging in Pending without errors. Signed-off-by: Daniil Loktev <[email protected]>
c670206
to
d743031
Compare
Workflow has started. The target step completed with status: failure. |
Workflow has started. The target step completed with status: failure. |
Workflow has started. The target step completed with status: cancelled. |
Workflow has started. The target step completed with status: success. |
Description
When importing VirtualDisk from VirtualImage or ClusterVirtualImage, if PVC size is insufficient, set phase to Failed with error message in Ready condition instead of hanging in Pending without errors.
Why do we need it, and what problem does it solve?
To provide clear, immediate feedback to users when a VD configuration error occurs during import from a VI or a CVI
What is the expected result?
Checklist
Changelog entries