Redis Tile: The service broker does not support upgrades for service instances created from this plan
search cancel

Redis Tile: The service broker does not support upgrades for service instances created from this plan

book

Article ID: 295149

calendar_today

Updated On:

Products

Redis for VMware Tanzu

Issue/Introduction

The Upgrade All Service Instances errands fails with the error:
response body "{\n \"description\": \"The service broker does not support upgrades for service instances created from this plan.\",\n \"error_code\": \"CF-MaintenanceInfoNotSupported\",\n \"code\": 390006\n}\n"
Stderr Error: failed to run job-process: exit status 1 (exit status 1)

The error occurs if, during the upgrade, the Register On-Demand Broker errand has not been run. 

1. The error is raised by the Cloud Controller here. It will be raised when the following two cases are true:
 
  • CAPI receives a Service Instance update request with maintenance info in the body
  • The service broker catalog, as it’s known by CAPI, doesn’t have maintenance_info set for the plan.
2. Redis < 2.3 does not support the Single Instance Upgrade functionality. It’s can be enabled for Redis >= 2.3.0.
 
  • The platform achieves Single Instance Upgrade through the maintenance_info property for the service plan in the service catalog.
  • That means that on Redis >= 2.3.0, maintenance_info is set on the ODB configuration.
3. When running the errand, ODB will verify the presence of maintenance_info in its configuration to determine if it should trigger upgrades via CF. This means that if there’s a mismatch between what the broker is configured with and what CF knows about, we’ll get the error defined above.


Environment

Product Version: 2.1

Resolution

Make sure that the Service broker catalog and the CF service catalog are in sync. This is achieved by running the Register On-Demand Broker errand and then Upgrade All Service Instances errand to make sure error is gone.


Note: This resolution applies to Redis >= 2.3.x and to MySQL >= 2.8.x.

Run the following errands in this order:

1. Register On-demand Broker

2. Upgrade all On-demand Service Instances