Description of problem: Not sure if we want to do anything about this.. but here's the info.. 1. on a running conductor.. OPEN the following URL https://host/conductor/logout * to be clear type in /conductor/logout 2. try to login first attempt will *always* fail Started GET "/conductor/logout" for 10.11.11.150 at Thu Mar 01 11:42:07 -0500 2012 Processing by UserSessionsController#destroy as HTML Redirected to https://qeblade30.rhq.lab.eng.bos.redhat.com/conductor/login Completed 302 Found in 2ms Started GET "/conductor/login" for 10.11.11.150 at Thu Mar 01 11:42:10 -0500 2012 Processing by UserSessionsController#new as HTML Rendered user_sessions/_security.html.haml (1.6ms) Rendered user_sessions/new.html.haml within layouts/login (8.6ms) Completed 200 OK in 10ms (Views: 9.7ms | ActiveRecord: 24.5ms) Started POST "/conductor/user_session" for 10.11.11.150 at Thu Mar 01 11:42:21 -0500 2012 Processing by UserSessionsController#create as JS Parameters: {"login"=>"admin", "password"=>"[FILTERED]", "authenticity_token"=>"nd8nm85fPjGx1ZsMHWUKsQNwqbxfMWTxIKv6Qx036Dg=", "utf8"=>"✓", "_password"=>"[FILTERED]"} Warden is authenticating admin against database User Load (0.4ms) SELECT "users".* FROM "users" WHERE "users"."login" = 'admin' LIMIT 1 SQL (0.3ms) BEGIN Quota Load (0.4ms) SELECT "quotas".* FROM "quotas" WHERE "quotas"."id" = 4 LIMIT 1 SQL (0.4ms) SELECT 1 FROM "users" WHERE ("users"."login" = 'admin') AND ("users".id <> 1) LIMIT 1 AREL (0.4ms) UPDATE "users" SET "updated_at" = '2012-03-01 16:42:21.354049', "last_login_at" = '2012-03-01 16:42:21.000000', "login_count" = 33 WHERE "users"."id" = 1 SQL (12.5ms) COMMIT Rendered text template (0.0ms) Completed 201 Created in 129ms (Views: 0.8ms | ActiveRecord: 22.1ms) Started GET "/conductor/logout" for 10.11.11.150 at Thu Mar 01 11:42:21 -0500 2012 Processing by UserSessionsController#destroy as HTML User Load (5.9ms) SELECT "users".* FROM "users" WHERE "users"."id" = 1 LIMIT 1 Redirected to https://qeblade30.rhq.lab.eng.bos.redhat.com/conductor/login Completed 302 Found in 9ms Started GET "/conductor/login" for 10.11.11.150 at Thu Mar 01 11:42:22 -0500 2012 Processing by UserSessionsController#new as HTML Rendered user_sessions/_security.html.haml (1.7ms) Rendered user_sessions/new.html.haml within layouts/login (9.1ms) Completed 200 OK in 11ms (Views: 10.1ms | ActiveRecord: 15.5ms)
This is not seems to be the case with the current build.First or any subsequent login after logout is successful with valid credentials. Verified on:- [root@dhcp201-113 ~]# rpm -qa|grep aeolus aeolus-conductor-doc-0.13.7-1.el6cf.noarch aeolus-all-0.13.7-1.el6cf.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-configure-2.8.6-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-conductor-0.13.7-1.el6cf.noarch aeolus-conductor-daemons-0.13.7-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