| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
This is the equivalent command for applying the fix: sed -i 's_du -sb $dest | cut -f1_du -sb $dest 2>/dev/null | cut -f1 || true_g' /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/nasbackup.sh We haven't confirmed the exact root cause of the du failure yet. As a precaution, we applied this fix to all servers and will monitor backups over the next few days. So, I am running tests with 2>>/var/log/cloudstack/agent/nasbackup.err so I can see what is the error message. |
Sorry, something went wrong.
Proposed Changes Rationalebackup_size=$(du -sb "$dest" 2>/dev/null | cut -f1) || true
timeout 60 umount "$mount_point" 2>/dev/null || true
rmdir "$mount_point" 2>/dev/null || true
echo -n "$backup_size"
|
Sorry, something went wrong.
|
Dear @abh1sar , do you think you can help me with this bug? Regards, |
Sorry, something went wrong.
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #13424 +/- ##
============================================
- Coverage 18.94% 18.93% -0.01%
- Complexity 18376 18473 +97
============================================
Files 6192 6221 +29
Lines 556550 560039 +3489
Branches 67954 68285 +331
============================================
+ Hits 105454 106066 +612
- Misses 439517 442347 +2830
- Partials 11579 11626 +47
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness.
|
Sorry, something went wrong.
There was a problem hiding this comment.
This PR adjusts the KVM NAS backup script’s “statistics/cleanup” section so that failures while computing backup disk usage (and related cleanup commands) don’t cause an otherwise successful backup job to be marked as failed.
Changes:
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sorry, something went wrong.
There was a problem hiding this comment.
clgtm
Sorry, something went wrong.
There was a problem hiding this comment.
hi @daviftorres
would it be possible to test script changes in your env where it is reproducible?
Some log outputs would be nice.
Sorry, something went wrong.
Sorry, something went wrong.
|
@abh1sar a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
@abh1sar a [SL] Jenkins job has been kicked to build packages. It will be bundled with no 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 18442 |
Sorry, something went wrong.
|
@abh1sar 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-16468)
|
Sorry, something went wrong.
There was a problem hiding this comment.
code lgtm
Sorry, something went wrong.
…ckup to Fail (apache#13424) (cherry picked from commit f9a9451)
| Back | FazBrowse Home | New Git URL |
Description
This PR tried to prevent the failure of the job at the statistics section of a backup that has actually succeeded.
Apparently, it also fixes some silent failures I previously reported in #11727
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?