fix(vm): show CSI and volume errors in VM status#1766
fix(vm): show CSI and volume errors in VM status#1766
Conversation
|
Workflow has started. The target step completed with status: failure. |
|
Workflow has started. The target step completed with status: failure. |
images/virtualization-artifact/pkg/controller/vm/internal/watcher/volumeevent_watcher.go
Outdated
Show resolved
Hide resolved
images/virtualization-artifact/pkg/controller/vm/internal/watcher/volumeevent_watcher.go
Outdated
Show resolved
Hide resolved
images/virtualization-artifact/pkg/controller/vm/vm_controller.go
Outdated
Show resolved
Hide resolved
images/virtualization-artifact/pkg/controller/vm/internal/lifecycle.go
Outdated
Show resolved
Hide resolved
Signed-off-by: Daniil Loktev <lokt.daniil@gmail.com>
|
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: failure. |
|
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: failure. |
Description
Fix VM status (
Runningcondition) to properly display CSI driver and volume attachment errorsFix misleading errors related to SDN ("waiting for SDN module") (
NetworkReadycondition)Why do we need it, and what problem does it solve?
When a VM fails to start due to CSI driver issues (e.g., missing CSI driver, volume attachment failures), the Console UI shows incorrect error messages: "Cannot determine the status of additional interfaces, waiting for a response from the SDN module", which come from
NetworkReadycondition. The actual CSI error was hidden in pod events and not surfaced in the VM status.What is the expected result?
Checklist
Changelog entries