Skip to content

fix(vmrestore): handle the nil value vm.spec.provisioning#971

Merged
hardcoretime merged 1 commit into
mainfrom
fix/vmrestore/handle-nil-value-vm-provisioning
Apr 24, 2025
Merged

fix(vmrestore): handle the nil value vm.spec.provisioning#971
hardcoretime merged 1 commit into
mainfrom
fix/vmrestore/handle-nil-value-vm-provisioning

Conversation

@hardcoretime
Copy link
Copy Markdown
Contributor

@hardcoretime hardcoretime commented Apr 24, 2025

Description

Handle the vm.spec.provisioning correctly when its value is nil.

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

When the vm.spec.provisioning is nil, it causes a panic in the controller.

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: vmrestore
type: fix
summary: "Handle the `vm.spec.provisioning` correctly when its value is empty."
impact_level: low

Signed-off-by: Roman Sysoev <roman.sysoev@flant.com>
@hardcoretime hardcoretime added this to the v0.18.0 milestone Apr 24, 2025
@hardcoretime hardcoretime added the e2e/run Run e2e test on cluster of PR author label Apr 24, 2025
@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Apr 24, 2025
@hardcoretime hardcoretime merged commit cbe3d55 into main Apr 24, 2025
65 of 70 checks passed
@hardcoretime hardcoretime deleted the fix/vmrestore/handle-nil-value-vm-provisioning branch April 24, 2025 12:55
@Isteb4k Isteb4k modified the milestones: v0.18.0, v0.17.0 Apr 28, 2025
yachmenevas pushed a commit that referenced this pull request Oct 15, 2025
Signed-off-by: Roman Sysoev <roman.sysoev@flant.com>
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