Maintenance_Info Does Not Match The Catalog
search cancel

Maintenance_Info Does Not Match The Catalog

book

Article ID: 298389

calendar_today

Updated On:

Products

VMware Tanzu Application Service for VMs

Issue/Introduction

Customers may run into issues creating service instances (Mysql, Redis, etc) due to the below error message which can be found in the broker logs. The below example is from a failed creation of a Redis instance.

broker.stout.log
{"timestamp":"1678121803.305308104","source":"on-demand-service-broker","message":"on-demand-service-broker.provision.maintenance-info-conflict","log_level":2,"data":{"correlation-id":"deb30095-afb5-4824-5077-95930059d989","error":"passed maintenance_info does not match the catalog maintenance_info","instance-details":{"service_id":"13560975-3F2C-44E8-B1F4-FDADF89CCB93","plan_id":"05491E77-4B47-49D3-97FE-3E8E2B02F905","organization_guid":"17c4d920-71c7-4672-8a09-015717d5adf9","space_guid":"a32ffd4e-d4fe-4fcc-9f66-657ce2ff8aff","context":{"platform":"cloudfoundry","organization_guid":"17c4d920-71c7-4672-8a09-015717d5adf9","space_guid":"a32ffd4e-d4fe-4fcc-9f66-657ce2ff8aff","organization_name":"pma","space_name":"puma-data-service-dev","organization_annotations":{},"space_annotations":{},"instance_name":"pas_test","instance_annotations":{}},"maintenance_info":{"version":"2.4.5-build.1"}},"instance-id":"5d6b3450-fa67-4be7-a685-17b135b68594","requestIdentity":"ca9ba2eb-e3b9-46a2-bb68-54cb1f42c0e8","session":"1326"}}

The maintenance_info is the current semantic version of the service plan which is used to determine whether or not the service instance is up to date with the service plan. In the error message, you can see the version is 2.4.5-build.1.

https://docs.vmware.com/en/On-Demand-Services-SDK-for-VMware-Tanzu/0.42/on-demand-services-sdk/GUID-tile.html#optional-configure-maintenance-information-8

The correct version can be found in the broker manifest or by curling the /catalog endpoint. Below is an example of the correct version which is defined in the service_catalog section of the broker manifest.
 
global_quotas:
   service_instance_limit: 85
id: 13560975-3F2C-44E8-B1F4-FDADF89CCB93
maintenance_info:
   version: 3.1.3-build.2
metadata:
   display_name: Redis On-Demand

https://github.com/pivotal-cf/on-demand-service-broker/blob/main/broker/catalog.go#L102



Environment

Product Version: 2.12

Resolution

In order to update the maintenance_info, the customer has 3 options:

1. Run an apply change with the register-broker errand selected. This enables access to plans in the service catalog and updates Cloud Foundry with the new metadata.

2. Run the register-broker errand manually via bosh
bosh -d DEPLOYMENT-NAME run-errand register-broker
3. Update the broker using CF CLI
cf update-service-broker SERVICE_BROKER USERNAME PASSWORD URL