gCTS in S/4HANA Cloud 2502: “Could Not Verify Content” / “Registered Commits couldn’t be read” Error

[dnnunes97]

Hello SAP Community,

I’m in a multi-off delivery scenario, where I develop ABAP custom code in an SAP S/4HANA Cloud 1-system environment (the source) and then deploy it to an SAP S/4HANA Cloud 3-system environment (the target) using Git-Enabled CTS (gCTS). Concretely, I push commits from the 1-system landscape to a remote Git repository, and then attempt to pull those commits into the 3-system landscape (DEV → TEST → PROD).

Since the S/4HANA Cloud Public 2502 upgrade in our 3-system TEST environment, I can no longer import new commits from my remote Git repositories using Git-Enabled CTS (gCTS). Each time I try to pull a commit, I see:

Could not verify content
The repository was not imported because the content could not be verified. Please contact the repository owner.

And in the technical details:

Error action COMMIT_VERIFICATION Code 411x011: Registered Commits couldn’t be read.

In the gCTS logs (the ones viewable in the gCTS Fiori application), I mostly get “Error when importing commit” without much else. However, looking deeper into the Eclipse ADT Feed, Gateway error logs (OData service SCTS_GCTS_SRV) reveals more specific messages, such as:

{... ,"section": "REPOSITORY", "action": "PULL_BY_COMMIT", "severity": "ERROR", "message": "BAdI 'scts_gcts_enh_deploy' raised exception for 'check_before_import' "}

{"severity":"ERROR", "message": "Error when importing commit.", "code": "GCTS.API.411"}

It seems the COMMIT_VERIFICATION step fails before the import actually begins. This problem started immediately after the 2502 upgrade — previously we had no issues pulling from the same Git repository.

Has anyone seen this error in a multi-off delivery scenario?

• Is there a new verification check in 2502 that might fail if certain commit data, authorizations, or repository settings aren’t in place?
• Could the BAdI scts_gcts_enh_deploy be blocking the import for some reason in check_before_import?
• Are there SAP Notes/KBAs covering a similar error in COMMIT_VERIFICATION with “GCTS.API.411” or “Registered Commits couldn’t be read”?

Environment/Versions

• Source: S/4HANA Cloud Public 1SL (Partner Demo) – version 2408
• Target: S/4HANA Cloud Public 3SL (DEV → TEST → PROD) – Currently failing in TEST version 2502. DEV is still in version 2408, commits are being pulled successfully.
• gCTS for multi-off delivery with a GitHub remote repository

I would appreciate any pointers or workarounds for getting multi-off delivery working again in 2502.

Thank you in advance!

[sergio-oliveira]

We are facing a similar situation. Did you solve it?

When we add the repository, the gCTS App shows the Commits correctly, just like they have been pushed to Git.
We even tried to debug method check_before_import from the mentioned BADI. Apparently it tries to get the Commits from a service at https://userapps.support.sap.com/odata/gcts_commit_reg/CommitSet?$filter=Repository eq '[REPOSITORY_HASH]'. In our case this GET method returns with http status code 200, but the contents of the returned method are empty (in your case, I think you are getting a different http code, so your message is slightly different, but still around the same code block within the mentioned method).

We don't have access to a version 2408 system, so I can't tell if our scenario would work there. We will try to open a support ticket with SAP to see if they can help.

[Karin]

Hi,
some general comments on this issue:

• in Multi-Off, commits can only be pulled in an S/4HANA public cloud system, if they also had been pushed from an S/4HANA Public Cloud system - this applies to all commits in a repository (containing ABAP objects)
• An upgrade of the systems does not 'destroy' the verification - in this case please open a case in component BC-CTS-GIT
• If you pushed (accidentally) something to a repository from a non-S/4HANA public cloud system or created a commit on git directly, please refer also to the question 'When cloning a repository to a target system, I get an error message 'Content Versification failed' with 'Technical Detail: Code411x3: Commit verification for <repoID>failed' ' in the Troubleshooting on the SAP Help Portal. To fix this, you need to create a new commit and create a case on BC-CT-GIT to get your repository fixed.

Kind regards
Karin

[hgioioso]

Hello, we are having same issue! did you get the solution?

thanks.