Skip to content

fix(vm): show CSI and volume errors in VM status#1766

Open
loktev-d wants to merge 13 commits intomainfrom
fix/vm/show-csi-volume-errors
Open

fix(vm): show CSI and volume errors in VM status#1766
loktev-d wants to merge 13 commits intomainfrom
fix/vm/show-csi-volume-errors

Conversation

@loktev-d
Copy link
Contributor

@loktev-d loktev-d commented Nov 28, 2025

Description

Fix VM status (Running condition) to properly display CSI driver and volume attachment errors
Fix misleading errors related to SDN ("waiting for SDN module") (NetworkReady condition)

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 NetworkReady condition. The actual CSI error was hidden in pod events and not surfaced in the VM status.

What is the expected result?

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: vm
type: fix
summary: show CSI and volume errors in VM status

Signed-off-by: Daniil Loktev <lokt.daniil@gmail.com>
loktev-d and others added 3 commits November 28, 2025 13:59
Signed-off-by: Daniil Loktev <lokt.daniil@gmail.com>
Signed-off-by: Daniil Loktev <lokt.daniil@gmail.com>
@loktev-d loktev-d requested a review from fl64 as a code owner November 28, 2025 13:00
loktev-d and others added 4 commits November 30, 2025 15:45
Signed-off-by: Daniil Loktev <lokt.daniil@gmail.com>
Signed-off-by: Daniil Loktev <lokt.daniil@gmail.com>
Signed-off-by: Daniil Loktev <lokt.daniil@gmail.com>
@loktev-d loktev-d added this to the v1.2.0 milestone Dec 1, 2025
Signed-off-by: Daniil Loktev <lokt.daniil@gmail.com>
@universal-itengineer universal-itengineer modified the milestones: v1.2.0, v1.3.0 Dec 1, 2025
@loktev-d loktev-d added the e2e/run Run e2e test on cluster of PR author label Dec 1, 2025
@deckhouse-BOaTswain
Copy link
Contributor

deckhouse-BOaTswain commented Dec 1, 2025

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Dec 1, 2025
@loktev-d loktev-d marked this pull request as draft December 2, 2025 14:39
@loktev-d loktev-d added the e2e/run Run e2e test on cluster of PR author label Dec 2, 2025
@deckhouse-BOaTswain
Copy link
Contributor

deckhouse-BOaTswain commented Dec 2, 2025

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Dec 2, 2025
@loktev-d loktev-d marked this pull request as ready for review December 3, 2025 13:26
@loktev-d loktev-d marked this pull request as draft December 3, 2025 13:26
@nevermarine nevermarine modified the milestones: v1.3.0, v1.4.0 Dec 16, 2025
@nevermarine nevermarine removed this from the v1.4.0 milestone Jan 23, 2026
@loktev-d loktev-d marked this pull request as ready for review February 9, 2026 10:48
@nevermarine nevermarine modified the milestones: v1.5.0, v1.6.0 Feb 9, 2026
Signed-off-by: Daniil Loktev <lokt.daniil@gmail.com>
@LopatinDmitr LopatinDmitr self-requested a review February 12, 2026 17:29
@loktev-d loktev-d added the e2e/run Run e2e test on cluster of PR author label Feb 13, 2026
@deckhouse-BOaTswain
Copy link
Contributor

deckhouse-BOaTswain commented Feb 13, 2026

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Feb 13, 2026
@loktev-d loktev-d added the e2e/run Run e2e test on cluster of PR author label Feb 13, 2026
@deckhouse-BOaTswain
Copy link
Contributor

deckhouse-BOaTswain commented Feb 13, 2026

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Feb 13, 2026
@loktev-d loktev-d added the e2e/run Run e2e test on cluster of PR author label Feb 13, 2026
@deckhouse-BOaTswain
Copy link
Contributor

deckhouse-BOaTswain commented Feb 13, 2026

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Feb 13, 2026
@loktev-d loktev-d added the e2e/run Run e2e test on cluster of PR author label Feb 19, 2026
@deckhouse-BOaTswain
Copy link
Contributor

deckhouse-BOaTswain commented Feb 19, 2026

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Feb 19, 2026
@loktev-d loktev-d added the e2e/run Run e2e test on cluster of PR author label Feb 19, 2026
@deckhouse-BOaTswain
Copy link
Contributor

deckhouse-BOaTswain commented Feb 19, 2026

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Feb 19, 2026
@loktev-d loktev-d added the e2e/run Run e2e test on cluster of PR author label Feb 19, 2026
@deckhouse-BOaTswain
Copy link
Contributor

deckhouse-BOaTswain commented Feb 19, 2026

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Feb 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

Comments