Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1110307

Summary: notifier daemon is not keeping startup settings after upgrade to 3.3
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-engine-setupAssignee: Yedidyah Bar David <didi>
Status: CLOSED ERRATA QA Contact: Petr Beňas <pbenas>
Severity: high Docs Contact:
Priority: medium    
Version: 3.3.0CC: acathrow, alonbl, bazulay, cpelland, dfediuck, didi, gklein, iheim, lveyde, pstehlik, Rhev-m-bugs, sbonazzo, scohen, stirabos, tpoitras, yeylon
Target Milestone: ---Keywords: ZStream
Target Release: 3.4.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: Doc Type: Bug Fix
Doc Text:
On upgrade from 3.2 to 3.3, the new 'ovirt-engine-notifier' is started and enabled on reboot if the old 'engine-notifierd' was up before setup.
Story Points: ---
Clone Of: 1083551 Environment:
Last Closed: 2014-07-29 16:24:15 UTC Type: ---
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: 1083551    
Bug Blocks:    

Comment 1 Yedidyah Bar David 2014-06-18 07:51:34 UTC
Please see https://bugzilla.redhat.com/show_bug.cgi?id=1083551#c13 .

Comment 3 Petr Beňas 2014-06-27 12:59:55 UTC
[root@brq-update yum.repos.d]# rpm -qa rhevm rhevm-setup
rhevm-3.3.4-0.53.el6ev.noarch
rhevm-setup-3.4.1-0.23.el6ev.noarch
[root@brq-update yum.repos.d]# service ovirt-engine-notifier status
ovirt-engine-notifier (pid  11015) is running...
[root@brq-update yum.repos.d]# rhevm-setup 
<snip/>
[root@brq-update yum.repos.d]# service ovirt-engine-notifier status
ovirt-engine-notifier (pid  15624) is running...

Comment 5 errata-xmlrpc 2014-07-29 16:24:15 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-2014-0960.html