Bug 1232022
| Summary: | undefined method `[]' for nil:NilClass [miq_policy/alert_field_changed] | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Bill Wei <bilwei> |
| Component: | Control | Assignee: | Bill Wei <bilwei> |
| Status: | CLOSED ERRATA | QA Contact: | Aziza Karol <akarol> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.4.0 | CC: | adahms, akarol, bilwei, cpelland, dajohnso, jhardy, jprause, mfalesni, mfeifer, obarenbo, simaishi |
| Target Milestone: | GA | Keywords: | ZStream |
| Target Release: | 5.4.1 | Flags: | mfalesni:
automate_bug?
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.4.1.0 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, attempting to create a new alarm and setting the 'What to evaluate' field to 'VMware Alarm' would result in the error 'undefined method `[]' for nil:NilClass [miq_policy/alert_field_changed]'. This update resolves a syntax error in the code used to form options for VMware alarms, making it possible to successfully create a new alarm when the 'What to evaluate' field is set to 'VMware alarm'.
|
Story Points: | --- |
| Clone Of: | 1231889 | Environment: | |
| Last Closed: | 2015-07-30 13:11:52 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: | |||
| Bug Depends On: | 1231889 | ||
| Bug Blocks: | |||
|
Comment 2
Bill Wei
2015-06-23 13:05:17 UTC
Able to create a new alarm when the 'What to evaluate' field is set to 'VMware alarm'. Verified: 5.4.1.0.20150717083323_6ed7e1c 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://rhn.redhat.com/errata/RHBA-2015-1511.html |