Bug #5716
closed
Some Directives or Nodes may be missing from the reporting, in non compliance mode, during the "pending" period of time
Added by Nicolas CHARLES about 10 years ago.
Updated almost 10 years ago.
Category:
Web - Compliance & node report
Description
Randomly, there are missing Directives or Nodes in the Rules details
Didn't find the cause yet, but it seems some data are not correctly extracted from the expected reports (to confirm)
Files
|
1.png (39 KB)
1.png |
config |
Nicolas CHARLES, 2014-10-30 17:09
|
|
|
2.png (9.9 KB)
2.png |
report |
Nicolas CHARLES, 2014-10-30 17:09
|
|
Here, there is the configuration and reports of directives in a directive
there is one less directives in the reports than in the config
This happens in non-compliance mode; and only as long as node don't send there new reports (i prevented my nodes from updating their promises, so they keep sending their old reports, where there were only 3 Directives applied)
- Subject changed from Some Directives or Nodes may be missing from the reporting, randomly to Some Directives or Nodes may be missing from the reporting, in non compliance mode, during the "pending" period of time
ok, after a while (15 minutes apparently) it does reports current state (unexpected old reports)
i guess I'd like to know that new directive is pending, but it seems hard to track which directive changed (directive added is kind of easy, but directive change isn't as we don't store this info), hence the solution ought to be indeed all applying, or nothing till some nodes were speaking
The missing information is "The report concern the configuration at that time, which was that - and it happens that it is not the current one for the rule".
This information is very important, else you get situation like the one you are describing.
I'm not sure what we want to display (config date at least, that it's not the last too, and perhaps the diff with the actual ? And other things ?) and how.
- Target version changed from 3.0.0~beta1 to 3.0.0~beta2
- Parent task deleted (
#5293)
- Target version changed from 3.0.0~beta2 to 3.0.0~rc1
- Target version changed from 3.0.0~rc1 to 3.0.0
- Status changed from New to Rejected
With more investigation, it is also a consequence of #6021.
So a re defined #6021 and now closing this one as duplicate.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Jonathan CLARKE 
Updated by 
