| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Codecov Report❌ Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.
@@ Coverage Diff @@
## 4.20 #13210 +/- ##
============================================
- Coverage 16.26% 16.25% -0.02%
Complexity 13433 13433
============================================
Files 5665 5666 +1
Lines 500572 500899 +327
Branches 60792 60884 +92
============================================
+ Hits 81417 81419 +2
- Misses 410047 410373 +326
+ Partials 9108 9107 -1
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.
Looks good (did not test).
@erikbocks does this apply for 4.20/4.22? If yes, can you rebase?
Sorry, something went wrong.
|
This change can be applied to both 4.20 and 4.22. However, the other changes can only be applied to the 4.22 branch, as they are dependent on code introduced in #9270. I will put the 4.22 changes to another PR, and rebase this one to the 4.20 branch. |
Sorry, something went wrong.
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 17972 |
Sorry, something went wrong.
|
could this be combined with #13212 ? |
Sorry, something went wrong.
|
@DaanHoogland, the reason why the PRs are separated is explained at #13210 (comment) and at #13212 PR's description. As the #13212 changes are dependent on changes introduced after 4.21, but the change in this PR is preset at both branches, it was better to separate them to include this fix in the next 4.20 minor. |
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 Build Failed (tid-16174) |
Sorry, something went wrong.
|
@winterhazel 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 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 18068 |
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.
|
I validated that QemuImg's behavior using longs was kept by taking a snapshot with the timeout configured as 2147483 (the closest number to Java's integer overflow). During the tests, I tried to set my snapshot timeout to 2200000 (to cause an Integer overflow), and observed that the command failed to be sent because they use integers internally. Not related to the PR, but pointing it out. |
Sorry, something went wrong.
|
[SF] Trillian test result (tid-16208)
|
Sorry, something went wrong.
There was a problem hiding this comment.
clgtm
Sorry, something went wrong.
|
Tested manually. The timeout is being defined correctly now. |
Sorry, something went wrong.
(cherry picked from commit a3970bb)
| Back | FazBrowse Home | New Git URL |
Description
The #9659 PR introduced the commands.timeout global configuration for granular command timeout definition. If a operator wishes to increase snapshot related timeouts, he could increase the CreateObjectCommand timeout in the commands.timeout configuration. The defined timeouts are set in seconds.
However, normal and incremental snapshots creation flows use qemu-img script to execute some of the necessary operations. These scripts accept timeouts as milliseconds, but receive them as seconds from the CreateObjectCommand. This leads to incorrect timeouts.
Therefore, this PR converts the CreateObjectCommand seconds to milliseconds before passing them to qemu-img scripts.
Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
First, I set commands.timeout configuration value to CreateObjectCommand=300. This defines this command timeout to 5 minutes. Then, I tried to create a full volume snapshot. The process failed due to a timeout.
Command timeout logI installed the packages with the timeout conversion to my local environment, then tried to create another snapshot. Using a debug breakpoint, I validated that the qemu-img script instance had the converted timeout. The new snapshot was created successfully,
When trying to create a incremental snapshot, the same error occurred. Then, I installed the packages with the necessary changes and tried to create another incremental snapshot. This process also used debug breakpoints to validate the scripts timeout.