Actions
Bug #4192
closed
Technnique "Enforce a file content" v3.2: The use of deletion line causes Directive to be in a 'Unknown' state
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
With Rudder 2.6.8 the use of deletion line in Technique "Enforce a file content" v3.2 will causes Directive to be in 'Unknown' state.
All component will have the success reports but it seems that an extra reports about post-hook execution is made:
"No command for ... was to be executed"
Updated by Nicolas CHARLES over 10 years ago
I cannot reproduce this.
Could you give more details?
We need to know the parameters you setted in the Directive
Updated by Nicolas CHARLES over 10 years ago
- Status changed from New to Discussion
- Assignee set to Nicolas PERRON
Updated by Jonathan CLARKE over 10 years ago
- Status changed from Discussion to Rejected
I can't reproduce this either. I suspect you had some left over locks from a previously interrupted run to make this happen.
I'm rejecting the bug, but if this occurs again, feel free to reopen it. In which case, please provide exact details of the config you applied, and some technical logs.
Updated by Benoît PECCATTE about 9 years ago
- Project changed from 24 to Rudder
- Category set to Techniques
Updated by Benoît PECCATTE almost 9 years ago
- Is duplicate of Bug #4450: More than one message per directive added
Actions