Project

General

Profile

Actions
Copy link

User story #5571

closed

Permit the nodes access rules to be reloaded automatically after each promises generation (was Promises are reloaded by cf-serverd only every 5 minutes)

Added by Nicolas CHARLES about 10 years ago. Updated almost 9 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Web - Config management
Target version:
2.11.4
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

cf-serverd reloads its promises only every 5 minutes, so when we accept new nodes, we may have to wait up to 5 minutes before it can receive its new promises

Subtasks 3 (0 open — 3 closed)

Bug #5573: Patch rudder-agent to have it understand SIGHUP to reload its promisesReleasedJonathan CLARKE2014-09-26Actions
Bug #5574: Have a configuration property to execute a post promise writing hookReleasedJonathan CLARKEActions
Bug #5732: Add migration script to add rudder.cfengine.reload.server.commandReleasedMatthieu CERDA2014-11-05Actions
Actions
Copy link
 #1

Updated by Nicolas CHARLES about 10 years ago

  • Tracker changed from Bug to User story
  • Subject changed from Promises are reloaded by cf-serverd only every 5 minutes to Permit the access rules ofnode to be reloaded automatically after each promises generation (was Promises are reloaded by cf-serverd only every 5 minutes)

The idea here is to have the cf-serverd reload its promises when SIGHUP'ed
It need one modification in cf-serverd, one on Rudder to configure this post-write hook (configurable), and then one migration script

Actions
Copy link
 #2

Updated by François ARMAND about 10 years ago

Why is that an user story ?

The behavior from the point of view of the user (coredumb) was a bug, because he nodes not getting their promises.

Moreover, targetting 2.11 is only for bugfixes.

For more context: the bug was introduced by CFEngine 3.6 that reloads promises far less frequently than precedent version were (and so why, as a bug correction, it should go to 2.11)

Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 10 years ago

Francois is right it should not be a user story...

But we fix a bug by adding new behavior ...

Actions
Copy link
 #4

Updated by Vincent MEMBRÉ about 10 years ago

  • Tracker changed from User story to Bug
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.11.4 to 2.11.5
Actions
Copy link
 #6

Updated by Jonathan CLARKE almost 10 years ago

  • Status changed from New to Pending technical review
Actions
Copy link
 #7

Updated by Jonathan CLARKE almost 10 years ago

  • Status changed from Pending technical review to Released
  • Target version changed from 2.11.5 to 2.11.4

This bug has been fixed in Rudder 2.11.4, which was released on November 18th 2014.

Actions
Copy link
 #8

Updated by Jonathan CLARKE almost 10 years ago

  • Subject changed from Permit the access rules ofnode to be reloaded automatically after each promises generation (was Promises are reloaded by cf-serverd only every 5 minutes) to Permit the nodes access rules to be reloaded automatically after each promises generation (was Promises are reloaded by cf-serverd only every 5 minutes)
Actions
Copy link
 #9

Updated by Benoît PECCATTE over 9 years ago

  • Category changed from 14 to Web - Config management
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ almost 9 years ago

  • Tracker changed from Bug to User story
Actions
Copy link

Also available in: Atom PDF