Created attachment 770865 [details] screenshot of error Description of problem: Adding Host Events and Gluster Volume Events fails with the error "Error while executing action: Action 1: The Notification event is unsupported." Version-Release number of selected component (if applicable): Red Hat Storage Console Version: 2.1.0-0.bb5.el6rhs How reproducible: Always Steps to Reproduce: Issue 1: 1. Click on "Users" 2. Click on the sub-tab "Event Notifier" and click on "Manage Events" 3. Select the "Host Events:" checkbox, enter the "Mail Recipient:" and click on OK Issue 2: 1. Click on "Users" 2. Click on the sub-tab "Event Notifier" and click on "Manage Events" 3. Select the "Gluster Volume Events:" checkbox, enter the "Mail Recipient:" and click on OK Actual results: Following errors are seen: ---- Error while executing action: Action 1: The Notification event is unsupported. Action 2: The Notification event is unsupported. Action 3: The Notification event is unsupported. Action 4: The Notification event is unsupported. Action 5: The Notification event is unsupported. Action 6: The Notification event is unsupported. Action 7: The Notification event is unsupported. ---- Expected results: The action should be successful. Screenshots attached
Created attachment 770866 [details] screenshot of error while adding Gluster Volume Events
Retargeting for 2.1.z U2 (Corbett) release.
This fix is available in downstream build as we have rebased with upstream
Verified as fixed in cb2. But looks like lots of additional events that are NOT relevant for rhs-c are still present. I'll open a separate bug to track the same. --- Failed electing an SPM for the Data-Center Host state was set to non-operational due to inaccessible Storage Domain etc.. ....
Please review the edited DocText and signoff.
Doctext ok.
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