Handle case where do_volume_creation_check gets a nil from Fog #73
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.
do_volume_creation_check
assumes it will always get the requested volume object back from Fog, resulting in a thrown exception and an errored-out provisioning attempt if that assumption is violated due to the requested volume not being found. This fixes the assumption, allowing the provisioning workflow to continue and retry as normal.This fixes the surface level issue in https://bugzilla.redhat.com/show_bug.cgi?id=1475260, though it doesn't explain why a 404 would be reported for an ID that came from Fog in the first place.