Skip to content

[patch] Fix applications stuck in Deleting state during deprovisioning due to incorrect sync-wave ordering - #594

Merged
rbinns merged 4 commits into
mainfrom
mascore-16865
Sep 11, 2026
Merged

rbinns merged 4 commits into
mainfrom
mascore-16865

Conversation

@Raahithyaj

Copy link
Copy Markdown
Contributor

MASCORE 16865.
Root Cause:
The Suite app and config apps (SLS, Mongo, BAS etc.) were both at the same sync-wave (130). Since ArgoCD deletes in descending wave order, they were being deleted at the same time. The Suite CR deletion killed the entity manager pods that are responsible for clearing finalizers on the config CRs , leaving them stuck in Terminating forever. This caused the post-delete hook jobs to time out and fail, preventing ArgoCD from clearing its own finalizers.
Fix:
Moved the config apps from sync-wave 130 → 140 (renamed 130-ibm-mas-suite-configs-app.yaml → 140-ibm-mas-suite-configs-app.yaml). This ensures config apps delete first (wave 140) while entity managers are still alive, allowing clean finalizer removal, before Suite (wave 130) deletes last.
Validation:
Reproduced the bug on inst03/noble9, applied the fix, re-provisioned and deprovisioned , all post-delete jobs completed successfully and all ArgoCD apps deleted cleanly with no apps stuck in Deleting state

Note: This was validated on a Suite + SLS only instance (no Manage/IOT/Facilities).
Screenshot 1 — No apps stuck in Deleting
image
Screenshot 2 — Post-delete jobs succeeded
image

@rbinns rbinns left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This branch his out of step with the base, please update.

@rbinns
rbinns merged commit 39062a5 into main Sep 11, 2026
3 checks passed
@rbinns
rbinns deleted the mascore-16865 branch September 11, 2026 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants