Don't lose VM volume attachments when refreshing the cloud inventory #243
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.
When the CloudManager refreshes, it removes from the inventory any Disks that were only added by the CinderManager as part of attaching Volumes to VMs since the CloudManager doesn't find them while collecting inventory. As a result, Volumes will have correct statuses but incorrect numbers of attachments, leading to confusing user experience and various UI actions failing.
This patch causes the CloudManager to be aware of VM volume attachments so that the associations are not broken between Cloud and Cinder refreshes.
This is a solution for https://bugzilla.redhat.com/show_bug.cgi?id=1544344
Depends on #242