Description of problem: Failures to remove volumes from an import domain result in imported volumes on data domains being marked as illegal. Version-Release number of selected component (if applicable): rhevm-3.2.2-0.41 How reproducible: Always. Steps to Reproduce: 1. Export a guest to an import domain. 2. Manually remove the volume from the import domain. 3. Attempt to remove the volume from the import domain. 4. The original volume on the data domain is now marked as illegal. Actual results: Original volumes marked as illegal. Expected results: Imported volumes are not touched as a result of any failures to remove volumes from the import domain. Additional info:
I've attached a quick patch to workaround this by checking if the parent command is an image/template removal command for an import domain.
This bug has been cloned to bug #1007507
Verified on is15, status of the original disk is OK.
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0038.html