[patch] Revert sync-wave change for suite-configs app - restore to wave 130 - #599
Merged
Merged
Conversation
added 2 commits
September 16, 2026 14:30
mnivedithaa
approved these changes
Sep 16, 2026
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
2 participants
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.
Problem
PR #594 moved the suite-configs app from sync-wave 130 to 140 (and renamed the template file) to fix apps getting stuck in Deleting state during deprovisioning. However this broke fvtsaas — the MAS Suite operator requires configs like MongoCfg and SlsCfg to be present before it can reach Ready state. With configs at wave 140 (after Suite at 130), the Suite was created before configs existed, causing a provisioning deadlock.
Change
Note
The deprovisioning issue from #594 is still being investigated. A proper fix using finalizer patching in the post-delete hook jobs is being developed and will be submitted as a follow-up PR.