+++ This bug was initially created as a clone of Bug #976514 +++ Description of problem: The engine-notifierd service is not restarted after a failed upgrade and rollback to 3.1. Version-Release number of selected component (if applicable): rhevm-setup-3.2.0-11.30.el6ev.noarch How reproducible: Always. Steps to Reproduce: 1. Enable and start the engine-notifierd service. 2. Attempt to upgrade from 3.1 to 3.2, ensuring it fails and results in a rollback. For example I used BZ#975022. 3. Once the rollback is complete the engine-notifierd service is still down. Actual results: engine-notifierd service is still down. Expected results: engine-notifierd service has restarted. Additional info:
Verified on rhevm-3.1.0-53.bz923443.el6ev.noarch to sf19 upgrade (failed & roll backed)
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/RHBA-2013-1149.html