Red Hat Bugzilla – Bug 1254636
OpenStack: Archived instances are not shown in the "archive" tree
Last modified: 2016-07-12 06:20:03 EDT
Description of problem: OpenStack Instances which just recently have been retired, still show up next to regular instances and not in the "Archived" section. Please check attached screenshot which should illustrate the issue. Version-Release number of selected component (if applicable): cfme-5.4.1.0-1.el6cf.x86_64 How reproducible: always Steps to Reproduce: 1. retire some OpenStack instances 2. Navigate to "Cloud, Instances" 3. Notice the instances show up under nova and _also_ under "archived" Actual results: VMs should only show up under archived after they have been retired (this is the behaviour with RHEV and VMware) Expected results: Additional info:
https://github.com/ManageIQ/manageiq/pull/5410
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/c7e254027e1abc6e67d69e8e35e90959b326a6c0 commit c7e254027e1abc6e67d69e8e35e90959b326a6c0 Author: Roman Blanco <rblanco@redhat.com> AuthorDate: Wed Oct 14 15:30:37 2015 +0200 Commit: Roman Blanco <rblanco@redhat.com> CommitDate: Mon Mar 7 13:18:42 2016 +0100 Archived Openstack instances only in "Archived" tree https://bugzilla.redhat.com/show_bug.cgi?id=1254636 app/controllers/application_controller.rb | 2 +- app/models/miq_report/search.rb | 2 ++ app/presenters/tree_builder.rb | 4 ---- app/presenters/tree_builder_instances.rb | 1 + app/views/layouts/_x_gtl.html.haml | 2 +- spec/models/miq_report_spec.rb | 2 ++ 6 files changed, 7 insertions(+), 6 deletions(-)
https://github.com/ManageIQ/manageiq/pull/7408
Instances are shown only in the "archived" tree after retired instances Verified in 5.6.0.1-beta2.20160413141124_e25ac0e
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/RHBA-2016:1348