Hide Forgot
Description of problem: =============================== While using the list view on the deployment details page (https://hostname/conductor/deployments/1), there is a drop down to change the data in the deployment being viewed (Viewing: All instances, non-stopped instances, running instances, stopped instances). If you change it from the default you get the error in the summary: No route matches "/conductor/deployments/1?details_tab=instances&only_tab=true" Version-Release number of selected component (if applicable): ===================================================================== aeolus-all-0.7.0-4.el6.noarch aeolus-conductor-0.7.0-4.el6.noarch aeolus-conductor-daemons-0.7.0-4.el6.noarch aeolus-conductor-doc-0.7.0-4.el6.noarch aeolus-configure-2.4.0-3.el6.noarch rubygem-aeolus-cli-0.2.0-3.el6.noarch rubygem-aeolus-image-0.2.0-1.el6.noarch How reproducible: 100% Steps to Reproduce: =========================== 1. deploy a image which brings you to the deployment details page 2. change to list view 3. select a item in the drop down, all instances, see screenshot error
Created attachment 542029 [details] ss
Same thing w/ pools and instances https://bugzilla.redhat.com/show_bug.cgi?id=761502
I can't seem to replicate this on the development 'master' branch. Perhaps this has been fixed already?
It seems to have been already fixed along with 758653
Works for me, in aeolus-conductor-0.8.0-0.20111214144402git245fa3e
Fixed in rpm -qa|grep aeolus aeolus-conductor-doc-0.8.0-0.20111222233342gitd98cb57.el6.noarch rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.noarch rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.noarch aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-configure-2.5.0-0.20111222173430git17b704a.el6.noarch aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch
These bugs are verified, removing from ce-sprint
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/RHEA-2012-0583.html