Bug #14995: When node configuration is updated, status becomes pending even if the node is sending very old reports - Rudder - Issue Tracker

Actions

Copy link

Bug #14995

open

When node configuration is updated, status becomes pending even if the node is sending very old reports

Added by Nicolas CHARLES almost 5 years ago. Updated about 15 hours ago.

Status:

New

Priority:

N/A

Assignee:

Category:

Web - Config management

Target version:

7.3.15

Pull Request:

Severity:

Major - prevents use of part of Rudder | no simple workaround

UX impact:

User visibility:

Operational - other Techniques | Rudder settings | Plugins

Effort required:

Small

Priority:

Name check:

Fix check:

Regression:

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

Capture du 2019-05-30 21-28-03.png (51.6 KB) Capture du 2019-05-30 21-28-03.png

Nicolas CHARLES, 2019-05-30 21:28

Related issues 1 (1 open — 0 closed)

Actions

Copy link

Updated by Nicolas CHARLES almost 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

Actions

Copy link

Updated by Nicolas CHARLES almost 5 years ago

Description updated (diff)

Actions

Copy link

Updated by Vincent MEMBRÉ almost 5 years ago

Target version changed from 5.0.12 to 5.0.13

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 5.0.13 to 5.0.14

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 5.0.14 to 5.0.15

Actions

Copy link

Updated by François ARMAND over 4 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?

Actions

Copy link

Updated by François ARMAND over 4 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

Actions

Copy link

Updated by Vincent MEMBRÉ over 4 years ago

Target version changed from 5.0.15 to 5.0.16
Priority changed from 63 to 62

Actions

Copy link

#10

Updated by Alexis Mousset about 4 years ago

Target version changed from 5.0.16 to 5.0.17
Priority changed from 62 to 59

Actions

Copy link

#11

Updated by Nicolas CHARLES about 4 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

Actions

Copy link

#12

Updated by Vincent MEMBRÉ about 4 years ago

Target version changed from 5.0.17 to 5.0.18
Priority changed from 58 to 57

Actions

Copy link

#13

Updated by Vincent MEMBRÉ almost 4 years ago

Target version changed from 5.0.18 to 5.0.19
Priority changed from 57 to 56

Actions

Copy link

#14

Updated by Vincent MEMBRÉ over 3 years ago

Target version changed from 5.0.19 to 5.0.20

Actions

Copy link

#15

Updated by Vincent MEMBRÉ over 3 years ago

Target version changed from 5.0.20 to 797

Actions

Copy link

#16

Updated by Benoît PECCATTE almost 3 years ago

Target version changed from 797 to 6.1.14

Actions

Copy link

#17

Updated by Vincent MEMBRÉ almost 3 years ago

Target version changed from 6.1.14 to 6.1.15

Actions

Copy link

#18

Updated by Vincent MEMBRÉ almost 3 years ago

Target version changed from 6.1.15 to 6.1.16

Actions

Copy link

#19

Updated by Vincent MEMBRÉ over 2 years ago

Target version changed from 6.1.16 to 6.1.17

Actions

Copy link

#20

Updated by Vincent MEMBRÉ over 2 years ago

Target version changed from 6.1.17 to 6.1.18

Actions

Copy link

#21

Updated by Vincent MEMBRÉ over 2 years ago

Target version changed from 6.1.18 to 6.1.19

Actions

Copy link

#22

Updated by Vincent MEMBRÉ about 2 years ago

Target version changed from 6.1.19 to 6.1.20

Actions

Copy link

#23

Updated by Vincent MEMBRÉ almost 2 years ago

Target version changed from 6.1.20 to 6.1.21

Actions

Copy link

#24

Updated by Vincent MEMBRÉ almost 2 years ago

Target version changed from 6.1.21 to old 6.1 issues to relocate
Priority changed from 56 to 57

Actions

Copy link

#25

Updated by François ARMAND 7 months 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

Actions

Copy link

#26

Updated by François ARMAND 7 months 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

Actions

Copy link

#27