Description of problem: When clicking on instances there is an error page displayed that states: Multiple parents found. [vm_cloud/explorer] Version-Release number of selected component (if applicable): cfme-5.6.1.2 How reproducible: on this env: trivial Steps to Reproduce: 1. navigate to an instance view for this OSP tenant Actual results: FATAL -- : Error caught: [ActionView::Template::Error] Multiple parents found. Expected results: vm instance information Additional info: logs pending
https://github.com/ManageIQ/manageiq/pull/14060
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/af9e051cb6d0d5b90b0e5448cc8ca15e5557011d commit af9e051cb6d0d5b90b0e5448cc8ca15e5557011d Author: Jason Frey <jfrey> AuthorDate: Fri Feb 24 01:50:55 2017 -0500 Commit: Jason Frey <jfrey> CommitDate: Fri Feb 24 17:07:22 2017 -0500 Fix "Multiple Parents Found" issue when moving a relationship. Originally, `.parent=` was written in terms of `add_children`. However, `add_children` supports duplicating nodes in the tree. This is reasonable because you may have a tree where multiple entries make sense, and for those things that have multiple entries, you wouldn't call `.parent`, you would probably call `.parents` and it is expected that calling `.parent` would blow up with the "Multiple Parents Found" error. However, the expectation of calling `.parent=` is that it will become the new, sole, parent, and so implementing it via add_children is wrong because it creates an oddity in that you can call `.parent=` and then not be able to call `.parent` afterwards. https://bugzilla.redhat.com/show_bug.cgi?id=1379464 https://bugzilla.redhat.com/show_bug.cgi?id=1391850 https://bugzilla.redhat.com/show_bug.cgi?id=1406431 app/models/account.rb | 4 +- app/models/mixins/relationship_mixin.rb | 21 +++++----- lib/extensions/ar_miq_set.rb | 3 +- spec/models/mixins/relationship_mixin_spec.rb | 56 +++++++++++++++++++++++++++ 4 files changed, 71 insertions(+), 13 deletions(-)
*** Bug 1426738 has been marked as a duplicate of this bug. ***
verified on 5.8.0.3
*** Bug 1438803 has been marked as a duplicate of this bug. ***
Hi, Could you provide steps to reproduce Thanks
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days