Red Hat Bugzilla – Bug 882847
upgrade 3.0 to 3.1: event notification is not sent.
Last modified: 2016-02-10 14:04:45 EST
Description of problem:
After upgrade from IC158.2 to SI24.5,
Though event notification is activated, email is not sent.
After the upgrade there are 2 notifier.conf files:
Setting both to correct settings didn't made the email sent.
Version-Release number of selected component (if applicable):
IC158.2 to SI24.5
Steps to Reproduce:
1. Define the /etc/ovirt-engine/notifier/notifier.conf for sending notifications
2. Activate engine-notifierd service.
3. Attach event notification to a user
(I added a user from AD, attached to it event notification for ovirt-engine stop)
4. service ovirt-engine restart several times, and expect email.
no email is sent
There is another bug, on that the values from the old notifier.conf  are not copied to the new notifier conf  - Bug 880923
Created attachment 656451 [details]
Created attachment 656453 [details]
Created attachment 656455 [details]
Created attachment 656456 [details]
*** Bug 881071 has been marked as a duplicate of this bug. ***
As mentioned in bug 881071, which was marked as duplicate of this bug,
here also there are many error messages "PSQLException: FATAL: connection limit exceeded for non-superusers".
one thing I did notice is that the code is not using a DB connection pool.
The error appears every 5 seconds. please provide the configuration file of the notification service on your setup.
The configuration file of the notification service is already attached.
I first configured conf file , and when it didn't work I configured ,
both mentioned in the description.
*** Bug 882682 has been marked as a duplicate of this bug. ***
test only. 3.0->3.1 upgrade flow
*** Bug 882688 has been marked as a duplicate of this bug. ***
*** Bug 882690 has been marked as a duplicate of this bug. ***
Verified on upgrade IC158.2 -> SI27.
First verified notification sent for ISC158.2, then after upgrade verified the notifier.conf is kept and notification is sent.
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.