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

osd: check if osd is safe-to-destroy before removal (backport #9230) #9255

Merged
merged 1 commit into from Nov 29, 2021

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Nov 25, 2021

This is an automatic backport of pull request #9230 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

@mergify mergify bot added the conflicts label Nov 25, 2021
@leseb leseb force-pushed the mergify/bp/release-1.7/pr-9230 branch from 55b75be to bf2586d Compare November 25, 2021 10:02
@leseb leseb force-pushed the mergify/bp/release-1.7/pr-9230 branch from bf2586d to 6f9a938 Compare November 25, 2021 10:46
If multiple removal jobs are fired in parallel, there is a risk of
losing data since we will forcefully remove the OSD. It's also simply
true if a single OSD is not safe to destroy, there is also a risk of
data loss.

So now, we check if the OSD is safe-to-destroy first and then proceed.
The code waits forever and retries every minute unless the
--force-osd-removal flag is passed.

Signed-off-by: Sébastien Han <seb@redhat.com>
(cherry picked from commit 7402c2c)
@leseb leseb force-pushed the mergify/bp/release-1.7/pr-9230 branch from 6f9a938 to 29065e3 Compare November 25, 2021 11:03
@leseb leseb merged commit f38dcb9 into release-1.7 Nov 29, 2021
@leseb leseb deleted the mergify/bp/release-1.7/pr-9230 branch November 29, 2021 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant