-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resolve merge problems in the backup framework #10457
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #10457 +/- ##
============================================
+ Coverage 4.00% 16.16% +12.15%
- Complexity 0 13269 +13269
============================================
Files 396 5666 +5270
Lines 32530 498051 +465521
Branches 5766 60259 +54493
============================================
+ Hits 1302 80489 +79187
- Misses 31078 408554 +377476
- Partials 150 9008 +8858
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
api/src/main/java/org/apache/cloudstack/backup/BackupProvider.java
Outdated
Show resolved
Hide resolved
@DaanHoogland my suggestion is, revert VeeamBackupProvider.java and then cherry-pick the commit #9898
|
yes, you are right, but these are rather safe.
What you suggest will not lead to a compiling version without further fixes either, neither starting on main or starting from this branch. The question is if https://github.com/apache/cloudstack/pull/10457/files#diff-35507d9957e6b1b12096c22153fc877ea347a7dd2316a0c670a0c80a6c3da3a4R330-R405 does the job. |
oh, sorry, the commit I pasted was wrong, the correct commit is a8b18a5 which is the last commit before merge forward.
I tried locally, the difference is
|
@winterhazel @weizhouapache , is it correct that we can drop the whole transactional bit in as in pushed changes as @weizhouapache suggested. |
Correct, the transaction was moved to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks ok
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code lgtm
|
thanks guys, As this is a merge forward, I am not sure if we should do a full regression suite on this, especially since the major changes require 3rd party software. What do you think? (packaging is underway) |
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 12561 |
@blueorangutan test |
@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code LGTM
@@ -414,6 +407,11 @@ public boolean willDeleteBackupsOnOfferingRemoval() { | |||
return false; | |||
} | |||
|
|||
@Override | |||
public void syncBackups(VirtualMachine vm, Backup.Metric metric) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
syncBackups has been moved to BackupManagerImpl. Need to remove syncBackups from all providers.
@@ -344,6 +352,23 @@ public List<Backup.RestorePoint> listRestorePoints(VirtualMachine vm) { | |||
return getClient(vm.getDataCenterId()).listRestorePoints(backupName, vm.getInstanceName()); | |||
} | |||
|
|||
private Backup checkAndUpdateIfBackupEntryExistsForRestorePoint(List<Backup> backupsInDb, Backup.RestorePoint restorePoint, Backup.Metric metric) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this method has also been moved along with syncBackups to BackupManagerImpl. can be removed from here
@@ -328,54 +328,12 @@ public Map<VirtualMachine, Backup.Metric> getBackupMetrics(final Long zoneId, fi | |||
|
|||
@Override |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please restore the code in createNewBackupEntryForRestorePoint and listRestorePoints, and delete code from syncBackups
Up to you guys, but I think we should we should be good already, as the tests that involve the only change here that could affect something already passed on #10017. |
[SF] Trillian test result (tid-12491)
|
Description
This PR solves merge problems in the backup framework and providers.
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?