Project

General

Profile

Actions
Copy link

Bug #16017

closed

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

Added by Alexis Mousset about 5 years ago. Updated about 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Web - Config management
Target version:
6.0.0~beta1
Pull Request:
https://github.com/Normation/rudder/p...
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 open — 3 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
Copy link

Also available in: Atom PDF