Project

General

Profile

Actions

Bug #8346

closed

rudder agent update doesn't always update policy

Added by Jonathan CLARKE almost 5 years ago. Updated almost 5 years ago.

Status:
Released
Priority:
N/A
Category:
Agent
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

We use several flag files to copy policy (promises, ncf, tools) from the Rudder server to Rudder nodes. The way these are used is:
1) Copy flag file
2) Check if copy changed flag file
3) If there was a change, start copy of main contents

However, if step 3 gets interrupted, or fails for any reason (not enough space on device, network issue, user killed process, etc), the next "update" will stop at step 2 (there will be no change to the flag file).

"rudder agent update" should be able to get around this, using a "force/-f" flag.


Subtasks 1 (0 open1 closed)

Bug #8347: rudder agent update doesn't always update policy - also force ncf updateRejectedJonathan CLARKE2016-05-19Actions
Actions #1

Updated by Jonathan CLARKE almost 5 years ago

  • Status changed from New to In progress
Actions #2

Updated by Jonathan CLARKE almost 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-agent/pull/65
Actions #3

Updated by Jonathan CLARKE almost 5 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #4

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.16, 3.1.10 and 3.2.3 which were released on 2016-06-01, but not announced.

Actions

Also available in: Atom PDF