[ovirt-users] Upgrade to 3.5.3 fails on ovirt-engine-notifier service

[Trey Dockendorf]

I just upgraded from 3.5.1 to 3.5.3 and found the end of engine-setup
failed because of the ovirt-engine-notifier service.  The logs indicate
that the MAIL_SERVER option was not set.  I had set this before via Puppet
and know it was working because right before I started the upgrade I was
receiving event notifications.  It appears as though the RPM (or some other
mechanism) set the config file
at /usr/share/ovirt-engine/services/ovirt-engine-notifier/ovirt-engine-notifier.conf
back to its original state with my changes removed.

Attached is the log from engine-setup.

Is this a bug?  I was able to work around this by manually setting
MAIL_SERVER back to the value I had already set previously and then
re-running engine-setup.  Even after re-running engine-setup I noticed I
had to manually start ovirt-engine-notifier service.

Thanks,
- Trey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20150622/67181bf6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ovirt-engine-setup-20150622112959-o5ppp0.log
Type: application/octet-stream
Size: 2497919 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20150622/67181bf6/attachment-0001.obj>