How to resolve "Service broker error: this service instance is outdated" when running cf update-service
Article ID: 453969
Updated On:
Products
Issue/Introduction
When running the cf update-service command, the process fails with the following error: Service broker error: The service broker has been updated, and this service instance is out of date. Please contact your operator.
Cause
This error occurs when a service broker tile is upgraded, but the necessary upgrade errands were not fully executed or registered. As a result, the service broker and the existing service instance have a version mismatch, causing the service instance to be marked as "outdated" and rejecting update operations.
Resolution
To resolve this mismatch, you must ensure that the service instances are synchronized with the new broker version. Follow these steps:
Select the Upgrade Errand: Navigate to the Ops Manager configuration for the service tile (e.g., Tanzu for Postgres, MySQL, etc.).
Run the Register and Upgrade Errands: Select the errand responsible for registering the broker (typically named "Register Broker" or similar) and the errand that upgrades service instances ("Upgrade All On-Demand Service Instances"). These errands trigger the necessary updates to sync all existing service instances with the current broker's version.
Apply Changes: Perform an "Apply Changes" operation on the tile to execute the errand.
Verify and Retry: Once the "Apply Changes" process completes successfully, retry the original command:
cf update-service <SERVICE_INSTANCE_NAME> -c '<CONFIGURATION_OPTIONS>'
If the error persists after executing this errand, verify that the "Register Service Broker" errand was selected during the deployment process, as this is often required in tandem to ensure the broker catalog is fully updated.
Additional Information
Feedback
