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)

User story #5571: 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 almost 12 years ago. Updated over 10 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 CLARKEActions
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 CERDAActions

Updated by Nicolas CHARLES almost 12 years ago Actions
Copy link
 #1

  • 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

Updated by François ARMAND almost 12 years ago Actions
Copy link
 #2

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)

Updated by Vincent MEMBRÉ over 11 years ago Actions
Copy link
 #3

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

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

Updated by Vincent MEMBRÉ over 11 years ago Actions
Copy link
 #4

  • Tracker changed from User story to Bug

Updated by Vincent MEMBRÉ over 11 years ago Actions
Copy link
 #5

  • Target version changed from 2.11.4 to 2.11.5

Updated by Jonathan CLARKE over 11 years ago Actions
Copy link
 #6

  • Status changed from New to Pending technical review

Updated by Jonathan CLARKE over 11 years ago Actions
Copy link
 #7

  • 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.

Updated by Jonathan CLARKE over 11 years ago Actions
Copy link
 #8

  • 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)

Updated by Benoît PECCATTE over 11 years ago Actions
Copy link
 #9

  • Category changed from 14 to Web - Config management

Updated by Vincent MEMBRÉ over 10 years ago Actions
Copy link
 #10

  • Tracker changed from Bug to User story
Actions
Copy link

Also available in: PDF Atom