Actions
Bug #11088
closed
Bug #9807: When in changes only mode, with no heartbeat, 'rudder agent run' outputs 'error: Rudder agent was interrupted during execution by a fatal error.'
Backport "rudder.json" system variable files to 3.1
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
To correct parent task, we need to have the policy mode information in the CLI.
The best solution for that is create a new files with that information. That file exists in 4.2, it is "rudder.json". We need to backport that creation to 3.1.
There is no forseen compatibility problem since current agents don't expects "rudder.json", and next agent will have to handle the case where there is no rudder.json (because it only appears after a valid policy update).
Updated by François ARMAND over 7 years ago
- Status changed from New to In progress
Updated by François ARMAND over 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1710
Updated by Vincent MEMBRÉ over 7 years ago
- Related to Architecture #10936: Generate a "rudder.json" file containting system variables added
Updated by François ARMAND over 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|4804991960735a618b4cbbb6c96b02a2bfec4aae.
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from Pending release to Released
Updated by Alexis Mousset about 6 years ago
- Related to Architecture #10662: Generate a file containing the compliance mode added
Actions