Upgrade to 3.5.3 fails on ovirt-engine-notifier service
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
Hi, please never change anything in /usr/share/ovirt-engine, because these file will always be overwritten on RPM upgrades. To change MAIL_SERVER for ovirt-engine-notifier please create config file (for example 99-user.conf) under /etc/ovirt-engine/notifier/notifier.conf.d and put you customizations here, for example: MAIL_SERVER=my-mail-server.com This way your changes survive upgrades. Let me know if you have any other issues with it. Thanks Martin Perina ----- Original Message -----
From: "Trey Dockendorf" <treydock@gmail.com> To: "users" <users@ovirt.org> Sent: Monday, June 22, 2015 7:09:57 PM Subject: [ovirt-users] Upgrade to 3.5.3 fails on ovirt-engine-notifier service
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
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I thought using /usr/share/ovirt-engine was wrong, but I was going off of RedHat docs [1]. I didn't realize an alternative location existed. Having just searched some more I found the oVirt docs [2] which I don't recall existing or mentioning the conf.d at the time I setup the notifier service. Thanks, - Trey [1]: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualizat... [2]: http://www.ovirt.org/Features/configuration-event-subscribers On Mon, Jun 22, 2015 at 2:38 PM, Martin Perina <mperina@redhat.com> wrote:
Hi,
please never change anything in /usr/share/ovirt-engine, because these file will always be overwritten on RPM upgrades.
To change MAIL_SERVER for ovirt-engine-notifier please create config file (for example 99-user.conf) under /etc/ovirt-engine/notifier/notifier.conf.d and put you customizations here, for example:
MAIL_SERVER=my-mail-server.com
This way your changes survive upgrades.
Let me know if you have any other issues with it.
Thanks
Martin Perina
----- Original Message -----
From: "Trey Dockendorf" <treydock@gmail.com> To: "users" <users@ovirt.org> Sent: Monday, June 22, 2015 7:09:57 PM Subject: [ovirt-users] Upgrade to 3.5.3 fails on ovirt-engine-notifier service
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
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi, it's mentioned in [2] in section Detailed description [3], but I agree it could be made more visible :-( Also in RHEV 3.5 doc it's mentioned in [4], but again I agree it could be more visible. Martin [3] http://www.ovirt.org/Features/configuration-event-subscribers#Detailed_Descr... [4] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualizat... ----- Original Message -----
From: "Trey Dockendorf" <treydock@gmail.com> To: "Martin Perina" <mperina@redhat.com> Cc: "users" <users@ovirt.org> Sent: Monday, June 22, 2015 9:42:25 PM Subject: Re: [ovirt-users] Upgrade to 3.5.3 fails on ovirt-engine-notifier service
I thought using /usr/share/ovirt-engine was wrong, but I was going off of RedHat docs [1]. I didn't realize an alternative location existed.
Having just searched some more I found the oVirt docs [2] which I don't recall existing or mentioning the conf.d at the time I setup the notifier service.
Thanks, - Trey
[1]: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualizat... [2]: http://www.ovirt.org/Features/configuration-event-subscribers
On Mon, Jun 22, 2015 at 2:38 PM, Martin Perina <mperina@redhat.com> wrote:
Hi,
please never change anything in /usr/share/ovirt-engine, because these file will always be overwritten on RPM upgrades.
To change MAIL_SERVER for ovirt-engine-notifier please create config file (for example 99-user.conf) under /etc/ovirt-engine/notifier/notifier.conf.d and put you customizations here, for example:
MAIL_SERVER=my-mail-server.com
This way your changes survive upgrades.
Let me know if you have any other issues with it.
Thanks
Martin Perina
----- Original Message -----
From: "Trey Dockendorf" <treydock@gmail.com> To: "users" <users@ovirt.org> Sent: Monday, June 22, 2015 7:09:57 PM Subject: [ovirt-users] Upgrade to 3.5.3 fails on ovirt-engine-notifier service
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
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (2)
-
Martin Perina -
Trey Dockendorf