Actions
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
Pull Request:
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
Updated by Jonathan CLARKE about 9 years ago
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Parent task set to #7443
Updated by Jonathan CLARKE about 9 years ago
- Status changed from New to In progress
- Assignee changed from Benoît PECCATTE to Jonathan CLARKE
Updated by Jonathan CLARKE about 9 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/806
Updated by Jonathan CLARKE about 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-packages|91e6cedf43d982711fd798ed3982a60ddec470a1.
Updated by Benoît PECCATTE about 9 years ago
Applied in changeset rudder-packages|9be20d5feaeaf6b31efeccfc6d98ffa3a1fd5610.
Updated by Vincent MEMBRÉ about 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.2.0~beta1 which was released today.
Actions