MTX ERROR: While creating an HDI container in HANA

[sandeep_mekala]

Hi All

Started getting the following error when a new tenant getting subscribed to our cap application in mtx sidecar application. Looks this is coming while creating a hdi container using service manager. Mostly, looks like CAP/service manager is failing some thing related to HANA cloud native tenants enhancement. Any idea how to fix this?

2023-05-16T23:34:01.14+0530 [APP/PROC/WEB/0] ERR Root Cause: Failed provisioning request context: map[container_id:3479c4ce-0f16-40d8-b245-d37639694976 crm_customer_id: global_account_id:3ff4ed93-96a2-4975-8030-006eae3a2f52 instance_annotations:map[] instance_name:QU93akOM6eNtX2oqReHuk7qKtOwTW7wocfbeX5SJk7o= landscape_label:cf-eu10-canary license_type:SAPPROD organization_annotations:map[] organization_guid:fec18f28-67c3-4c1f-b9d2-1c5f978d2c3d organization_name:slhacrdev origin:cloudfoundry platform:sapcp region:cf-eu10-canary service_instance_id:1918ccbf-dba5-4f83-935d-8e55b7db11ae signature:Z0xdYcNkIVnq8nxJt5KZki7q5qAIJKYWgYQw/Bm8YJeDDW0WdfAd/ze3Cy5IPtXfXBGXW3vSg/QSHm2+A5WqnTS1XC9l7WeDtnM3UkNmrBQa64LQPCL9rBDWqqfE3YxEcQzt76J8YT61Tak6CdJS7jlOVya3vExYi5YNunBN8ptCwgb4UDTecEBUHFMNHe+bova/YnFDhLhsyNbXPkp2xp6Mejaf9tZkJqtBTGFJ07BG8LlgFxoK5UsfoDHItXPQze9uBJN6x/g2/HV4WB0MZvN4SFu7E6IjB6PYsO7AsHq47rilvUnKvIhohhQD/KKBjVQB2NBhz71ZTou6cuBW+apLFCj7Z8shLk/wR1D/iXs//5FFwebKm0kkoNfmARuaUGgPRJQei//oKYYzTxaYkn75FENNLRHDdTFcXh/JWMT7M7wDwPQvbrMTnAeZN687lR+YWnUGIJ25fSDfMLWO/HT6eSvixFh/8gIAsiLmc8KXcdYgZ1cNJHHzet0hKFdpb+A39n/dJx1MgPb/rQfiB68DvnTEhJEHgW9KN/5FdKKRgvX0JqEF/3fHnAXpubx1E3tc0VM1ytfGiGpniKXiwIauwXlfc4ile/94XjZQXXx9pLegrVF9x1x+kTXelLarqfzmbGF+tatXdMMohTAJDwDqxQy0tnHhiz8muLx4rdc= space_annotations:map[] space_guid:addbc3e0-3386-42ef-9f80-9792f858de33 space_name:acrsspace subaccount_id:5ecd41ca-383a-4de0-8cac-0580088d99b0 subdomain:slhacrdev zone_id:5ecd41ca-383a-4de0-8cac-0580088d99b0], instanceID: 1918ccbf-dba5-4f83-935d-8e55b7db11ae, planID: bebaad3e-352b-4928-bc6b-8783d754ac3b, serviceID: 79d9e11a-95c2-4771-ae2d-8ba703bd8fda, acceptsIncomplete: true: Status: 400; ErrorMessage: <nil>; Description: the parameters dataEncryption and subscriptionContext can only be used when enableTenant is true : ; ResponseError: <nil>

Thank you

Sandeep Mekala

[sandeep_mekala · Accepted solution]

It is issue with HANA service broker.

https://jira.tools.sap/browse/NGPBUG-354665

[sandeep_mekala]

Hi Amin

Thank you for quick response. We are not handling of provisioning of HDI containers for each tenant. I guess, it is handled by CAP default handler. Any idea if any parameters need to be enabled in our CAP application environment to influence this behaviour?

Thank you

Sandeep Mekala

[Amin_Omidy]

Hi Sandeep,

The error message indicates that there is an issue with provisioning a new tenant in your CAP (SAP Cloud Application Programming Model) application using the service manager. It appears to be related to HANA cloud native tenants enhancement and specifically mentions a problem with the parameters "dataEncryption" and "subscriptionContext" when the "enableTenant" flag is not set to true.

To fix this issue, you may need to ensure that the "enableTenant" flag is set to true when provisioning a new tenant. Additionally, make sure that you provide valid values for the "dataEncryption" and "subscriptionContext" parameters, if they are required for tenant creation.

Here are the possible suggested steps to resolve the problem:

1-Check the provisioning code: Review the code responsible for provisioning new tenants in your CAP application. Look for the place where the service manager is used to create the tenant and verify that the "enableTenant" flag is correctly set to true.

2-Validate parameter values: Ensure that any additional parameters required for tenant creation, such as "dataEncryption" and "subscriptionContext," are provided with valid values according to the requirements of your application and the service manager.

Retry the tenant creation: Once you have made the necessary adjustments to the code and parameter values, try to create a new tenant again and see if the issue is resolved. Monitor the logs and error messages for any further indications of problems during the provisioning process.

If the problem persists or if you need further assistance, it might be helpful to provide more details about the specific CAP version, service manager version, and any relevant configuration files or code snippets related to the tenant provisioning process.

Thanks,

Amin