Project

General

Profile

Actions

Bug #8845

closed

ncf.conf logger issues when updating from 3.1 to 3.2

Added by Florian Heigl over 8 years ago. Updated about 8 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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?


Related issues 2 (0 open2 closed)

Related to Rudder - Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params )ReleasedJonathan CLARKEActions
Related to Rudder - Bug #9416: Transient error during upgrade from 3.1 to 4.0RejectedActions
Actions

Also available in: Atom PDF