Description of problem: 'Red Hat Diagnose' can be submitted even without selected text. The trick is to quickly double-click on the button, then it gets dark-blue color and then next submit would cause searching for Recommendations (or at least it seems so as there appears in-progress wheel icon). This seems odd. Version-Release number of selected component (if applicable): redhat-support-plugin-rhev-3.4.0-4.el6ev.noarch How reproducible: 100% Steps to Reproduce: 1. go to 'Log Viewer' tab 2. login into RH Customer Portal from this ui plugin 3. do not select any host/machine but quickly double-click 'Red Hat Diagnose' button and then click on it once again Actual results: search is executed, 'No solutions found.' displayed in _green_ background color Expected results: should not work, nothing is selected as pattern for search Additional info:
https://github.com/redhataccess/redhat_access_angular_ui/commit/d5aeeeef77a907464a62fc2e7d3970f956b79187
out of scope for 3.4.2, missing from tracker bug: [RHEV] 3.4.2 Bug tracker - https://bugzilla.redhat.com/show_bug.cgi?id=1123858. moving to 3.4.3
ok, as this button doesn't appear anymore before a log if selected - redhat-support-plugin-rhev-3.5.0-0.el6ev.noarch
Hi Spenser, If this bug requires doc text for errata release, please provide draft text in the following format: Cause: Consequence: Fix: Result: The documentation team will review, edit, and approve the text. If this bug does not require doc text, please set the 'requires_doc_text' flag to -.
Cause: The Red Hat Diagnose button could be enabled without text being selected. Consequence: The user could diagnose an empty text string, resulting no solutions being returned. Fix: Disable the 'Red Hat Diagnose' button when no text is selected. Result: The user can no longer click the button when text is not selected.
Spenser, please mark the require_doc_text flag as '-' if any of these bugs needs doc for errata or ? if you need to document it and request assistance from doc team? this is needed asap for the last rc build due this week.
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-0211.html