Description of problem:

BZ1042829 introduced 'Failed to restart VM on a different host' event from notification subscription. In the process there was error in event_up_name - VDS_INITIATED_RUN_VM_FAIL vs VDS_INITIATED_RUN_VM_FAILED.

But instead of removing bogus VDS_INITIATED_RUN_VM_FAIL, just new VDS_INITIATED_RUN_VM_FAILED was added.

Please clean after yourself.

engine=# select * from event_subscriber ;
            subscriber_id             |        event_up_name        |  method_address   | tag_name | notification_method 
--------------------------------------+-----------------------------+-------------------+----------+---------------------
 fdfc627c-d875-11e0-90f0-83df133b58cc | VDS_INITIATED_RUN_VM_FAILED | jbelka |          | EMAIL
(1 row)

engine=# select * from event_map where event_up_name ilike '%run_vm%';
        event_up_name        | event_down_name 
-----------------------------+-----------------
 VDS_INITIATED_RUN_VM_FAIL   | 
 VDS_INITIATED_RUN_VM_FAILED | 
(2 rows)

Version-Release number of selected component (if applicable):
av2 rhevm-3.4.0-0.3.master.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. check db
2.
3.

Actual results:
forgotten wrong event_up_name

Expected results:
remove useless stuff

Additional info:
it could be fun to search what else is rotting in the DB :)