Bug #8845
closed
ncf.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?
Updated by François ARMAND about 8 years ago
- Status changed from New to Rejected
- Target version set to 3.2.7
The process is taken part as of rudder-upgrade, and the code says it does take care of ncf.conf and rudderify techniques again. So we need to understand why it does not work :)
We did have broken reports in ncf in 3.2.5 ( #8475 and then #8826 ), which are now corrected in the coming 3.2.6. So maybe the problem was due to that.
I'm going to close that one, but please report if you still have problem with 3.2.6.
Updated by François ARMAND about 8 years ago
- Related to Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ) added
Updated by Nicolas CHARLES about 8 years ago
- Related to Bug #9416: Transient error during upgrade from 3.1 to 4.0 added