App Binding Fails with Upstream HTTP Error 422 - Tanzu Hub

Products

• VMware Tanzu Platform - Hub

Issue/Introduction

Binding an application to a service instance fails during the BindServiceWorkflow. The user interface or task log displays the following error message:

Error: Upstream HTTP Error: 422, Could not invoke operation POST /v3/service_credential_bindings

Environment

Tanzu Hub (versions prior to11.0)

Cause

The target service instance is in a failed provisioning or lifecycle state. Platform rules prevent binding applications to failed service instances. When the bind operation attempts to connect to an unhealthy service instance, a 422 Unprocessable Entity error returns.

Resolution

To resolve this issue, perform the following steps:

1. Check the status of the target service instance in the platform console or command-line interface.
2. Confirm the service instance status shows as failed.
3. Delete the failed service instance.  
4. Review the service broker and gateway application logs to identify the root cause of the initial provisioning failure as explained in KB article How to troubleshoot Spring Cloud Gateway for VMware Tanzu.
5. Deploy a new service instance and verify the status reports as successful.
6. Retry binding the application to the new, healthy service instance.

 

Additional Information

Review task execution details and error origins within the Hub Tasks interface at URLs following this format: https://<Tanzu Hub UI url>/hub/tasks/details/####