Closed abh1sar closed 3 days ago
@blueorangutan package
@abh1sar 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.
Attention: Patch coverage is 27.27273%
with 8 lines
in your changes missing coverage. Please review.
Project coverage is 12.24%. Comparing base (
351de5f
) to head (50e09fe
). Report is 1 commits behind head on 4.18.
Files | Patch % | Lines |
---|---|---|
...n/java/com/cloud/resource/ResourceManagerImpl.java | 0.00% | 7 Missing :warning: |
...cycle/CloudStackPrimaryDataStoreLifeCycleImpl.java | 0.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 10111
@blueorangutan test
@abh1sar a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests
@blueorangutan package
@abh1sar 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]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 10124
[SF] Trillian test result (tid-10612) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 42162 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9301-t10612-kvm-centos7.zip Smoke tests completed. 107 look OK, 3 have errors, 0 did not run Only failed and skipped tests results shown below:
Test | Result | Time (s) | Test File |
---|---|---|---|
test_08_migrate_vm | Error |
45.85 | test_vm_life_cycle.py |
test_01_cancel_host_maintenace_with_no_migration_jobs | Error |
114.46 | test_host_maintenance.py |
test_disable_oobm_ha_state_ineligible | Error |
1513.05 | test_hostha_kvm.py |
test_hostha_enable_ha_when_host_in_maintenance | Failure |
310.26 | test_hostha_kvm.py |
@blueorangutan test
@abh1sar a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests
[SF] Trillian test result (tid-10626) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 41860 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9301-t10626-kvm-centos7.zip Smoke tests completed. 107 look OK, 3 have errors, 0 did not run Only failed and skipped tests results shown below:
Test | Result | Time (s) | Test File |
---|---|---|---|
test_08_migrate_vm | Error |
45.92 | test_vm_life_cycle.py |
test_01_vpc_site2site_vpn | Failure |
279.86 | test_vpc_vpn.py |
test_hostha_enable_ha_when_host_disabled | Error |
3.68 | test_hostha_kvm.py |
test_hostha_enable_ha_when_host_in_maintenance | Error |
302.87 | test_hostha_kvm.py |
test_hostha_kvm_host_recovering | Error |
7.13 | test_hostha_kvm.py |
@blueorangutan test keepEnv
@abh1sar a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests
Working on resolving smoke test failures
codewise lgtm
@abh1sar
what about other resource states, like ErrorInMaintenance
or ErrorInPrepareForMaintenance
, PrepareForMaintenance
?
[SF] Trillian test result (tid-10648) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 45084 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9301-t10648-kvm-centos7.zip Smoke tests completed. 109 look OK, 1 have errors, 0 did not run Only failed and skipped tests results shown below:
Test | Result | Time (s) | Test File |
---|---|---|---|
test_hostha_enable_ha_when_host_disabled | Error |
4.74 | test_hostha_kvm.py |
test_hostha_enable_ha_when_host_in_maintenance | Error |
302.76 | test_hostha_kvm.py |
The approach of ssh-ing into the in-maintenance-host to restart the agent even if the agent was already connected is not right, as it breaks the change done in https://github.com/apache/cloudstack/pull/3239
I think better solution would be to allow createStoragePoolCommand to run on the host in maintenance mode (like ModifyStoragePoolCommand)
@sureshanaparti @kiranchavala
The approach of ssh-ing into the in-maintenance-host to restart the agent even if the agent was already connected is not right, as it breaks the change done in #3239
I think better solution would be to allow createStoragePoolCommand to run on the host in maintenance mode (like ModifyStoragePoolCommand)
@sureshanaparti @kiranchavala
Yes @abh1sar, If the agent is already connected, better check & update the storage pools with agent command.
@blueorangutan package
@abh1sar 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.
codewise lgtm
@abh1sar what about other resource states, like
ErrorInMaintenance
orErrorInPrepareForMaintenance
,PrepareForMaintenance
?
Have changed the approach, so this code is now obsolete. Please check.
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 10184
@blueorangutan test
@abh1sar a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests
[SF] Trillian test result (tid-10670) Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7 Total time taken: 39649 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9301-t10670-kvm-centos7.zip Smoke tests completed. 109 look OK, 1 have errors, 0 did not run Only failed and skipped tests results shown below:
Test | Result | Time (s) | Test File |
---|---|---|---|
test_hostha_kvm_host_fencing | Error |
106.67 | test_hostha_kvm.py |
Description
This PR...
Fixes #9295
When a host is in maintenance, CreateStoragePoolCommand and DeleteStoragePoolCommand are not allowed to execute by the AgentAttache. This will cause a new storage pool to not be present on the host even after it comes out of maintenance, as the cloudstack agent is not restarted when cancel maintain is called (#3239). This also causes a deleted storage pool to never be removed from a host in maintenance.
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?