Skip to content

Conversation

hardcoretime
Copy link
Contributor

@hardcoretime hardcoretime commented Sep 22, 2025

Description

  • Skip test if forced restoration fails with the virtual machine in the pending phase.
  • Skip annotation and label checks.
  • Skip MAC address checks.

Why do we need it, and what problem does it solve?

These bugs are currently known, and nightly end-to-end tests should not fail for the related cases.

What is the expected result?

Nightly end-to-end tests should not fail due to known errors.

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: api
type: chore
summary: "Nightly end-to-end tests should not fail due to known errors."
impact_level: low

@hardcoretime hardcoretime added this to the v1.1.0 milestone Sep 22, 2025
@hardcoretime hardcoretime force-pushed the test/vmrestore/disable-some-checks branch from e84a6ae to 5d7a28f Compare September 22, 2025 15:36
- Skip test if forced restoration fails with the virtual machine in the pending phase.
- Skip annotation and label checks.
- Skip MAC address checks.

Signed-off-by: Roman Sysoev <[email protected]>
@hardcoretime hardcoretime force-pushed the test/vmrestore/disable-some-checks branch from 5d7a28f to 3495a08 Compare September 22, 2025 16:03
Isteb4k
Isteb4k previously approved these changes Sep 22, 2025
@hardcoretime hardcoretime merged commit c6261ed into main Sep 22, 2025
25 of 27 checks passed
@hardcoretime hardcoretime deleted the test/vmrestore/disable-some-checks branch September 22, 2025 18:48
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.

3 participants