| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Codecov ReportAttention: Patch coverage is 6.06061% with 31 lines in your changes missing coverage. Please review.
@@ Coverage Diff @@
## 4.19 #9498 +/- ##
===========================================
Coverage 15.10% 15.10%
- Complexity 11220 11225 +5
===========================================
Files 5404 5404
Lines 473460 473486 +26
Branches 57728 59047 +1319
===========================================
+ Hits 71525 71541 +16
- Misses 393941 393948 +7
- Partials 7994 7997 +3
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.
There was a problem hiding this comment.
clgtm, you do have a good test scenario for this, do you @rp- ? Or is it only intermitted (i.e. not automatable)
Sorry, something went wrong.
I'm not sure it is easy to reproducible automate that, as it is a timing/parallelism issue. But we have 2 customers who didn't report any issues with this yet. |
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 10620 |
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-11065)
|
Sorry, something went wrong.
|
@rohityadavcloud 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 10927 |
Sorry, something went wrong.
|
Packaging result [SF]: ✖️ el8 ✖️ el9 ✔️ debian ✖️ suse15. SL-JID 10950 |
Sorry, something went wrong.
|
I guess the failed packaging is nothing related to this PR? |
Sorry, something went wrong.
11:02:25 [ERROR] Failures: 11:02:25 [ERROR] VMSchedulerImplTest.testScheduleNextJobScheduleCurrentSchedule:262 expected:<Wed Sep 04 09:02:00 UTC 2024> but was:<Wed Sep 04 09:03:00 UTC 2024> looks like a test was too slow , so might have to do with too busy container. retrying @rp- |
Sorry, something went wrong.
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 10988 |
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-11364)
|
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 11033 |
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-11408)
|
Sorry, something went wrong.
|
[SF] Trillian test result (tid-11765)
|
Sorry, something went wrong.
|
@JoaoJandre Adding a deletStoragePool to ModifyStoragePool has the negative effect that there would never be a mounted primary storage on the agent, which is currently assumed and creating instances/copy templates will fail. I'm not really sure how to move forward with this then, maybe don't let the management server create 2 jobs with the same secondary storage pool to the same agent in parallel. |
Sorry, something went wrong.
We could keep the ref-count for the secondary storage only. The com.cloud.hypervisor.kvm.storage.KVMStoragePoolManager#createStoragePool(java.lang.String, java.lang.String, int, java.lang.String, java.lang.String, com.cloud.storage.Storage.StoragePoolType, java.util.Map<java.lang.String,java.lang.String>, boolean) already takes a parameter to determine if the pool is primary or not, we could pass it to com.cloud.hypervisor.kvm.storage.LibvirtStorageAdaptor#createStoragePool to determine if we should keep the ref-count or not. |
Sorry, something went wrong.
And on delete? only check if the uuid is part of the refcount map? |
Sorry, something went wrong.
@rp- Yeah, if it is not part of the map, we assume that it can be deleted. If it is, we check the refcount. |
Sorry, something went wrong.
|
@JoaoJandre This seem to work in my tests now |
Sorry, something went wrong.
If a secondary storage pool is used by e.g. 2 concurrent snapshot->template actions, if the first action finished it removed the netfs mount point for the other action. Now the storage pools are usage ref-counted and will only deleted if there are no more users.
|
@rp- 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 11533 |
Sorry, something went wrong.
|
@DaanHoogland can you start tests here, I would want to see if they succeed now |
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.
There was a problem hiding this comment.
CLGTM, I'll try to test this in the coming days
Sorry, something went wrong.
|
[SF] Trillian test result (tid-11773)
|
Sorry, something went wrong.
|
Tested:
All operations succeeded and the storage was umounted afterwards (only once detached for test 4). |
Sorry, something went wrong.
If a secondary storage pool is used by e.g. 2 concurrent snapshot->template actions, if the first action finished it removed the netfs mount point for the other action. Now the storage pools are usage ref-counted and will only deleted if there are no more users.
| Back | FazBrowse Home | New Git URL |
Description
If a storage pool is used by e.g. 2 concurrent snapshot->template actions, if the first action finished it removed the netfs mount point for the other action.
Now the storage pools are usage ref-counted and will only deleted if there are no more users.
Fixes: #8899
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Run several snapshot to template actions, that are executed on the same host.
How did you try to break this feature and the system with this change?