Bug 1761525 - Creating a filter with a blank field triggers a 500 error
Summary: Creating a filter with a blank field triggers a 500 error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.11.0
Hardware: All
OS: All
high
high
Target Milestone: GA
: 5.10.12
Assignee: Yuri Rudman
QA Contact: Angelina Vasileva
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On: 1741243
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-14 14:57 UTC by Satoe Imaishi
Modified: 2019-11-06 08:58 UTC (History)
9 users (show)

Fixed In Version: 5.10.12.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1741243
Environment:
Last Closed: 2019-11-06 08:58:35 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 CFME Bot 2019-10-21 17:05:33 UTC
New commit detected on ManageIQ/manageiq/hammer:

https://github.com/ManageIQ/manageiq/commit/c10710a70d5687d15ba39765380993b0bb4e0cce
commit c10710a70d5687d15ba39765380993b0bb4e0cce
Author:     Keenan Brock <keenan>
AuthorDate: Thu Aug 22 15:35:01 2019 -0400
Commit:     Keenan Brock <keenan>
CommitDate: Thu Aug 22 15:35:01 2019 -0400

    Merge pull request #19176 from yrudman/remove-not-expected-token-when-initializiing-miq-expression

    Do not raise error in MiqExpression#to_sql if (:token) present as one of operators

    (cherry picked from commit 4c3904032d184eff1fb6aabe8c19bc73892b556e)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1761525

 lib/miq_expression.rb | 1 +
 spec/lib/miq_expression_spec.rb | 15 +
 2 files changed, 16 insertions(+)

Comment 3 Angelina Vasileva 2019-10-25 09:00:04 UTC
Fixed and verified in 5.10.12.1.20191022171907_f883bde.

I couldn't reproduce the bug in any way that's mentioned in the description or comments.

Comment 5 errata-xmlrpc 2019-11-06 08:58:35 UTC
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-2019:3268


Note You need to log in before you can comment on or make changes to this bug.