server: fix pod retrieval during volume attach#10324
server: fix pod retrieval during volume attach#10324DaanHoogland merged 8 commits intoapache:4.19from
Conversation
Fixes apache#10120 When an uploaded volume is attached to a VM for which no existing volume can be found it was resulting in error. For such volumes, server needs to find a suitable pool first and copy them to the pool from secondary store. Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
|
@blueorangutan package |
|
@shwstppr 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. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.19 #10324 +/- ##
===========================================
+ Coverage 0 15.15% +15.15%
- Complexity 0 11313 +11313
===========================================
Files 0 5409 +5409
Lines 0 474664 +474664
Branches 0 57904 +57904
===========================================
+ Hits 0 71935 +71935
- Misses 0 394686 +394686
- Partials 0 8043 +8043
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 12327 |
weizhouapache
left a comment
There was a problem hiding this comment.
code lgtm
@shwstppr
thanks for the quick fix
|
@blueorangutan test |
|
@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-12306)
|
|
@blueorangutan package |
|
@shwstppr 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. |
DaanHoogland
left a comment
There was a problem hiding this comment.
code looks good, let's test ;)
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 12339 |
|
@DaanHoogland this is ready now. If we revert #10267 then I'll add commits from that here |
|
@blueorangutan test |
|
@shwstppr a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
Fixes issue highlighted in apache#9315 (comment) Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
daa379e to
557b3ba
Compare
|
@blueorangutan package |
|
@shwstppr 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. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 12363 |
|
@blueorangutan test |
|
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-12321)
|
Looks fine |
|
[SF] Trillian test result (tid-12329)
|
kiranchavala
left a comment
There was a problem hiding this comment.
LGTM, tested the volume upload scenario and its working fine ,
Also, Able to attach volume in allocated state
Smoke test also passed successfully
- Launch 2 Cloudstack instances (vm1 and vm2) with only root disk in the same admin account.
- Stop the instances (vm1 and vm2) and detach the root disk associated with the vm's (vm1 and vm2)
- Download the root disk of vm1 to you local desktop
- Upload the root disk of vm1 to the admin account. The state of the volume will be in Uploaded state
- Attach the uploaded root disk of vm 1 to vm 2(Make sure to attach it as device id 0)
- Uploaded volume attached successfully
Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
Description
Includes changes from #10267 as they've been reverted by #10323
Fixes issue highlighted in #9315 (comment)
A volume in Allocated state can be attached to a stopped VM even when the actual volume is not created in the primary store.
test_12_start_vm_multiple_volumes_allocatedin test/integration/smoke/test_vm_life_cycle.py does the same.After changes in #10267, a scenario was failing as a suitable pool was not found for an allocated volume when attached to a VM which has never been started
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Verified test_vm_life_cycle.py with changes,
How did you try to break this feature and the system with this change?