Upgrade-all-instances errand fails with "the service instance could not be found" error.

Products

• Support Only for Spring

Issue/Introduction

Spring Cloud Service (SCS) Upgrade-all-instances errand fails with the service instance could not be found error message.

install_log.txt shows the following error:
 

2022-12-06 02:28:41.842 DEBUG 7 --- [ctor-http-nio-4] cloudfoundry-client.response             : 404    /v2/service_instances/d5b42145-a174-4b20-a651-2dd0442a0f52 (41 ms)  
           2022-12-06 02:28:41.855 ERROR 7 --- [           main] i.p.s.c.s.errand.BrokerErrandCli         : Errand failed  
             
org.cloudfoundry.client.v2.ClientV2Exception: CF-ServiceInstanceNotFound(60004): The service instance could not be found: d5b42145-a174-4b20-a651-2dd0442a0f52  
           	at org.cloudfoundry.reactor.util.ErrorPayloadMappers.lambda$null$0(ErrorPayloadMappers.java:49) ~[cloudfoundry-client-reactor-5.7.0.RELEASE.jar!/:na] 

 

Background

The error CF-ServiceInstanceNotFound(60004): The service instance could not be found is related to a known issue for the Spring Cloud Service tile where deleted service instances were causing the errand to exit with failure and the Engineering team addressed it. Any release prior SCS 3.1.40 contains this behavior, the SCS release notes have briefly added a mention of it.

Environment

Product Version: 3.1

Resolution

Upgrade SCS to 3.1.40.