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 virt-v2v disk name generation #872

Merged
merged 1 commit into from
May 1, 2024
Merged

Conversation

bkhizgiy
Copy link
Member

@bkhizgiy bkhizgiy commented Apr 24, 2024

Currently, the function generating the disk names didn't work as expected, and instead of matching the disk number with the corresponding letter, it caused the letters to be attached from the previous disk. This resulted in only the first disk being properly copied due to incorrect linking. With these changes, the disk name generation works as expected.

@bkhizgiy bkhizgiy changed the title fix virt-v2v disk name generation Fix virt-v2v disk name generation Apr 24, 2024
Copy link

codecov bot commented Apr 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 17.48%. Comparing base (b679a00) to head (a79f099).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #872      +/-   ##
==========================================
- Coverage   17.59%   17.48%   -0.12%     
==========================================
  Files          94       95       +1     
  Lines       16853    17006     +153     
==========================================
+ Hits         2965     2973       +8     
- Misses      13621    13765     +144     
- Partials      267      268       +1     
Flag Coverage Δ
unittests 17.48% <100.00%> (-0.12%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

virt-v2v/cold/entrypoint.go Outdated Show resolved Hide resolved
Copy link
Member

@ahadas ahadas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've made changes in the description of the PR, please update the commit (which is currently empty) accordingly
and also please add unit tests, there's a concrete case we can take from https://issues.redhat.com/browse/MTV-1098

@germanovm
Copy link

Won't this break at the 27th disk now by both the 1st and 27th disk being named sda instead of sdaa for the 27th?

@bkhizgiy
Copy link
Member Author

@germanovm ahh yes, it will, we need to add the cycle back here like we had in the original code (but without the bug:) )

@ahadas
Copy link
Member

ahadas commented Apr 30, 2024

@germanovm ahh yes, it will, we need to add the cycle back here like we had in the original code (but without the bug:) )

another case to cover in unit tests ;)

@bkhizgiy bkhizgiy force-pushed the diskname branch 2 times, most recently from 2c3f74a to 242964e Compare April 30, 2024 11:49
Makefile Outdated Show resolved Hide resolved
Makefile Outdated Show resolved Hide resolved
Signed-off-by: Bella Khizgiyaev <bkhizgiy@redhat.com>
Copy link

sonarcloud bot commented May 1, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@ahadas ahadas added this to the 2.6.1 milestone May 1, 2024
@ahadas ahadas merged commit 69a3992 into kubev2v:main May 1, 2024
11 of 12 checks passed
@ahadas ahadas removed this from the 2.6.1 milestone May 1, 2024
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