Project

General

Profile

Actions
Copy link

Bug #4148

closed

A node in an invalid time could lead to have 'No answer' state on the whole promises

Added by Cédric Cabessa about 11 years ago. Updated about 11 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas CHARLES
Category:
Web - Nodes & inventories
Target version:
2.8.1
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

On some occasion the rudder server get stuck: * the compliance of every rules is 0% * the "last seen" date of every node is not updated anymore (the date of the nodes are all in a +/- 5min window)

On the other hand, the "technical logs" of the node is OK
The node apply and fetch promises correctly (we can change an existing technique, and it will be applied on the nodes)

Workaround suggested by Vincent on IRC: * connect to the pgsql server * select * from statusupdate; show a date in the past (confirmation of the bug) * change this date to recent time (now - 10min for exemple)
update statusupdate set date='2013-11-13 16:15:00+01' where key='executionStatus'

The compliance should return back to 100% in a few minutes

Actions
Copy link
 #1

Updated by Vincent MEMBRÉ about 11 years ago

  • Status changed from New to 8
  • Assignee set to Vincent MEMBRÉ
  • Priority changed from N/A to 1 (highest)
  • Target version set to 2.8.1

Thank you Cédric for reporting.

We store the date of the latest report treated, which in your case in 1970 (time on the Android node you used).

We should instead store the maximum date in the batch we have just treated.

Actions
Copy link
 #2

Updated by Vincent MEMBRÉ about 11 years ago

  • Status changed from 8 to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/368
Actions
Copy link
 #3

Updated by Nicolas CHARLES about 11 years ago

  • Subject changed from Compliance 0% and "last seen" never updated to Compliance 0% and "last seen" can get never updated with node at invalid time
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ about 11 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #6

Updated by François ARMAND about 11 years ago

  • Assignee changed from François ARMAND to Nicolas CHARLES

Nicolas, please if you take the responsibility to review and merge, change the assignee before processing - it will avoid ducplicate work.

Actions
Copy link
 #7

Updated by Nicolas PERRON about 11 years ago

  • Subject changed from Compliance 0% and "last seen" can get never updated with node at invalid time to A node in a invalid time could lead to have 'No answer' state on the whole promises
Actions
Copy link
 #8

Updated by Nicolas PERRON about 11 years ago

  • Subject changed from A node in a invalid time could lead to have 'No answer' state on the whole promises to A node in an invalid time could lead to have 'No answer' state on the whole promises
Actions
Copy link
 #9

Updated by Nicolas PERRON about 11 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.8.1, which was released today.
Check out:

Actions
Copy link

Also available in: Atom PDF