+++ This bug was initially created as a clone of Bug #854275 +++ Description of problem: During the creation of a new user, a message will be returned after clicking save user. The messages indicate the user was created successfully; however, the user will not show up in the user list immediately and a related error message is returned, '' did not meet the current search criteria and is not being shown Version-Release number of selected component (if applicable): katello-common-1.1.8-1.git.19.fc6b1f1.fc16.noarch Steps to Reproduce: 1. Navigate to your favorite katello deployment 2. Login with admin 3. create a new user Actual results: User created successfully '' did not meet the current search criteria and is not being shown Expected results: User create successfullly w/ the user appearing in the user list (left pane). Additional info:
2012-09-07 10:15:51 < adprice> omaciel: ahah! got something. changed roles and org of a user. then switched to orgs page and got " '' no longer matches the current search criteria " 2012-09-07 10:16:26 < omaciel> adprice: BINGO!
Created attachment 610745 [details] Katello log Calls that were made when reproducing this.
fix merged in https://github.com/Katello/katello/commit/c5a15c5caa2f1d3c78149ffc99e9a43bc73b9723
Regression as of c5a15c5caa2f1d3c78149ffc99e9a43bc73b9723
merged. was a deeper issue with elastic search https://github.com/Katello/katello/commit/044ebf811430c03994910954ffd4c530728c4709
Verified: * candlepin-0.7.12-1.el6_3.noarch * candlepin-tomcat6-0.7.12-1.el6_3.noarch * katello-candlepin-cert-key-pair-1.0-1.noarch * katello-certs-tools-1.1.8-1h.el6_3.noarch * katello-cli-common-1.1.10-1h.el6_3.noarch * katello-cli-headpin-0.2.2-1.el6_2.noarch * katello-common-1.1.14-2h.el6_3.noarch * katello-configure-1.1.11-1h.el6_3.noarch * katello-glue-candlepin-1.1.14-2h.el6_3.noarch * katello-headpin-1.1.14-2h.el6_3.noarch * katello-headpin-all-1.1.14-2h.el6_3.noarch * katello-selinux-1.1.2-1h.el6_3.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/RHSA-2013-0544.html