Actions
Bug #15031
closed
reset and check commands break server in some cases
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
We should never remove common ncf on root server.
This is a template, please edit and remove what is not relevant.
I found this bug in Rudder version [Your Version here], on [Distribution here]
This bug happens:
- During installation of Rudder agent / Rudder server
- While running rudder agent on a Node
- When using Rudder web interface
- When looking at compliance of a Node
- When configurations are generated on Rudder Server
- When a Nodes applies a configuration
Description:
You can reproduce it with the following steps:
- ...
- ...
You can workaround this issue by doing likewise:
Updated by Alexis Mousset almost 5 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset almost 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-agent/pull/223
Updated by Alexis Mousset almost 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-agent|443347517c824ae1f5324191df7b01c9692e26bc.
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.0~beta1 which was released today.
Actions