Bug 986988

Summary:	The engine-notifierd service is not restarted after a failed upgrade and rollback to 3.1.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Idith Tal-Kohen <italkohe>
Component:	ovirt-engine-setup	Assignee:	Alex Lourie <alourie>
Status:	CLOSED ERRATA	QA Contact:	Ilanit Stein <istein>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.2.0	CC:	acathrow, bazulay, byount, cpelland, iheim, jkt, lyarwood, mgoldboi, pstehlik, Rhev-m-bugs
Target Milestone:	---	Keywords:	ZStream
Target Release:	3.2.2
Hardware:	x86_64
OS:	Linux
Whiteboard:	integration
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	The engine-notifierd service is now restarted when the Manager is rolled back to a previous version after a failed upgrade, if it had been running before the upgrade.	Story Points:	---
Clone Of:	976514	Environment:
Last Closed:	2013-08-13 13:08:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	976514
Bug Blocks:

Description Idith Tal-Kohen 2013-07-22 14:45:06 UTC

+++ 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:

Comment 2 Ilanit Stein 2013-07-29 10:46:29 UTC

Verified on rhevm-3.1.0-53.bz923443.el6ev.noarch to sf19 upgrade (failed & roll backed)

Comment 3 errata-xmlrpc 2013-08-13 13:08:49 UTC

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