Environment
Description
When enabling the new Veeam Control Service (integration.veeam.control.enabled=true), the CloudStack Management Server fails to start the Veeam Control API service.
The failure is caused by a missing database table:
Table 'cloud.management_server_details' doesn't exist
The Veeam Control Service continues to load, but the API server itself is not started.
Relevant Log Output
ERROR [o.a.c.v.VeeamControlServiceImpl]
Failed to start Veeam Control API server, continuing without it
com.cloud.utils.exception.CloudRuntimeException:
Unable to find on DB, due to:
Table 'cloud.management_server_details' doesn't exist
Stack trace references:
org.apache.cloudstack.veeam.VeeamControlServer.startIfEnabled(VeeamControlServer.java:83)
org.apache.cloudstack.veeam.VeeamControlServiceImpl.start(VeeamControlServiceImpl.java:114)
Investigation Performed
Veeam Control Service classes are present
The package contains the Veeam Control Service implementation:
org/apache/cloudstack/veeam/VeeamControlServiceImpl.class
org/apache/cloudstack/veeam/VeeamControlServer.class
It also contains:
com/cloud/cluster/dao/ManagementServerHostDetailsDao.class
com/cloud/cluster/dao/ManagementServerHostDetailsDaoImpl.class
which appear to require the missing table.
No schema definition found
We searched all delivered SQL and schema files:
grep -Rni "management_server_details" \
/usr/share/cloudstack-management/setup \
/usr/share/cloudstack-management/lib \
/usr/share/cloudstack-common
Result:
We also searched specifically for table creation statements:
grep -Rni "CREATE TABLE.*management_server_details" \
/usr/share/cloudstack-management/setup
Result:
Expected Behaviour
When Veeam Control Service is enabled the service should start successfully and all required database objects should be available through either:
- create-schema.sql (fresh install), or
- an upgrade migration script.
Actual Behaviour
The service fails to start because the required table does not exist and no schema migration appears to be provided.
Questions
- Is management_server_details intentionally omitted from the current Lemur build?
- Is there a missing schema migration or upgrade script?
- Can you provide the expected DDL for this table?
- Is this a known issue in the current Lemur preview packages?
Thank you.
Environment
Description
When enabling the new Veeam Control Service (integration.veeam.control.enabled=true), the CloudStack Management Server fails to start the Veeam Control API service.
The failure is caused by a missing database table:
The Veeam Control Service continues to load, but the API server itself is not started.
Relevant Log Output
Stack trace references:
Investigation Performed
Veeam Control Service classes are present
The package contains the Veeam Control Service implementation:
It also contains:
which appear to require the missing table.
No schema definition found
We searched all delivered SQL and schema files:
grep -Rni "management_server_details" \ /usr/share/cloudstack-management/setup \ /usr/share/cloudstack-management/lib \ /usr/share/cloudstack-commonResult:
We also searched specifically for table creation statements:
grep -Rni "CREATE TABLE.*management_server_details" \ /usr/share/cloudstack-management/setupResult:
Expected Behaviour
When Veeam Control Service is enabled the service should start successfully and all required database objects should be available through either:
Actual Behaviour
The service fails to start because the required table does not exist and no schema migration appears to be provided.
Questions
Thank you.