Description of problem: After deleting the datacenter, all the correlate disks, VMs, templates are all gone. But the disk entries are still in table "base_disks". Version-Release number of selected component (if applicable): * rhevm-3.2.0-11.33.el6ev.noarch How reproducible: 100% reproduce. Steps to Reproduce: 1. Create a datacenter and initialize it. 2. Create several virtual machines with disks.(no need for installing a OS on them). 3. Delete the datacenter 4. In database, we'll see the disk entries of the deleted datacenter. engine# SELECT * from base_disks ; Actual results: See the disk entries of the deleted datacenter are in the database(table base_disks). Expected results: The correlate disk entries should be deleted as well. Additional info:
Hi Team, As it's already one month since the bug was opened, is there any update here? Customer is looking forward on our actions. Thanks a lot! Cheers, Kevein
This bug reproduces on NFS and ISCSI. to reproduce the scenario we should delete to storage pool with force remove. The appropriate fix should be to add a foreign key with cascade delete when removing the storage pool
Fixing the script of force remove. take in notice, the fix only reference the force delete operation, if there are already orphaned entries in the DB, there should be deleted manually.
verified using is12 verification steps - 1. Create a datacenter and initialize it. 2. Create several virtual machines with disks.(no need for installing a OS on them). 3. Delete the datacenter 4. In database, we'll see the disk entries of the deleted datacenter. engine# SELECT * from base_disks ;
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