Fix servermaintenance deletion logic

[nagadeesh-nagaraja]

Proposed Changes

Fixes #949

[coderabbitai]

Warning

Review limit reached

@nagadeesh-nagaraja, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 39 minutes and 46 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d24b75a8-594f-4a06-bc1b-b7843c5cb27f

📥 Commits

Reviewing files that changed from the base of the PR and between 1636209 and 828f0d0.

📒 Files selected for processing (2)

• internal/controller/servermaintenance_controller.go
• internal/controller/servermaintenance_controller_test.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fixservermainteanncedeletion

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}