GitLab Content Pipeline Checkin fails with "Error: Failed to get files in repository 404 Not Found"

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Unable to checkin new content from Aria Suite Lifecycle Manager to GitLab.

Environment

When we run a Content Pipeline test to Gitlab it fails with the following:

{"summaryMessage":"Failed to deploy contents","failures":[

{"errorMessage":"Failed to deploy the content : <contentName> to the endpoint: <SCM endpoint name>, Error: Failed to commit, Error: Failed to get files in repository [<path-to-project] details=404 404 Not Found url=[https://<gitlab-fqdn>/api/v4/projects/<projectId>/repository/tree?ref=main&recursive=true&path=Automation-CustomResource%2F<contentName>%2Fcustom-resource]"}

Cause

Since GitLab 17.7 there was an API change introduced which changed the behaviour of the repository API when a requested path was not found. Prior to 17.7 the API returned a status_code 200 and an empty reponse, now it returns a status_code 404

(see more details here -  https://docs.gitlab.com/api/repositories/)

Currently unable to checkin new content from Aria Suite Lifecycle to a GitLab repository due to this behaviour.

Resolution

The fix will be available in the release 8.18 Patch-2.

To resolve the issue, please replace the Jar file with the one provided in this KB.

Replace the jar file:

Steps to apply the jar :

Take a snapshot of the LCM Appliance.
Replace the existing jar file in the below location with the jar file attached to this KB.

# /opt/vmware/vlcm/blackstone/spring-common

Restart the service with the command

systemctl restart blackstone-spring

Try to add the endpoint again.