Project

General

Profile

Bug #16017

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

Added by Alexis MOUSSET 26 days ago. Updated 12 days ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

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

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

Associated revisions

Revision 482a68a6 (diff)
Added by Nicolas CHARLES 25 days ago

Fixes #16017: nodeslist.json can take up to 5 minutes to be updated after accepting a node

History

#1

Updated by Alexis MOUSSET 26 days ago

  • Status changed from New to In progress
  • Assignee changed from Nicolas CHARLES to Alexis MOUSSET
#2

Updated by Alexis MOUSSET 26 days ago

  • Status changed from In progress to New
  • Assignee changed from Alexis MOUSSET to Nicolas CHARLES
#3

Updated by Nicolas CHARLES 26 days ago

  • Status changed from New to In progress
#4

Updated by Nicolas CHARLES 26 days ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder/pull/2544
#5

Updated by Nicolas CHARLES 25 days ago

  • Status changed from Pending technical review to Pending release
#6

Updated by Vincent MEMBRÉ 12 days ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.0.0~beta1 which was released today.

Also available in: Atom PDF