Created attachment 591098 [details] error_msg Description of problem: Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1.Create new user with Global profile user (default role) 2.Login to Conductor as Global profile user 3.Start a new VM 4.When the VM is in pending state, click on monitor Actual results: It will display a long error message on the UI Expected results: It should not display any error message on click of monitor . PFA: attacher error screen shot (error_msg.png) and rails log(Rails_log) Additional info: rpm -qa | grep aeolus aeolus-configure-2.5.7-1.el6_3.noarch aeolus-all-0.8.27-1.el6_3.noarch aeolus-conductor-0.8.27-1.el6_3.noarch aeolus-conductor-doc-0.8.27-1.el6_3.noarch aeolus-conductor-daemons-0.8.27-1.el6_3.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch rubygem-aeolus-cli-0.3.3-1.el6_3.noarch
Created attachment 591100 [details] Rails_log
this error is observed for global zone user also
Subject: [PATCH conductor] bug 831057: fix ambiguous order by name https://bugzilla.redhat.com/show_bug.cgi?id=831057 There was a deployments 'order by' clause that just listed 'name' which was ambiguous (since the joined pool and pool_families models also have a 'name' column) --- src/app/models/pool.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/app/models/pool.rb b/src/app/models/pool.rb index 6bd3605..c4acbce 100644 --- a/src/app/models/pool.rb +++ b/src/app/models/pool.rb @@ -124,7 +124,7 @@ class Pool < ActiveRecord::Base if options[:with_deployments] result[:deployments] = deployments.list_for_user(options[:current_user], Privilege::VIEW). - order('name asc'). + order('deployments.name asc'). paginate(:page => options[:page], :per_page => options[:per_page]). map {|d| d.as_json} end --
Pushed to 1.0.1 at 22ffc7b96288a21b09f558c852309488025df0a3
No error displayed when clicked on monitor page while the VM is pending. verified: rpm -qa | grep aeolus rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-conductor-daemons-0.13.8-1.el6cf.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-conductor-doc-0.13.8-1.el6cf.noarch aeolus-configure-2.8.6-1.el6cf.noarch aeolus-all-0.13.8-1.el6cf.noarch aeolus-conductor-0.13.8-1.el6cf.noarch
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-1516.html