Project

General

Profile

Actions

Bug #17456

closed

Hooks are being triggered at every start of apache or foreman-rake

Added by Marcel Gazdík over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Low
Category:
Usability
Target version:
-
Fixed in Releases:
Found in Releases:

Description

Description of problem:
RemoteExecutionFeature bugs are being triggered each time when the apache is started or when any foreman-rake command is being executed.

Version-Release number of selected component (if applicable):
0.3.0.11

How reproducible:
create "remote_execution_feature" folder in "/usr/share/foreman/config/hooks" and then create folder(s) named by the event which is related to operation save i. e.

  • after_commit
  • after_create

(see foreman-rake hooks:events[remote_execution_feature] for complete list)

and then create a script in the event folder. - ex:

$: cat 00-update-log.sh 
#!/bin/sh

LOG=/var/log/foreman/production.log
PREFIX="HOOK-EXEC:" 

echo "$PREFIX Hook execution detected \"$0\", params $#: " >> $LOG

CNT=0
[ "$#" != "0"  ] && while (( "$#" )); do 
        echo "$PREFIX $CNT: $1" >> $LOG
        CNT=$(($CNT + 1))
        shift 
done

echo "$PREFIX Hook stdin data: " >> $LOG
echo -n "$PREFIX " >> $LOG
cat >> $LOG
echo "" >> $LOG
echo "$PREFIX End of execution ($0)" >> $LOG

Actual results:
Script will be executed every time the foreman-rake command will be executed or during the start of apache (Passenger)

Expected results:
Script will be executed only if a new feature will be introduced or updated.


Related issues 1 (1 open0 closed)

Related to Foreman Remote Execution - Bug #17455: Hooks are being triggered at every start of apache or foreman-rakeNew11/23/2016Actions
Actions

Also available in: Atom PDF