framework/spring: throw RuntimeException when fail to start or load a module

[weizhouapache]

Description

This PR fixes the issue that when fail to start cloudstack-management service, there are huge amount of logs which are misleading and difficult to address the root cause.

Steps to reproduce the issue

• use a wrong db username in /etc/cloudstack/management/db.properties, for example

db.cloud.username=wronguser

• restart cloudstack-management service

Prior, there are hundreds of errors like No bean named 'DefaultConfigResources' available

# grep "No bean named 'DefaultConfigResources' available" /var/log/cloudstack/management/management-server.log |wc -l
372

With this change, these errors do not appear. only get few errors like

2026-05-19 06:49:17,187 DEBUG [c.c.u.d.T.Transaction] (main:[]) (logid:) Creating default datasource for database: cloud with connection pool lib: hikaricp
2026-05-19 06:49:17,191 DEBUG [c.c.u.d.T.Transaction] (main:[]) (logid:) Creating default datasource for database: cloud_usage with connection pool lib: hikaricp
2026-05-19 06:49:17,194 DEBUG [c.c.u.d.T.Transaction] (main:[]) (logid:) Creating default datasource for database: simulator with connection pool lib: hikaricp
2026-05-19 06:49:17,196 WARN  [c.c.u.d.T.Transaction] (main:[]) (logid:) Unable to load db configuration, using defaults with 5 connections. Falling back on assumed datasource on localhost:3306 using username:password=cloud:cloud. Please check your configuration com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: Could not create connection to database server. Attempted reconnect 3 times. Giving up.
...

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)
• Build/CI
• Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?

[weizhouapache]

@blueorangutan package

[blueorangutan]

@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]

Codecov Report

❌ Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.
✅ Project coverage is 17.67%. Comparing base (4a49ffa) to head (e9ca574).
⚠️ Report is 3 commits behind head on 4.22.

Files with missing lines	Patch %	Lines
.../module/model/impl/DefaultModuleDefinitionSet.java	0.00%	4 Missing ⚠️
.../spring/lifecycle/CloudStackExtendedLifeCycle.java	0.00%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               4.22   #13186      +/-   ##
============================================
- Coverage     17.67%   17.67%   -0.01%     
  Complexity    15788    15788              
============================================
  Files          5922     5922              
  Lines        533123   533120       -3     
  Branches      65201    65199       -2     
============================================
- Hits          94242    94240       -2     
+ Misses       428237   428235       -2     
- Partials      10644    10645       +1     

Flag	Coverage Δ
uitests	3.69% <ø> (ø)
unittests	18.75% <0.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[blueorangutan]

Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 17906

[weizhouapache]

@blueorangutan test

[blueorangutan]

@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

[winterhazel]

Looks good. I will test.

[winterhazel]

Tested. Way less errors are logged now on a startup failure.

[blueorangutan]

[SF] Trillian test result (tid-16108)
Environment: kvm-ol8 (x2), zone: Advanced Networking with Mgmt server ol8
Total time taken: 81163 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr13186-t16108-kvm-ol8.zip
Smoke tests completed. 144 look OK, 5 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test	Result	Time (s)	Test File
test_vm_backup_create_vm_from_backup	Failure	607.97	test_backup_recovery_nas.py
test_vm_backup_lifecycle	Error	1.28	test_backup_recovery_nas.py
ContextSuite context=TestSharedFSLifecycle>:setup	Error	0.00	test_sharedfs_lifecycle.py
test_10_attachAndDetach_iso	Failure	607.15	test_vm_life_cycle.py
test_01_create_vm_snapshots	Failure	606.77	test_vm_snapshots.py
test_02_revert_vm_snapshots	Failure	600.62	test_vm_snapshots.py
test_03_delete_vm_snapshots	Failure	0.03	test_vm_snapshots.py
test_01_create_volume	Failure	611.68	test_volumes.py
test_01_root_volume_encryption	Failure	698.23	test_volumes.py
test_02_data_volume_encryption	Failure	645.77	test_volumes.py
test_03_root_and_data_volume_encryption	Failure	670.23	test_volumes.py
test_02_attach_volume	Failure	1266.77	test_volumes.py
test_02_attach_volume	Failure	1266.79	test_volumes.py
test_03_download_attached_volume	Failure	661.17	test_volumes.py
test_04_delete_attached_volume	Failure	661.96	test_volumes.py
test_05_detach_volume	Failure	753.92	test_volumes.py
test_06_download_detached_volume	Failure	845.24	test_volumes.py
test_07_resize_fail	Failure	656.63	test_volumes.py
test_08_resize_volume	Failure	666.10	test_volumes.py
test_09_delete_detached_volume	Failure	659.45	test_volumes.py
test_10_list_volumes	Failure	656.54	test_volumes.py
test_11_attach_volume_with_unstarted_vm	Failure	755.65	test_volumes.py
test_12_resize_volume_with_only_size_parameter	Failure	660.15	test_volumes.py
test_13_migrate_volume_and_change_offering	Failure	792.32	test_volumes.py
test_14_delete_volume_delete_protection	Failure	660.70	test_volumes.py