Bug 1506033

Summary: Corrupted report filter when using regular expression
Product: Red Hat CloudForms Management Engine Reporter: David La Motta <dlamotta>
Component: ReportingAssignee: Gregg Tanzillo <gtanzill>
Status: CLOSED DUPLICATE QA Contact: Niyaz Akhtar Ansari <nansari>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.8.0CC: jhardy, nansari, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-25 14:55:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David La Motta 2017-10-24 20:39:00 UTC
Description of problem:
Using a regular expression in a report filter corrupts the filter and renders the report useless.


Version-Release number of selected component (if applicable):
5.8.1.5.20170725160636_e433fc0

How reproducible:
100%


Steps to Reproduce:
1. Create a new reports based on VMs and Instances, call it Corrupted Report
2. Add 'Name' as a column. More fields could be added but it is not necessary
3. Switch to filter tab and craft the following conditional:
   VM and Instance : Vendor REGULAR EXPRESSION MATCHES "openstack"
4. Check the checkbox
5. Click on the conditional as if to edit it and watch things break
6. Your report is now corrupted

Actual results:
Upon clicking the conditional the following error is displayed:

There is an error in the selected expression element, perhaps it was imported or edited manually. 
This element should be removed and recreated or you can report the error to your CFME administrator. 
Error details: undefined method `[]' for nil:NilClass 

Now the 

Expected results:
No error should be displayed and the report should not be corrupted.

Additional info:
I am marking this as medium sev because the workaround is to blow away the report and start from scratch again.

Comment 2 David La Motta 2017-10-25 14:55:27 UTC

*** This bug has been marked as a duplicate of bug 1477701 ***