Bug 1231889 - undefined method `[]' for nil:NilClass [miq_policy/alert_field_changed]
Summary: undefined method `[]' for nil:NilClass [miq_policy/alert_field_changed]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Control
Version: 5.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: 5.5.0
Assignee: Bill Wei
QA Contact: Milan Falešník
URL:
Whiteboard:
Depends On:
Blocks: 1232022
TreeView+ depends on / blocked
 
Reported: 2015-06-15 14:42 UTC by Milan Falešník
Modified: 2016-08-10 14:19 UTC (History)
4 users (show)

Fixed In Version: 5.5.0.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1232022 (view as bug list)
Environment:
Last Closed: 2015-12-08 13:13:45 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:
mfalesni: automate_bug+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2551 0 normal SHIPPED_LIVE Moderate: CFME 5.5.0 bug fixes and enhancement update 2015-12-08 17:58:09 UTC

Description Milan Falešník 2015-06-15 14:42:28 UTC
Description of problem:
When creating a new Alarm, when the "What to evaluate" field is set to VMware Alarm, it throws the error mentioned in the title.

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

How reproducible:
always

Steps to Reproduce:
1. Go to Control / Explorer / Alarms
2. Create a new Alarm
3. In the form, set the "What to evaluate" to "VMware Alarm".

Actual results:
undefined method `[]' for nil:NilClass [miq_policy/alert_field_changed]

Expected results:
The field changes.

Additional info:

Comment 2 CFME Bot 2015-06-15 20:58:36 UTC
New commit detected on manageiq/master:
https://github.com/ManageIQ/manageiq/commit/da8cc3706fbd8a6e91060a65c2242f6bf5c8ed04

commit da8cc3706fbd8a6e91060a65c2242f6bf5c8ed04
Author:     Bill Wei <bilwei>
AuthorDate: Tue Jun 16 03:39:30 2015 +0800
Commit:     Bill Wei <bilwei>
CommitDate: Tue Jun 16 03:39:30 2015 +0800

    Fix a coding error in forming options for VMWare alarm
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1231889

 vmdb/app/views/miq_policy/_alert_builtin_exp.html.haml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comment 3 CFME Bot 2015-06-22 15:58:26 UTC
New commit detected on cfme/5.4.z:
https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=def733e9bb5d19777a3e9e51a0aa2a7ac6f0d66c

commit def733e9bb5d19777a3e9e51a0aa2a7ac6f0d66c
Author:     Bill Wei <bilwei>
AuthorDate: Tue Jun 16 03:39:30 2015 +0800
Commit:     Bill Wei <bilwei>
CommitDate: Tue Jun 16 05:00:01 2015 +0800

    Fix a coding error in forming options for VMWare alarm
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1231889

 vmdb/app/views/miq_policy/_alert_builtin_exp.html.haml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comment 4 CFME Bot 2015-06-22 15:58:42 UTC
New commit detected on cfme/5.4.z:
https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=cc4fc9d0a99423d78dbb7796fa3e06133f9819ca

commit cc4fc9d0a99423d78dbb7796fa3e06133f9819ca
Merge: b7809e0 def733e
Author:     Greg McCullough <gmccullo>
AuthorDate: Mon Jun 22 11:33:18 2015 -0400
Commit:     Greg McCullough <gmccullo>
CommitDate: Mon Jun 22 11:33:18 2015 -0400

    Merge branch 'vmware_alarm' into '5.4.z'
    
    Fix a coding error in forming options for VMWare alarm
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1231889
    
    Upstream PR
    https://github.com/ManageIQ/manageiq/pull/3172
    
    See merge request !130

 vmdb/app/views/miq_policy/_alert_builtin_exp.html.haml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comment 5 Milan Falešník 2015-09-11 12:27:52 UTC
Verified working both in upstream build from 0831 and also in CFME 5.4.2.0. The Alerts form now works correctly with VMware Alarm again.

Comment 6 Milan Falešník 2015-09-30 13:31:00 UTC
Checked in 5.5.0.2-alpha1.1 too.

Comment 8 errata-xmlrpc 2015-12-08 13:13:45 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/RHSA-2015:2551


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