Mirror syncs fail for config servers across multiple foundations

Products

• VMware Tanzu Application Service

Issue/Introduction

Multiple foundations with Spring Cloud Service config servers saw their mirror syncs fail in the same time period. No changes had been made to the platform.

Environment

SCS 3.2.5

TAS 6.0.12

Resolution

Collect the spring-cloud-services VM logs from each affected SCS deployment:

bosh -d <scs-deployment> logs spring-cloud-services

In each environment, the mirror-service.stdout.log file contained similar errors, each referring to the same source control repository:

2025-06-11T10:46:59.135Z  INFO 7 --- [   scheduling-1] i.p.s.c.mirrorservice.mirrors.ShellUtil  : error: cannot lock ref 'refs/heads/feature/repo-name/MY_REPO': 'refs/heads/feature/repo-name' exists; cannot create 'refs/heads/feature/repo-name/MY_REPO'

 

The error of this type (cannot lock ref 'path': 'repo-path' exists; cannot create 'path') can occur when a repository has been deleted and recreated with the same name.

The mirror service can be re-initialized by restarting the service; after restarting, the error should cease. To restart the service, 'bosh ssh' to the spring-cloud-serices VM and run these commands:

sudo -i

monit restart mirror-service