Open BartJM opened 2 weeks ago
Attention: Patch coverage is 0%
with 3 lines
in your changes missing coverage. Please review.
Project coverage is 15.80%. Comparing base (
8af08dd
) to head (c460198
). Report is 35 commits behind head on main.
Files with missing lines | Patch % | Lines |
---|---|---|
...n/java/com/cloud/resource/ResourceManagerImpl.java | 0.00% | 3 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
🚨 Try these New Features:
@blueorangutan package
@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.
Packaging result [SF]: ✖️ el8 ✖️ el9 ✖️ debian ✖️ suse15. SL-JID 11525
Packaging result [SF]: ✖️ el8 ✖️ el9 ✖️ debian ✖️ suse15. SL-JID 11525
this seems to have to do with github api limits. trying a build in the background.
Description
This PR adds the host preparing for maintenance to the avoid list for the deployment planner.
Without adding the host to the avoid list the deployment planner will return the host preparing for maintenance when a vm has a local storage root disk and has the host preparing for maintenance as the last host.
Steps to reproduce
Actual behaviour
Expected
Local storage vm live migrated to another host.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Centos8 mbx env with
host.maintenance.local.storage.strategy
set to Migration.Tested maintenance mode on a host with
5 and 6 result in an ErrorInMaintenance due to dest being null. Similar as described in https://github.com/apache/cloudstack/issues/9887. Without this patch these would still fail with the same error as described in actual behavior.
After creation of a ha vm with ha data disk maintenance was not possible. After manual migration to another host and back, migration did complete. Migration without selecting host also gave a no destination found error and also occurred without this patch so is unrelated.
How did you try to break this feature and the system with this change?