Scheduler v1.6.3+ push-apps errand failing

Products

Operations Manager

Issue/Introduction

When upgrading Scheduler tile to v1.6.3+, deploy-scheduler errand fails with error message:

+ cf push scheduler-new -f /var/vcap/jobs/deploy-scheduler/scheduler-manifest.yml -i 1 -n scheduler-new -d run-28.slot-35.#####-###-####.#######.com -s cflinuxfs3  
           Deprecation warning: Use of the '-d' command-line flag option is deprecated in favor of the 'routes' property in the manifest. Please see https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-attributes.html#routes for usage information. The '-d' command-line flag option will be removed in the future.  
             
           Start unsuccessful  
             
           TIP: use 'cf logs scheduler-new --recent' for more information  
           ++ cf app scheduler-new  
           ++ grep '#0'  
           ++ awk '{print $2}'  
           + app_state=crashed  
           + popd  
           + [[ crashed != \r\u\n\n\i\n\g ]]  
           + exit 1  
             

1 errand(s)

Errand 'deploy-scheduler' completed with error (exit code 1)

Exit code 1

The above error indicates the errand fails but does not reveal why, therefore we need to go to the scheduler-new app logs to find any relevant information about the failure. To do this we can target we can target the system org and scheduler space and review the recent logs for the scheuler-new application. This KB is specific to the following error message:

2023-04-01T15:21:36.24-0400 [APP/PROC/WEB/0] OUT 19:21:36.238 [main] ERROR org.springframework.boot.SpringApplication - Application run failed
2023-04-01T15:21:36.24-0400 [APP/PROC/WEB/0] OUT java.lang.IllegalStateException: Exiting the application since the Spring Cloud Connector library has been detected on the classpath.  Please remove this dependency from your project and set the environment variable JBP_CONFIG_SPRING_AUTO_RECONFIGURATION '{enabled: false}' in the Cloud Foundry manifest.

This error happens due to buildpack changes involving Deprecation of Spring Cloud Connectors & Spring Auto Reconfiguration. For more info about these changes, please see this KB. To work around this errand failure we can ensure a compatible buildpack is in place while errands run.

Environment

Product Version: 2.10

Resolution

Target the env that is being used to deploy Scheduler with cf CLI.
Check to see what java_buildpack_offline is being utilized in that environment by using command: cf buildpacks.
Locate java_buildpack_offline. If this buildpack is below v4.49 the Scheduler deployment errands may result in error.
Fix: Ensure that java_buildpack_offline is pointed v4.49+ in order to allow errands to succeed.

**Note: Compatible buildpack versions are found in the Scheduler release details on Tanzu.net. Documentation for updating buildpacks can be found here.