Description of problem: When a VM instance in an orchestration stack is removed from the provider due to stack update becomes achieved in VMDB, but it still have an association with the stack. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a stack with one instance in provider 2. Refresh the provider and collect both stack and instances in VMDB 3. Update the stack, for example, change the flavor of the instance. This will force the stack to delete the existing instance and create another instance with the new flavor. 4. Refresh the provider Actual results: The stack contains two instances, the old and the new one. The old instance is achieved but still have the association with the stack. Expected results: The stack should contain only the new instance. Additional info:
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/f7babe009a707f08efcccc1cca50df9e3f368702 commit f7babe009a707f08efcccc1cca50df9e3f368702 Author: Bill Wei <bilwei> AuthorDate: Fri Jun 5 11:58:26 2015 -0400 Commit: Bill Wei <bilwei> CommitDate: Wed Jul 8 17:44:49 2015 -0400 Remove association to stack for disconnected VMs https://bugzilla.redhat.com/show_bug.cgi?id=1228367 app/models/vm_or_template.rb | 13 +++++++++++++ 1 file changed, 13 insertions(+)
Verified in 5.5.0.9
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. https://access.redhat.com/errata/RHSA-2015:2551