Bug 1397675 - Can't add/save Registry & Event Log Entry in Host/VM Analysis Profile
Summary: Can't add/save Registry & Event Log Entry in Host/VM Analysis Profile
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Martin Hradil
QA Contact: Niyaz Akhtar Ansari
URL:
Whiteboard: ui
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-23 07:06 UTC by Niyaz Akhtar Ansari
Modified: 2018-09-20 11:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-20 11:54:47 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Niyaz Akhtar Ansari 2016-11-23 07:06:07 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
Version 5.6.3.1.20161121165709_0acddf6


How reproducible:
100%

Steps to Reproduce:
1.Navigate to Settings → Configuration
2.Click on the Settings accordion, then click Analysis Profiles
3.Add Host/VM Analysis Profile
4.Add Values in Registry & Event Log fields
5.Click Add/save



Actual results:
Unable to add/save After entering values in Registry & Event Log fields 

Expected results:


Additional info:
Comment 3 Josh Carter 2018-09-20 11:54:47 UTC 
Bug Closure

Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

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