Project

General

Profile

Actions

Bug #2855

closed

Rudder doesn't properly checks the folder name for techniques when writing them

Added by Nicolas CHARLES over 12 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
1 (highest)
Category:
Web - Config management
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

If we have another folder in the /var/rudder/configuration-repository with the same file hierarchy than the techniques folders, then when writing promises (not at any other moment), the files read might come from the other folder.

Step to reproduce :
  1. Copy the /var/rudder/configuration-repository/techniques to policies
  2. Garble completely the content of the files in /var/rudder/configuration-repository/policies
  3. add the /var/rudder/configuration-repository/policies folder to the git, and commit it
  4. do a modification (simple) in the /var/rudder/configuration-repository/techniques, and commit it (this step is mandatory for rudder to reload the technique lib)
  5. reload the technique library

Some files in the generated promises will be garbled (not all)

Note : I'm not sure if it would happen in 2.3.9, but that's most likely

Actions #1

Updated by François ARMAND over 12 years ago

  • Status changed from New to Pending technical review
  • % Done changed from 0 to 100

Applied in changeset commit:714d83a1fa6bce179ef4ed3316117f906b275578.

Actions #2

Updated by Nicolas CHARLES over 12 years ago

  • Status changed from Pending technical review to Released

this looks valid, thank you Francois

Actions #3

Updated by Benoît PECCATTE almost 10 years ago

  • Category changed from 14 to Web - Config management
Actions

Also available in: Atom PDF