Actions
Bug #16017
closed
nodeslist.json can take up to 5 minutes to be updated after accepting a node
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
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.
Updated by Alexis Mousset about 5 years ago
- Status changed from New to In progress
- Assignee changed from Nicolas CHARLES to Alexis Mousset
Updated by Alexis Mousset about 5 years ago
- Status changed from In progress to New
- Assignee changed from Alexis Mousset to Nicolas CHARLES
Updated by Nicolas CHARLES about 5 years ago
- Status changed from New to In progress
Updated by Nicolas CHARLES about 5 years 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
Updated by Nicolas CHARLES about 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|482a68a6b0b9998be1628e4aa51b12cc79f4aa37.
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.0~beta1 which was released today.
Actions