Description of problem: After adding an alert on a Cloudforms 3.1 appliance that triggers on "provider.clusters > 0" no longer issues alerts Version-Release number of selected component (if applicable): Cloudforms 3.1 How reproducible: all the time Steps to Reproduce: 1. setup email notifications on the zone 2. create a new policy called "reproducer" that evaluates "provider.clusters > 0" hourly 3. make it send an email to a user of the appliance Actual results: no email is ever sent, evm.log doesn't show ever trying to send the email Expected results: emails are sent as the alert is evaluated hourly and is always true Additional info: does not reproduce on Cloudforms 3.2
Please confirm this problem only occurs on CloudForm 3.1. Can QE loan me a 3.1 environment to debug this issue?
Restore overwritten attributes due to comment collision.
I can confirm my tests were done at the same time on 3.2 and 3.1 in lab and 3.1 failed to send emails while 3.2 did not. it seems nothing at all happened on the 3.1 instead of the alert being triggered and the email sent.
This has been fixed in upstream and 5.4. https://github.com/ManageIQ/manageiq/pull/2979 It is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1223835. We yet need to decide whether to back port the fix to 5.3.
http://gitlab.cloudforms.lab.eng.rdu2.redhat.com/cloudforms/cfme/merge_requests/260
commit 7d6463013088618014af9b733ef6e9e99ba0624a Author: Bill Wei <bilwei> Date: Fri May 22 09:00:07 2015 -0400 Call Zone's accessor methods to get models' instances in current zone Add a set of {tablename}_without_a_zone methods to get instances that are not connected to the zone through ext_management_system association. Add spec tests for MiqAlert.evaluate_hourly_timer https://bugzilla.redhat.com/show_bug.cgi?id=1223835
*** Bug 1265323 has been marked as a duplicate of this bug. ***
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions