Project

General

Profile

Actions

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)
Category:
Web - Nodes & inventories
Target version:
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

Also available in: Atom PDF