| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Codecov ReportAttention: Patch coverage is 9.41402% with 943 lines in your changes missing coverage. Please review.
@@ Coverage Diff @@
## main #10632 +/- ##
============================================
+ Coverage 16.41% 16.56% +0.15%
- Complexity 13629 14008 +379
============================================
Files 5702 5758 +56
Lines 503405 511750 +8345
Branches 60976 62242 +1266
============================================
+ Hits 82626 84774 +2148
- Misses 411594 417506 +5912
- Partials 9185 9470 +285
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry.
|
Sorry, something went wrong.
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
Sorry, something went wrong.
|
@JoaoJandre a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 13204 |
Sorry, something went wrong.
|
@rohityadavcloud @sureshanaparti @weizhouapache could we run the CI? |
Sorry, something went wrong.
|
@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
Sorry, something went wrong.
|
[SF] Trillian test result (tid-13177)
|
Sorry, something went wrong.
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
Sorry, something went wrong.
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
Sorry, something went wrong.
|
@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
Sorry, something went wrong.
|
[SF] Trillian test result (tid-13740)
|
Sorry, something went wrong.
|
@DaanHoogland I'm pretty sure these test results are not linked to this PR, could we try one more time? |
Sorry, something went wrong.
…o kvm-disk-only-vm-snapshot
|
@slavkap I've pushed a new commit based on your suggestions. Could you check? |
Sorry, something went wrong.
|
@DaanHoogland a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✖️ debian ✔️ suse15. SL-JID 14177 |
Sorry, something went wrong.
|
I checked the debian build in the background. There is nothing wrong. It was one of those timing unit-test that failed 18:11:30 [ERROR] ConfigKeyScheduledExecutionWrapperTest.scheduleDynamicTest:110 Runnable ran four times per second
18:11:30 Expected: one of {<7>, <8>}
18:11:30 but: was <6>
I think we should modify those to be more robust to virtualised environments. |
Sorry, something went wrong.
Thanks for checking. I agree we should make these tests more robust. |
Sorry, something went wrong.
fyi I ran the build in the background and it passes without issues |
Sorry, something went wrong.
|
@DaanHoogland are we good to merge then? |
Sorry, something went wrong.
|
I'm fine with it. |
Sorry, something went wrong.
There was a problem hiding this comment.
code LGTM
I didn't have time to run tests with NFS except for creating/deleting VM snapshots on running and stopped VMs.
This doesn't affect other storage plug-ins, but I have executed the StorPool tests that have passed
Sorry, something went wrong.
Co-authored-by: João Jandre <joao@scclouds.com.br> Co-authored-by: Fabricio Duarte <fabricio.duarte.jr@gmail.com>
| Back | FazBrowse Home | New Git URL |
Description
This PR implements the spec available at #9524. For more information regarding it, please read the spec.
Furthermore, the following changes that are not contemplated in the spec were added:
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Basic Tests
I created a test VM to carry out the tests below. Additionally, after performing the relevant operations, the VM's XML and the storage were checked to observe if the snapshots existed.
Snapshot Creation
The tests below were also repeated with the VM stopped.
Snapshot Reversion
Snapshot Removal
Advanced Tests
Deletion Test
All tests were carried out with the VM stopped.
The snapshot was marked as hidden and was not removed from storage.
Snapshot s3 was removed normally. Snapshot s2 was merged with snapshot s4.
Snapshot s4 was marked as hidden and was not removed from storage.
Snapshot s5 was removed normally. Snapshot s4 was merged with the delta of the VM's volume.
Reversion Test
Snapshot s1 was marked as hidden and was not removed from storage.
Concurrent Test
I created 4 VMs and took a VM snapshot of each. Then, I instructed to remove them all at the same time. All snapshots were removed simultaneously and successfully.
Test with Multiple Volumes
I created a VM with one datadisk and attached 8 more datadisks (10 volumes in total), took two VM snapshots, and then instructed to remove one at a time. The snapshots were removed successfully.
Tests Changing the snapshot.merge.timeout Config
Tests Related to Volume Resize with Disk-Only VM Snapshots on KVM
The last two tests were repeated on a VM with several snapshots, so that a merge between snapshots was performed. The result was the same.
Tests Related to Events: