Red Hat Bugzilla – Bug 1334943
two error messages displayed in advanced search
Last modified: 2018-04-17 03:46:51 EDT
Created attachment 1155884 [details] logs and screenshots Description of problem: I started the advanced search dialogue and it seems like its a work in progress... Version-Release number of selected component (if applicable): cfme-5.6.0.5-beta2.4.1.el7cf.x86_64 How reproducible: 100% Steps to Reproduce: 1. in any of the container menus (pods, providers atc) press the advanced search button 2. 3. Actual results: The dialogue that comes up have several issues. here are a few: 1. the ??? marked in yellow 2. no explanations on the fields 3. set searches (not really advanced if you have to select a specific filed) 4. if do not select anything in the <choose> roller we get a double error: select an expression element type and an element type needs to be selected 5. there is a button saying "loading" 6. all of the rest of the buttons are greyed out. Expected results: we need to either disable the dialogue or fix it Additional info: screen shot and logs
So far there's nothing specific to containers. Updating the whiteboard.
https://github.com/ManageIQ/manageiq/pull/8615
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/8a6523666b955422661c9b0824727b699bdef044 commit 8a6523666b955422661c9b0824727b699bdef044 Author: Milan Zazrivec <mzazrivec@redhat.com> AuthorDate: Wed May 11 15:02:56 2016 +0200 Commit: Milan Zazrivec <mzazrivec@redhat.com> CommitDate: Wed May 11 15:02:56 2016 +0200 Remove extraneous error message in advanced search Strings "Select an expression element type" and "Expression element type must be selected" say in fact the same thing and one of them is extraneous. https://bugzilla.redhat.com/show_bug.cgi?id=1334943 app/controllers/application_controller/filter.rb | 1 - 1 file changed, 1 deletion(-)
https://github.com/ManageIQ/manageiq/pull/8473
only one error message is displayed. cfme-5.6.0.8-rc1.1.el7cf.x86_64
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/RHBA-2016:1348