Bug #8845
closedncf.conf logger issues when updating from 3.1 to 3.2
Description
Hi,
I've had two cases now where I ended up with broken NCF.
My techniques would all still try to use log_rudder with two arguments instead of four.
I helplessly changed them to use logger_rudder, which breaks reports with a deprecation warning.
From what I can see the reason is that ncf.conf isn't updated by the rpm, instead it'll make a ncf.conf.rpmnew
So the new default logger is never put in place.
if anything re-runs a rudderify for all existing ncf techniques during the upgrade this would have no effect since
the config in place is in fact an old one.
OS CentOS, old Rudder version 3.1.9, new rudder version 3.2.5
And, incidentially since this breaks my demos, Is there a way to easily bulk-upgrade the NCF techniques?
How's it meant to happen?