Project

General

Profile

Actions

Bug #16017

closed

nodeslist.json can take up to 5 minutes to be updated after accepting a node

Added by Alexis Mousset over 4 years ago. Updated over 4 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:

Description

This makes the first report fail in some cases, so we should generate the nodeslist into /var/rudder/lib/relay/nodeslist.json directly, like we do for allnodescerts.pem.

This will allow immediate conf update and avoid latency.

Relays do not have this issue as policies are updated by the agent, so no extra latency is introduced.


Subtasks 3 (0 open3 closed)

Bug #16018: Do not copy nodeslist.json from inputs on root serverReleasedNicolas CHARLESActions
Bug #16022: Reload relayd when updating nodeslist.json on relaysReleasedNicolas CHARLESActions
Bug #16031: Broken policies after parentReleasedNicolas CHARLESActions
Actions

Also available in: Atom PDF