Created attachment 917781 [details] sosreport-LogCollector-20140714143248.tar.xz Description of problem: Assigning whole parent 'General Hosts Events' for notification causes following error window: ~~~ Error while executing action: The notification event VDS_ACTIVATE_MANUAL_HA is unsupported. ~~~ ~~~ 2014-07-14 14:29:29,319 DEBUG [org.ovirt.engine.core.bll.AddEventSubscriptionCommand] (org.ovirt.thread.pool-8-thread-29) [1b27710] Found permission 00000003-0003-0003-0003-00000000007b for user when running AddEventSubscription, on System with id aaa00000-0000-0000-0000-123456789aaa 2014-07-14 14:29:29,325 WARN [org.ovirt.engine.core.bll.AddEventSubscriptionCommand] (org.ovirt.thread.pool-8-thread-31) [f94dc19] CanDoAction of action AddEventSubscription failed. Reasons:$eventName VDS_ACTIVATE_MANUAL_HA,EN_UNSUPPORTED_NOTIFICATION_EVENT ~~~ FYI 'already subscribed' lines in engine.log are probably caused by Firefox caching issue (multiple instances opened), you can ignore it. Version-Release number of selected component (if applicable): ovirt-engine-webadmin-portal-3.5.0-0.0.master.20140629172257.git0b16ed7.el6.noarch How reproducible: 100% Steps to Reproduce: 1. assign whole parent 'General Hosts Events' for notification 2. 3. Actual results: Error while executing action: The notification event VDS_ACTIVATE_MANUAL_HA is unsupported. Expected results: ??? Additional info:
I got same for: ~~~ Error while executing action: The notification event CLUSTER_ALERT_HA_RESERVATION_DOWN is unsupported. ~~~ Please handle together, this one got caused by 'Cluster Events' parent. 'HA Reservation check has passed' got unselected in the subtree.
2014-07-14 14:37:35,799 WARN [org.ovirt.engine.core.bll.AddEventSubscriptionCommand] (org.ovirt.thread.pool-8-thread-49) [7f4dac3f] CanDoAction of action AddEventSubscription failed. Reasons:$eventName CLUSTER_ALERT_HA_RESERVATION_DOWN,EN_UNSUPPORTED_NOTIFICATION_EVENT
Such cases should not cause errors in the future. We should render event_map as optional at AddEventSubscriptionCommand. Exactly like it is at the Notification Service.
oVirt 3.5 has been released and should include the fix for this issue.