after few action execution failed attempts due to any reason, error changes to : ' Error 2 File or directory not found : "path to entrypoint file" '
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
SUMMARY
Action execution failed due to St2 GUI not able to render password stored as secret.
After few attempts error changes to error : [ ERROR 2 ] No such file or directory "Absolute path to entry point script"
Although File exists and action was working manually before last attempt.
This happened where action failed few times for any reason like
- kerberos not installed error
- Credentials rejected by the server
In both cases after 7-8 attempts st2 give different error
STACKSTORM VERSION
st2 3.1.0, On Python 2.7.5
OS, environment, install method
OS : RHEL 7.7
Steps to reproduce the problem
use ntlm to connect to windows server to execute action ( using winrm-ps-script runner )
Provide wrong user name format like : user/domain, domain/user, domain@user etc
Expected Results
St2 should throw exception: credentials rejected by server no matter how many times we try
Actual Results
after 7-8 attempts : Error changes to : No such file or directory.
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the winrm-ps-script runner and reproduce the failure using invalid NTLM credentials, including repeated attempts after the initial error. Done means repeated failures continue to report the credential or server rejection rather than changing to a misleading missing-entrypoint-file error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100