Bug 1447374 - UI: Unable to edit Compliance Policy Scope condition.
Summary: UI: Unable to edit Compliance Policy Scope condition.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.9.0
Assignee: Gregg Tanzillo
QA Contact: Dmitry Misharov
URL:
Whiteboard: ui
Depends On:
Blocks: 1477702
TreeView+ depends on / blocked
 
Reported: 2017-05-02 14:24 UTC by Satyajit Bulage
Modified: 2018-03-06 14:43 UTC (History)
9 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1477702 (view as bug list)
Environment:
Last Closed: 2018-03-06 14:43:03 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Satyajit Bulage 2017-05-02 14:24:44 UTC
Description of problem: While creating compliance policy for VM, an edit of the condition under scope is throwing an error.

Error--> "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 "


Version-Release number of selected component (if applicable): 5.8.0.12-rc1.20170425180304_4f35996


How reproducible:100%


Steps to Reproduce:
1. Navigate to Control --> Explorer
2. Create Compliance Policy and under scope add condition/crieteria
3. After adding condition/crieteria and click on it to edit.

Actual results: Throws error mentioned in description


Expected results: It should be able to edit without any error.


Additional info:

Comment 6 Yuri Rudman 2017-06-28 13:28:40 UTC
PR: https://github.com/ManageIQ/manageiq/pull/15452

Comment 8 Dmitry Misharov 2017-10-18 08:33:43 UTC
Verified in 5.9.0.2.20171010190026_0413a06. Expression editor works fine.


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