Project

General

Profile

Actions
Copy link

Bug #7451

closed

User story #7432: Don't copy files of local/50_techniques on the nodes

User story #7443: Call rudderify from rudder upgrade

After an upgrade to 3.2, the rudderified techniques are not commited, and not reread

Added by Nicolas CHARLES almost 9 years ago. Updated almost 9 years ago.

Status:
Released
Priority:
N/A
Assignee:
Benoît PECCATTE
Category:
Packaging
Target version:
3.2.0~beta1
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I upgraded from a nightly to 3.2, and got generation error because of conflicting arrity in logger_rudder

The rudder_reporting.st files are correct, but the generated cf are not
Updating techniques does not solve the issue

a git status shows the reason:

modified:   ../../../techniques/ncf_techniques/Network_configuration/1.0/rudder_reporting.st

We need to git add /var/rudder/configuration-repository/techniques/ncf_techniques and git commit, then reload the technique

Actions
Copy link

Also available in: Atom PDF