MR: http://gitlab.cloudforms.lab.eng.rdu2.redhat.com/cloudforms/cfme/merge_requests/113
New commit detected on cfme/5.4.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=84a539ca2e4a715cfbb8b4d1a0745e90a5c20fe8 commit 84a539ca2e4a715cfbb8b4d1a0745e90a5c20fe8 Author: Aparna Karve <akarve> AuthorDate: Fri Jun 5 09:34:16 2015 -0700 Commit: Aparna Karve <akarve> CommitDate: Fri Jun 5 15:42:00 2015 -0700 Create a hash to maintain separate search strings in the accordions https://bugzilla.redhat.com/show_bug.cgi?id=1228849 vmdb/app/controllers/provider_foreman_controller.rb | 7 +++++++ 1 file changed, 7 insertions(+)
New commit detected on cfme/5.4.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=5d0aa53d58dcc979aaab6f5cf5bf3242c59721e0 commit 5d0aa53d58dcc979aaab6f5cf5bf3242c59721e0 Merge: 87065ad 84a539c Author: Dan Clarizio <dclarizi> AuthorDate: Tue Jul 14 17:50:41 2015 -0400 Commit: Dan Clarizio <dclarizi> CommitDate: Tue Jul 14 17:50:41 2015 -0400 Merge branch 'bz1228849_separate_search_for_accs' into '5.4.z' Create a hash to maintain separate search strings in the accordions https://bugzilla.redhat.com/show_bug.cgi?id=1228849 Clean cherry-pick of f47c5fb80a8d23ec05714896365a92d835db97d8 PR - https://github.com/ManageIQ/manageiq/pull/3082 See merge request !113 vmdb/app/controllers/provider_foreman_controller.rb | 7 +++++++ 1 file changed, 7 insertions(+)
I can still see this issue in one place - looking back at the reproducer, I mentioned only one of the cases :/ I apologies for that. The issue also happens when you: - go to Infra / Configuration Management - click Providers / All Red Hat Satellite Providers (in accordion) - use "manager" as search text - click your provider (since it should be still present even with the filter applied) Now, you cannot see any configuration profiles except the "Unassigned Profiles Group". The rest is filtered out. Should I make a separate issue for that or can we fix it in this one? Please advise. Thanks
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://rhn.redhat.com/errata/RHBA-2015-1511.html