Bug #7971
closed
Non applicable reports "Not applicable is not applicable" are useless and can be duplicates, breaking reporting
Added by Vincent MEMBRÉ over 8 years ago.
Updated over 2 years ago.
Description
Sometimes we get a report message that is clearly useless: Not applicable is not applicable
We should replace it ...
I guess it's in ncf reporting added by Rudder but I may be wrong
- Project changed from Rudder to 41
- Target version set to 0.x
- Subject changed from Replace "Not applicable is not applicable" in reports message to Non applicable reports "Not applicable is not applicable" are useless and can be duplicates, breaking reporting
This is even worse than just useless reports actually. If we have several cases, for example:
SLES10: package_install("a")
SLES11: package_install("b")
Then two "Not applicable is not applicable" reports for the same technique will be generated, and only one will actually be sent.
We should include the name of the generic method and key parameter of the call that is "not applicable".
- Status changed from New to In progress
- Assignee set to Jonathan CLARKE
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/ncf/pull/391
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset commit:03c4e6a126b21af3fdf5c6bfa47e16bc3f32f73e.
- Status changed from Pending release to Released
- Target version changed from 0.x to ncf-0.x
- Priority set to 0
- Project changed from 41 to Rudder
- Category set to Generic methods
Also available in: Atom
PDF
Updated by 
Updated by Jonathan CLARKE 
Updated by