New commit detected on ManageIQ/manageiq-ui-classic/gaprindashvili: https://github.com/ManageIQ/manageiq-ui-classic/commit/162aad210abf41fab03d6714a434809590178ffb commit 162aad210abf41fab03d6714a434809590178ffb Author: Milan Zázrivec <mzazrivec> AuthorDate: Mon Dec 18 17:54:48 2017 +0100 Commit: Satoe Imaishi <simaishi> CommitDate: Tue Dec 19 09:30:35 2017 -0500 Merge pull request #2741 from hstastna/Adv_Search_services_list_fix Fix using view selector in My Services page (cherry picked from commit 6dec1a4cde3d11e887bdffb9b2742290b5ee65eb) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1527576 app/controllers/service_controller.rb | 1 + spec/controllers/service_controller_spec.rb | 29 +++++++++++++++++++++++++++++ 2 files changed, 30 insertions(+)
So I created custom filter with expression: Service: Aggregate All Vm Cpus = 454 and it threw me attached exception. Also after creating filters I have to refresh page to make these filters show up in the tree view.
Created attachment 1385596 [details] exception
Matous, showing filters in the tree view right after creating is an issue common for many explorer screens, not specially for My Services page.
Hilda, yes I am aware of it. I was just pointing that out. The first issue is the problem with My Services page only I hope.
Matous, thank you for all of your comments, I will fix the issue asap and update the info.
Matous, I have checked the issue, tested, investigated and it looks like this is not related to adding Adv search and creating filters in My Services generally, because other filters work well. This is related to aggregation or miq expressions, and from my point of view, the issue you have found, needs a new separate BZ and this BZ can be closed/verified because, originally, this BZ was about little bit different issues. Any other suggestions? Thank you.
(In reply to Hilda Stastna from comment #8) > Matous, > > I have checked the issue, tested, investigated and it looks like this is not > related to adding Adv search and creating filters in My Services generally, > because other filters work well. This is related to aggregation or miq > expressions, and from my point of view, the issue you have found, needs a > new separate BZ and this BZ can be closed/verified because, originally, this > BZ was about little bit different issues. Any other suggestions? Thank you. If I agree that the issue is in the expression, but if the screen is crashing this is pretty bad, and we should to fix it. A new ticket should be open ASAP
Hilda, I tried to use this expression on Instances and VMs pages and it worked with no problems. So I think this issue is connected to this BZ. Thanks.
Matous, thank you for the info. I was debugging and looking for a core of the problem you have mentioned and it threw me far from the UI part of the code or My Services page. The problem might be more complicated. So I think we should follow Loic's comment: "A new ticket should be open ASAP", to track and to test the bug more effectively.
As I created BZ(https://bugzilla.redhat.com/show_bug.cgi?id=1539710) specific situation reported I am setting it to verified because the rest of this functionality works correctly.
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://access.redhat.com/errata/RHSA-2018:0380