New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
action linux.service or linux.check_processes cannot be executed on remote host #5983
Comments
Further info/output: st2 run linux.check_processes search=name username=****** hosts=****** criteria=****** ~ |
The actions in the |
The python interpreter was deliberately altered: |
That sounds like a bug. The intent I believe is to have the pack actions working remotely. If you folks change the shebang python path in the script header, does the action work properly? |
I modify shebang python path to
|
Why not switch back? #!/usr/bin/env python3 |
Yep, please open a PR and it's worth checking if pack still works in CentOS8 per #5035. |
@armab |
SUMMARY
Get error "/opt/stackstorm/st2/bin/python: bad interpreter: No such file or directory" while using the corresponding actions.
The actions will be executed on a remote host and not on the stack storm controller.
On the remote host is stackstorm not installed and therefore the path does not exist.
The path exists on my stackstorm controller.
STACKSTORM VERSION
Paste the output of
st2 --version
: st2 3.8.0, on Python 3.8.13OS, environment, install method
Post what OS you are running this on, along with any other relevant information/
Steps to reproduce the problem
Affected (tested) actions: linux.service and linux.check_processes
Error notification:
{
"***********": {
"stdout": "",
"stderr": "bash: /tmp/6479d198cc128630e940fb88/service.py: /opt/stackstorm/st2/bin/python: bad interpreter: No such file or directory",
"return_code": 126,
"succeeded": false,
"failed": true
}
}
Expected Results
Get status of the services in linux.services or status of the process in linux.check_processes.
Actual Results
See Error notification.
The text was updated successfully, but these errors were encountered: