Hide Forgot
Description of problem: 'Add Event Notification' should show an error message if MAIL_SERVER is NOT configured and if "ovirt-engine-notifier" service is NOT started . Currently it allows you to add the event notification even if MAIL_SERVER is NOT configured or if the "ovirt-engine-notifier" service is stopped/not-running but the user will not receive any notifications. This will definitely confuse the RHS-C admins/users as they expect the feature to work, if no error occurred while enabling it. Version-Release number of selected component (if applicable): Red Hat Storage Console Version: 2.1.2-0.25.master.el6_5 How reproducible: Always Steps to Reproduce: 1. Click on "Users" 2. Click on the sub-tab "Event Notifier" and click on "Manage Events" 3. Check some Events and enter the 'Mail Recipient' 4. Click on OK Actual results: Action 'Add Event Notification' currently succeeds in the following cases: a. If NO MAIL_SERVER is defined in the configuration file "/usr/share/ovirt-engine/services/ovirt-engine-notifier/ovirt-engine-notifier.conf" b. If "ovirt-engine-notifier" service is NOT started or not running in the Engine. Expected results: Action should fail and display the accurate error message in any or both of the below cases. a. If NO MAIL_SERVER is defined in the configuration file "/usr/share/ovirt-engine/services/ovirt-engine-notifier/ovirt-engine-notifier.conf" b. If "ovirt-engine-notifier" service is NOT started or not running in the Engine. Additional info:
Created attachment 833532 [details] Manage Events pop up with warning note
Currently there is no way to check the status of notifier service. Hence we will show a warning by default in manage events pop up .
Verified as fixed in cb11 A warning message is shown in the manage events pop-up. see attached.
Created attachment 837228 [details] screensot
Doc text is not required as its only a note being added in the UI and also Admin guide got updated with the relevant information.
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. http://rhn.redhat.com/errata/RHEA-2014-0208.html