3.0 KiB
3.0 KiB
FIX-aviator-capability-on-BO-UI_688988251
Introduction
When the deploy status of Aviator capability is not done, the enable requset has been sent, it will cause the BO UI is not correct display. It is all OK except the BO UI. We will prevent the issue in our code in Release 24.4.
This document explains how to correct the data in this issue tenant.
Steps
- Login in the issue tenant with the tenant admin, switch to https://<ESM_FQDN>/sap/rest-client?TENANTID=804874389
- Send the GET request with URL common-settings/setting/OT_AI_CONFIG.
- You will get the result as bellow: { "OT_AI_CONFIG": "{\"llmEndpoint\":\"....\",\"tenantId\":\"XXXXXXX\"}" } The tenantId will be used in the steps 7.
- Go to the SMAX bastion server, then execute the command to login in the itom-bo-ats-deployment-xxx-xxx
kubectl exec -it itom-bo-ats-deployment-xxxxxx -c itom-bo-ats -n bash
-
- Get the dba password by "get_secret itom_itsma_dba_password_secret_key"
2. Login in to the pg in bo-ats db with psql.
3. execute the sql as bellow:
- Get 1 record with no llmTenantId in properties and status=0: SELECT * FROM "bo_db_user".tenant_capability WHERE tenant_id = <TENANT_ID> AND type = 6; 2. Update the LLM capability status to DONE: UPDATE "bo_db_user".tenant_capability SET status = 2 WHERE tenant_id = <TENANT_ID> AND type = 6; 3. Update set the LLM capability tenant id: UPDATE "bo_db_user".tenant_capability SET properties = jsonb_set(properties, '{llmTenantId}', '"<LLM_TENANT_ID in step 3>"') WHERE tenant_id = <TENANT_ID> AND type = 6; 4. Double check the llmTenantId in properties and status=2: SELECT * FROM "bo_db_user".tenant_capability WHERE tenant_id = <TENANT_ID> AND type = 6;
- Get the dba password by "get_secret itom_itsma_dba_password_secret_key"
2. Login in to the pg in bo-ats db with psql.
3. execute the sql as bellow:
Check in the BO UI
Login to the BO UI with suite-admin, you can see the data is back to normal.
Attachments:
image2024-7-16_16-21-2.png (image/png)