nautilus: ceph-volume: do not fail when trying to remove crypt mapper #30554
Conversation
This file contains 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
In a containerized context, at some point, need to run `simple scan` on a device from a separate container (not the existing and running corresponding container to that device), but this can't work because when it tries to remove the mapper which is still in use by the corresponding running osd container, it fails. This can be a bit more permissive and simply throw a warning. Closes: https://tracker.ceph.com/issues/41392 Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com> (cherry picked from commit 80d3e4c)
guits
approved these changes
Sep 25, 2019
jan--f
approved these changes
Sep 30, 2019
smithfarm
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In a containerized context, at some point, need to run
simple scanon a devicefrom a separate container (not the existing and running corresponding container
to that device), but this can't work because when it tries to remove the
mapper which is still in use by the corresponding running osd container,
it fails.
This can be a bit more permissive and simply throw a warning.
Closes: https://tracker.ceph.com/issues/41392
Signed-off-by: Guillaume Abrioux gabrioux@redhat.com
Backport of: #30490