Support Request – Deployment Build Failure (Cloud Foundry Deploy) – Job #5049

I need your support to resolve a deployment failure occurring in our Deploy_from_Nexus Jenkins pipeline.Job & Repository Details

Pipeline Job:
Deploy_from_Nexus – Build #5049
https://excisetax.jaas-gcp.cloud.sap.corp/job/Deploy_from_Nexus/5049/console

Repository:
https://github.wdf.sap.corp/EXCISETAX/ExciseTax/tree/ifs_cap4_springboot
Branch:
ifs_cap4_springboot`

Attached Log File: console_log_5049.txt
Recent Technical Changes

As part of our ongoing upgrade, we recently upgraded all CDS/CAP dependencies to CDS 9.x, specifically:

"@sap/cds": "9.6.4",
"@sap/cds-dk": "9.6.1",
"@sap/cds-mtxs": "3.6.2"

Summary of Deployment Failure

The pipeline consistently fails during the Cloud Foundry deploy step:
[cloudFoundryDeploy] Step execution failed.
Error: running command 'cf' failed: exit status 1
This happens even after 3 automatic retries of:

cf deploy target/Excise_Tax.mtar -f --version-rule ALL -e assembly/mta_extensions/canary.mtaext

Critical Issues Identified in the Log**

1. xs-security.json Parsing Error – UAA Update Fails**

The deployment fails while updating the service Excise_Tax-admin-uaa:

Error parsing xs-security.json:
Unrecognized field "grant-as-authority-to-apps"

This field appears to be unsupported by SAP Cloud Foundry UAA and causes:

• Failure to update the admin UAA instance
• Potential cascading failures in dependent applications

2. Application Startup Failure – mtx-sidecar

The mtx-sidecar application fails to start during deployment:
Error starting application "mtx-sidecar": Some instances have crashed.

failure console log: console_log5049.txt

versions:

I kindly request your support to help resolve this issue. Please let us know if any additional information or configuration is required.
Thank you for your support.

Start with the provided Build #5049 console log and the cf deploy target/Excise_Tax.mtar command, focusing on the xs-security.json parsing error and the mtx-sidecar crash. No repository file or test is named; done would require determining whether the failure is in the Cloud Foundry CLI and providing a reproducible, actionable diagnosis.