Project

General

Profile

Actions

Bug #5414

closed

Bug #5402: Agent can't run because some ncf promises are CFEngine 3.6 specific

Change location of the script used by Rudder to get compatible promises to solve migration issue

Added by Nicolas CHARLES about 8 years ago. Updated almost 8 years ago.

Status:
Released
Priority:
1
Assignee:
Matthieu CERDA
Category:
-
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

Description

The script list-compatible-inputs is bundled with ncf, but used by Rudder techniques
However we don't have strong dependency between Rudder and ncf (one can update Rudder without ncf)
Plus, as the script is used in the ncf folder, existing promises will make it non-executable, so the promise generation will fail, as they relies on it being executable

So, we decided to have packaging put it into /var/rudder/tools (the other ticket), and have the promises use it from this location

Actions #1

Updated by Nicolas CHARLES about 8 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Matthieu CERDA
Actions #2

Updated by Nicolas CHARLES about 8 years ago

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

Applied in changeset commit:bd6e203a4726bf8786f520d0af31f8f563cb846b.

Actions #3

Updated by Matthieu CERDA about 8 years ago

Applied in changeset commit:1d72cdfb3c3f8092b6eda7fa9cfb56029c600839.

Actions #4

Updated by Vincent MEMBRÉ almost 8 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.5, which was released on the 28/08/2014.

Actions

Also available in: Atom PDF