Actions
Bug #6089
closedenforce file content post modification hook if section is modified but global state of the file is not changed
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
In case when we do several modificaiton at once on a file, we may have sub-part in repaired (like section), and a global state kept (because another change applied as well).
However, the condition on command execution is a bit laxist:
execute_command_$(index).!(content_$(index)_failed|content_deletion_failed_$(index)|content_modification_failed_$(index)).(content_$(index)_modified|content_deletion_modified_$(index)|content_modification_modified_$(index)|section_content_modification_modified_${index})
as it doesn't take into account file_edition_global_files_status_XX_kept
This happens on version 5.0 of the technique, but may also happen on 6.0
Updated by Benoît PECCATTE almost 10 years ago
- Status changed from New to Pending technical review
- Assignee changed from Benoît PECCATTE to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/627
Updated by Nicolas CHARLES almost 10 years ago
- Status changed from Pending technical review to Rejected
Oh, actually, I was babbling nonsence in this ticket, the issue was fixed in http://www.rudder-project.org/redmine/issues/5312, but we had a previous version of the technique, and didn't check.
I'm sorry to have wasted your time Benoît :(
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.10.9 to 2.10.10
Actions