Bug #14995
openWhen node configuration is updated, status becomes pending even if the node is sending very old reports
Description
One node sends reports from a configuration dating 15:22
Several policy generation happened in a row since, and i get following status
This node has recently been assigned a new policy but no reports have been received for the new policy yet. This is expected, the node is reporting on the previous configuration policy and should report on the new one at latest 2019-05-30 19:34:06. Previous known states are displayed below. The latest reports received for this node are from a run started at 2019-05-30 19:24:06 with configuration ID 20190529-155230-4fa56379. Current configuration ID for this node is '20190530-191237-a0dac60d' (generated on 2019-05-30 19:12:37).
Every time, the "should report on the latest one" is in 10 minutes.
Since the node is still sending reports for a configuration that is very old, Rudder should know that it is not updating its configuration, and so Rudder should not say "pending", but "error".
Files
Updated by Nicolas CHARLES over 5 years ago
- Related to Enhancement #14458: Compliance color in node list is misleading when a node hasn't answered for a long long time added
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.12 to 5.0.13
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.13 to 5.0.14
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.14 to 5.0.15
Updated by François ARMAND about 5 years ago
I'm not sure I understand the problem, trying to re say it: the last generation happened at 19:12. So the run from 19:24 should have been for that generation, not the old one from 15:22 for which the node is. Is it that?
Updated by François ARMAND about 5 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Effort required set to Small
- Priority changed from 0 to 63
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.15 to 5.0.16
- Priority changed from 63 to 62
Updated by Alexis Mousset almost 5 years ago
- Target version changed from 5.0.16 to 5.0.17
- Priority changed from 62 to 59
Updated by Nicolas CHARLES almost 5 years ago
- Priority changed from 59 to 58
No, the issue is that it's still in "pending" mode, while it should clearly be in Error, as the node didn't update and was sending data older than the grace period
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.17 to 5.0.18
- Priority changed from 58 to 57
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.18 to 5.0.19
- Priority changed from 57 to 56
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.19 to 5.0.20
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 5.0.20 to 797
Updated by Benoît PECCATTE over 3 years ago
- Target version changed from 797 to 6.1.14
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.14 to 6.1.15
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.15 to 6.1.16
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.16 to 6.1.17
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.17 to 6.1.18
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.18 to 6.1.19
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.19 to 6.1.20
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.20 to 6.1.21
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.21 to old 6.1 issues to relocate
- Priority changed from 56 to 57
Updated by François ARMAND about 1 year ago
- Subject changed from Invalid configuration status for node sending old reports to When node configuration is update, it's in pending even if the node is sending very old reports
- Description updated (diff)
- Target version changed from old 6.1 issues to relocate to 7.3.8
- Priority changed from 57 to 0
- Regression set to No
Updated by François ARMAND about 1 year ago
- Subject changed from When node configuration is update, it's in pending even if the node is sending very old reports to When node configuration is updated, status becomes pending even if the node is sending very old reports
d
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.8 to 7.3.9
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.9 to 7.3.10
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.10 to 7.3.11
Updated by Vincent MEMBRÉ 11 months ago
- Target version changed from 7.3.11 to 7.3.12
Updated by Vincent MEMBRÉ 10 months ago
- Target version changed from 7.3.12 to 7.3.13
Updated by Vincent MEMBRÉ 10 months ago
- Target version changed from 7.3.13 to 7.3.14
Updated by Vincent MEMBRÉ 8 months ago
- Target version changed from 7.3.14 to 7.3.15
Updated by Vincent MEMBRÉ 7 months ago
- Target version changed from 7.3.15 to 7.3.16
Updated by Vincent MEMBRÉ 6 months ago
- Target version changed from 7.3.16 to 7.3.17