Scheduler v2.0.12 installation deploy-scheduler errand fails with java buildpack 4.74.0

Products

VMware Tanzu Application Service

Issue/Introduction

When installing scheduler tile version 2.0.12 with java buildpack 4.74.0, users could get failed on 'deploy-scheduler' errand.

The error message looks like:

+ cf push scheduler-new -f /var/vcap/jobs/deploy-scheduler/scheduler-manifest.yml -i 1 --no-route -s cflinuxfs4

Instances starting...

++ cf app scheduler-new

++ grep '#0'

++ awk '{print $2}'

+ app_state='v4.74.0-offline-https://github.com/pivotal-cf/java-buildpack#0c1df05

running'

+ popd

+ [[ v4.74.0-offline-https://github.com/pivotal-cf/java-buildpack#0c1df05

running != \r\u\n\n\i\n\g ]]

+ exit 1

Environment

Scheduler 2.0.12

Jave buildpack 4.74.0

Cause

app_state uses 'grep “#0”' as a filter. Normally, it only filters out the state of an app. But as the 4.74.0 java buildpack URL "4.74.0-offline-https://github.com/pivotal-cf/java-buildpack#0c1df05" contains "#0", it filters out both the app_state and the buildpack URL, and therefore causes the app state matching error.

Resolution

The issue was fixed in the below version:

Scheduler v2.0.13:
- [Bug Fix] Fix for deploying on Java buildpack 4.74.0