"Error: Failed to commit, Error: null" message when attempting to capture content and commit to git repository in vRealize Suite Lifecycle Manager 8.10
search cancel

"Error: Failed to commit, Error: null" message when attempting to capture content and commit to git repository in vRealize Suite Lifecycle Manager 8.10

book

Article ID: 322705

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • Attempts to commit content to git repositories fail with error:

{"summaryMessage":"Failed to capture contents","failures":[{"errorMessage":"Failed to deploy the content : <ContentName> to the endpoint: <GitLab Endpoint>, Error: Failed to commit, Error: null"}]}
 

  • The /var/log/vrlcm/blackstone-spring.log file contains a null value for changes_count property and errors similar to:
2023-04-11 12:03:21.536  INFO <vRSLCM FQDN> --- [ContentAsync-17] c.v.b.s.g.GitLabServiceImpl              [approveMerge] : gitlab response for merge : {"id":1234,"iid":296,"title":"[Request=1304][Reference Hash=develop][Commit message=]","target_branch":"develop","source_branch":"vLCM_Content_Req_1304_b034xxxx-xxxx-xxxx-0000-yyyyyyyyyyyy_1","state":"opened","merge_status":"checking","remove_source_branch":false,"should_remove_source_branch":false,"changes_count":null}
2023-04-11 12:03:21.536 ERROR <vRSLCM FQDN> --- [ContentAsync-17] c.v.b.s.g.GitLabServiceImpl              [approveMerge] : exception when getting merge detailsnull
2023-04-11 12:03:21.536 ERROR <vRSLCM FQDN> --- [ContentAsync-17] c.v.b.s.g.GitLabServiceImpl              [approveMerge] : error : [Ljava.lang.StackTraceElement;@50f4a024
2023-04-11 12:03:21.537  INFO <vRSLCM FQDN> --- [ContentAsync-17] c.v.b.s.g.GitLabServiceImpl              [lambda$deleteDevBranchesOnFailure$16] : Deleting the branch on failure: https://<GitLab FQDN>/api/v4/projects/58/repository/branches/vLCM_Content_Req_1304_b034xxxx-xxxx-xxxx-0000-yyyyyyyyyyyy_1
2023-04-11 12:03:21.537  INFO <vRSLCM FQDN> --- [ContentAsync-17] c.v.b.s.g.GitLabServiceImpl              [lambda$deleteDevBranchesOnFailure$16] : branch url : https://<GitLab FQDN>/api/v4/projects/58/repository/branches/vLCM_Content_Req_1304_b034xxxx-xxxx-xxxx-0000-yyyyyyyyyyyy_1

2023-04-11 12:03:21.809 ERROR <vRSLCM FQDN> --- [ContentAsync-17] c.v.b.s.g.GitLabServiceImpl              [commit] : Failed to commit
com.vmware.blackstone.exception.ClientErrorException: exception when getting merge details details=null url=[https://<GitLab FQDN>/api/v4/projects/58/merge_requests/296/changes]
            at com.vmware.blackstone.scm.gitlab.GitLabServiceImpl.approveMerge(GitLabServiceImpl.java:1684)
            at com.vmware.blackstone.scm.gitlab.GitLabServiceImpl.commit(GitLabServiceImpl.java:677)
            at com.vmware.blackstone.services.sourcecontrol.SourceControlExecutorService.executeCommitProvider(SourceControlExecutorService.java:299)
...
            at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException
            at com.vmware.blackstone.scm.gitlab.GitLabServiceImpl.approveMerge(GitLabServiceImpl.java:1654)
            ... 15 more


Environment

VMware vRealize Suite Lifecycle Manager 8.10.x

Cause

The changes_count field type in the Git response is referenced in Lifecycle Manager as integer type but the value is being sent by Git as type string.

Resolution

The issue is resolved in the Aria Suite Lifecycle 8.12 release.