Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1397432 - Hooks are being triggered at every start of apache or foreman-rake
Summary: Hooks are being triggered at every start of apache or foreman-rake
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.2.2
Hardware: x86_64
OS: Linux
low
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-22 14:06 UTC by Marcel Gazdík
Modified: 2021-12-10 14:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 18:03:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 17455 0 None None None 2016-11-23 08:18:22 UTC

Description Marcel Gazdík 2016-11-22 14:06:23 UTC
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):
6.2.x

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.

Comment 4 Ivan Necas 2016-11-23 08:18:20 UTC
Created redmine issue http://projects.theforeman.org/issues/17455 from this bug

Comment 6 Bryan Kearney 2018-09-04 18:03:11 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


Note You need to log in before you can comment on or make changes to this bug.