Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clean: Ensure cephcluster cleanup job runs #274

Merged
merged 2 commits into from
Oct 28, 2024

Conversation

travisn
Copy link
Member

@travisn travisn commented Apr 4, 2024

Description of your changes:
The cleanup policy was not allowed to take effect during the cluster cleanup. The finalizer was immediately be removed instead of remaining until the operator has a chance to handle the cleanup policy and internally remove the finalizer. Now the cleanup policy is allowed to be applied and the cleanup job(s) will be started to cleanup the host path and disks from OSDs.

Checklist:

  • Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
  • Reviewed the developer guide on Submitting a Pull Request
  • CI tests has been updated, if necessary.
  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.

@travisn travisn force-pushed the cleanup-policy-apply branch from 5f5dabb to eb70ba8 Compare April 4, 2024 23:23
Copy link
Collaborator

@subhamkrai subhamkrai left a comment

Choose a reason for hiding this comment

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

@travisn is this ready for review or you are still exploring the fix?
Thanks

@travisn
Copy link
Member Author

travisn commented Apr 5, 2024

@travisn is this ready for review or you are still exploring the fix? Thanks

The fix looks good in the local testing, there just seems to be a CI issue that I'm still looking at.

@travisn travisn force-pushed the cleanup-policy-apply branch 3 times, most recently from 7ead254 to 206a9c6 Compare April 5, 2024 22:16
@travisn travisn requested a review from Javlopez April 5, 2024 22:44
During the destroy-cluster, if there are any osd-prepare
jobs they will be purged, similar to deployments that are
not being purged automatically.

Signed-off-by: Travis Nielsen <[email protected]>
The cleanup policy was not allowed to take effect during the
cluster cleanup. The finalizer was immediately be removed instead
of remaining until the operator has a chance to handle the cleanup
policy and internally remove the finalizer. Now the cleanup policy
is allowed to be applied and the cleanup job(s) will be started
to cleanup the host path and disks from OSDs.

Signed-off-by: Travis Nielsen <[email protected]>
@travisn travisn force-pushed the cleanup-policy-apply branch from 206a9c6 to a73bf5e Compare October 25, 2024 20:57
@travisn
Copy link
Member Author

travisn commented Oct 25, 2024

@subhamkrai Ready for final review, the CI is passing now, after rebasing. Such an old PR! Time to enable the stale bot...

@subhamkrai subhamkrai merged commit 3b6633c into rook:master Oct 28, 2024
6 checks passed
@subhamkrai
Copy link
Collaborator

@subhamkrai Ready for final review, the CI is passing now, after rebasing. Such an old PR! Time to enable the stale bot...

Will check on adding the bot

@travisn travisn deleted the cleanup-policy-apply branch October 28, 2024 13:25
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.

2 participants