Skip to content
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

fix(vi): fix panic when creating vi from vd #384

Merged
merged 7 commits into from
Sep 19, 2024

Conversation

LopatinDmitr
Copy link
Contributor

@LopatinDmitr LopatinDmitr commented Sep 18, 2024

Description

This PR fixes the problem where creating a VirtualImage (VI) from a VirtualDisk (VD) caused the application to panic.

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

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.

Signed-off-by: dmitry.lopatin <dmitry.lopatin@flant.com>
Signed-off-by: dmitry.lopatin <dmitry.lopatin@flant.com>
Signed-off-by: dmitry.lopatin <dmitry.lopatin@flant.com>
Signed-off-by: dmitry.lopatin <dmitry.lopatin@flant.com>
Signed-off-by: dmitry.lopatin <dmitry.lopatin@flant.com>
@LopatinDmitr LopatinDmitr marked this pull request as ready for review September 19, 2024 06:30
@fl64 fl64 changed the title fix(vi): fix panic when create vi from vd fix(vi): fix panic when creating vi from vd Sep 19, 2024
Signed-off-by: dmitry.lopatin <dmitry.lopatin@flant.com>
Signed-off-by: dmitry.lopatin <dmitry.lopatin@flant.com>
@LopatinDmitr LopatinDmitr merged commit 62f8e47 into main Sep 19, 2024
10 checks passed
@LopatinDmitr LopatinDmitr deleted the fix/vi/fix-panic-when-create-vi-from-vd branch September 19, 2024 12:20
diafour pushed a commit that referenced this pull request Oct 2, 2024
Signed-off-by: dmitry.lopatin <dmitry.lopatin@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.

2 participants