CA-91480: Catch exception if blob doesn't exist on vm_destroy #911
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.
This was meant to fix CA-91480, but it turns out that this was a different issue. This issue is that vm_destroy doesn't catch an exception if it tries to destroy a VM which has a blob which also doesn't exist on the server, which could happen in a vm_import.
This is the first bug we've found that we've also included a regression unit test for, which is significant. Otherwise, this is an unlikely bug to encounter and fairly trivial to solve.