Stuck service operations recovery - #681
Draft
kathap wants to merge 4 commits into
Draft
Conversation
Expose service_operations_update_in_progress_cleanup.frequency_in_seconds as a configurable BOSH property in the clock job, defaulting to 1 hour, mirroring the existing create cleanup property.
…tions_update_stuck_in_progress_failed
Expose the frequency of the new stuck service-delete retry clock job as a configurable BOSH property (default 3600s), and render it into the cloud_controller_ng.yml config.
5 tasks
kathap
marked this pull request as draft
August 14, 2026 09:39
Expose cc.service_operations_binding_delete_stuck_in_progress_retry.frequency_in_seconds and render it into the clock config.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Expose configurable BOSH properties in the cloud_controller_clock job for the three new stuck-operation recovery jobs
A short explanation of the proposed change:
Adds three configurable BOSH properties for the
cloud_controller_clockjob, each defaulting to 1 hour (frequency_in_seconds), controlling how often the corresponding new periodic jobs run:cc.service_operations_update_stuck_in_progress_failed.frequency_in_seconds—the
ServiceOperationsUpdateStuckInProgressFailedjob.cc.service_operations_delete_stuck_in_progress_retry.frequency_in_seconds—the
ServiceOperationsDeleteStuckInProgressRetryjob (service instances).cc.service_operations_binding_delete_stuck_in_progress_retry.frequency_in_seconds—the
ServiceOperationsBindingDeleteStuckInProgressRetryjob (bindings & keys).An explanation of the use cases your change solves:
On landscapes where CCDB restarts more frequently than on public IaaS providers, if the DB is briefly unavailable during a service broker polling cycle, the CC polling job can fail permanently (
max_attempts=1) while the broker is still processing. This leaves a service operation stuck inin progressindefinitely with no delayed job working on it, requiring operator intervention.The companion ccng PR adds three jobs that recover these stuck operations automatically. The new BOSH properties let operators tune how frequently each cleanup/retry job runs.
Links to any other associated PRs
Stuck service operations recovery cloud_controller_ng#5367
I have viewed signed and have submitted the Contributor License Agreement
I have made this pull request to the
developbranchI have run CF Acceptance Tests on bosh lite