docker-storage-setup: If metadata volume already exists, do not create new one #40
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.
Fixes #39
It can happen that we created a metadata volume and later there was not
enough space to create data volume and script exited, leaving behind
metadata volume. Later if user adds more space to volume group and re-runs
the script, it fails saying metadata volume already exists.
For now fix this by checking if metadata volume exists or not. If it exists
use it (instead of erroring out).
I think ideally we should have cleanup logic and cleanup any logical
volumes created if error happens later. That probably also means
getting rid of "set -e".
Signed-off-by: Vivek Goyal vgoyal@redhat.com