Project

General

Profile

Actions

User story #5580

closed

Check the monotony of promises generation time on copy to nodes

Added by François ARMAND over 6 years ago. Updated over 5 years ago.

Status:
Released
Priority:
N/A
Category:
System techniques
Target version:
Suggestion strength:
User visibility:
Effort required:

Description

Today, an agent trying to update its promises is checking promises_generated file to know if they have changed and actually download them.

That file contains the datetime when the promises where generated, but only the hash of the file is check for modifiction, not that the actual datetime is more recent than the current one.

This will be problematic for any topology where a node can have several source for promises and theses sources can be out of sync, with really funny scenario where the node oscillated between several old and new set of promises.

The main idea is to be able to check the content of the file (that will need to contain a timestamp) and see if it's younger than the one in the machine (so that is implying that we need to proceed in two times, but we don't know if these two times are: 1/ download the file, 2/ check its content by comparing with the current one one node and update promises if necessary; OR 1/ download all promises in some directory; and 2/ compare and move promises directories around if necessary).


Subtasks 1 (0 open1 closed)

Bug #5612: Modify the rudder_promises_generated to contains a real timestampReleasedFrançois ARMAND2014-10-07Actions

Related issues

Related to Rudder - Bug #7796: Rudder agent does not detect when promise copy failedReleasedNicolas CHARLES2016-01-18Actions
Actions #1

Updated by Nicolas CHARLES over 6 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Nicolas CHARLES to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/531
Actions #2

Updated by Benoît PECCATTE over 6 years ago

  • Status changed from Pending technical review to Discussion
  • Assignee changed from Benoît PECCATTE to Nicolas CHARLES
Actions #3

Updated by Matthieu CERDA over 6 years ago

  • Target version changed from 140 to 3.0.0~beta1
Actions #4

Updated by Nicolas CHARLES over 6 years ago

  • Status changed from Discussion to Pending technical review
  • Assignee changed from Nicolas CHARLES to Jonathan CLARKE
Actions #5

Updated by Jonathan CLARKE over 6 years ago

  • Target version changed from 3.0.0~beta1 to 3.1.0~beta1
Actions #6

Updated by Benoît PECCATTE about 6 years ago

  • Assignee changed from Jonathan CLARKE to Benoît PECCATTE
Actions #7

Updated by Benoît PECCATTE about 6 years ago

  • Assignee changed from Benoît PECCATTE to Nicolas CHARLES
Actions #8

Updated by Nicolas CHARLES almost 6 years ago

it's been assigned to me, does it mean I need to update the pr ?

Actions #9

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 3.1.0~beta1 to 3.1.0~rc1
Actions #10

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 3.1.0~rc1 to 3.1.0
Actions #11

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 3.1.0 to 3.1.1
Actions #12

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 3.1.1 to 3.1.2
Actions #13

Updated by Jonathan CLARKE almost 6 years ago

  • Target version changed from 3.1.2 to 3.2.0~beta1
Actions #16

Updated by Nicolas CHARLES over 5 years ago

  • Assignee changed from Nicolas CHARLES to Jonathan CLARKE
  • Pull Request changed from https://github.com/Normation/rudder-techniques/pull/531 to https://github.com/Normation/rudder-techniques/pull/735
Actions #17

Updated by Jonathan CLARKE over 5 years ago

  • Tracker changed from Bug to User story
  • Subject changed from No check is done on the monotony of promises generation time to Check the monotony of promises generation time on copy to nodes
Actions #18

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from Pending technical review to Pending release
Actions #20

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending release to Released

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

Actions #21

Updated by Alexis MOUSSET over 5 years ago

  • Related to Bug #7796: Rudder agent does not detect when promise copy failed added
Actions

Also available in: Atom PDF