upgrade: skip the upgrade paths which are not needed#12881
upgrade: skip the upgrade paths which are not needed#12881weizhouapache wants to merge 2 commits intoapache:4.20from
Conversation
|
@blueorangutan package |
|
@weizhouapache 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 Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 4.20 #12881 +/- ##
=========================================
Coverage 16.25% 16.25%
+ Complexity 13415 13413 -2
=========================================
Files 5664 5664
Lines 500465 500467 +2
Branches 60780 60780
=========================================
+ Hits 81338 81341 +3
+ Misses 410031 410030 -1
Partials 9096 9096
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 17232 |
|
@blueorangutan test |
|
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
abh1sar
left a comment
There was a problem hiding this comment.
Thanks @weizhouapache. Looks good.
It's better to fix this logic rather than adding an upgrade path which does nothing.
Do you think we should still make sure that all the queries in the upgrade path are idempotent?
INSERT IGNORE INTO cloud.configuration_group (name, description, precedence) VALUES ('Usage Server', 'Usage Server related configuration', 9);
from https://github.com/apache/cloudstack/pull/12875/changes
yes @abh1sar |
Description
This PR provides an alternative solution as #12875
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?