Skip to content
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

oec service trying to call actionExecutor.py using python2 with missing modules when python3 works. No env in actionExecutor.py. #95

Open
ipaqmaster opened this issue Dec 15, 2022 · 1 comment

Comments

@ipaqmaster
Copy link

Should actionExecutor.py have an explicit python env set at the top of the file?

In my case I cannot execute remote Opsgenie2Nagios commands because actionExecutor.py doesn't specify a hashbang at the start of the file to pick a specific interpreter

@ipaqmaster
Copy link
Author

According to opsgenie/oec#49 it seems the service is the one targeting python and relying on the system default. It is ingoring any mention of #!/usr/bin/python3 at the top of the file. Seems to be an outstanding problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant