Project

General

Profile

Actions

Bug #25498

closed

Hooks are not executed anymore from their directory

Added by François ARMAND 2 months ago. Updated about 2 months ago.

Status:
Released
Priority:
2
Category:
Web - Config management
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

In Rudder 8.1, the execution path ("cwd") of hooks has changed.

They used to be seen as executed from their parent directory, so that for example "/opt/rudder/etc/hooks.d/policy-generation-finished/hello" was seen as executed from "/opt/rudder/etc/hooks.d/policy-generation-finished/hello".
Now, they are seen as executed from "/root".

Actions #1

Updated by François ARMAND 2 months ago

This might be linked to an update to nuprocess, since we don't seem to fix the CWD, while now, there is a:
NuProcessBuilder.setCwd(Path cwd) : Set the Path to which the current working directory (cwd) of the subsequent launch of a NuProcess will be set when calling the start() method.

Actions #2

Updated by François ARMAND 2 months ago

  • Status changed from New to In progress
Actions #3

Updated by François ARMAND 2 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/5889
Actions #4

Updated by François ARMAND 2 months ago

  • Priority changed from N/A to 2
Actions #5

Updated by Anonymous 2 months ago

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

Updated by Vincent MEMBRÉ about 2 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 8.1.7 which was released today.

Actions

Also available in: Atom PDF