-
Notifications
You must be signed in to change notification settings - Fork 28
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
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
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this 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
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? |
@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 ;) |
2c3f74a
to
242964e
Compare
Signed-off-by: Bella Khizgiyaev <bkhizgiy@redhat.com>
Quality Gate passedIssues Measures |
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.