Buildpack Auto detection fails on Elastic Runtime 1.12
search cancel

Buildpack Auto detection fails on Elastic Runtime 1.12

book

Article ID: 297561

calendar_today

Updated On:

Products

VMware Tanzu Application Service for VMs

Issue/Introduction

Symptoms:

When pushing a java application with an empty buildpack attribute. PCF (Pivotal Cloud Foundry) should be able to use auto detection to determine the appropriate buildpack. Pushing an application on PCF 1.12 fails with the following error:

# cf push demo -p . -b null

Creating app demo in org test-org / space test-space as user1...

FAILED

Server error, status code: 400, error code: 100001, message: The app is invalid: Must specify either a buildpack_url or an admin_buildpack_name

 

Environment


Cause

This is a known bug in PCF Elastic Runtime version 1.12 which was fixed on PAS version 2.0 and later.

Resolution

Upgrade to PAS 2.0 and later