Skip to content
This repository has been archived by the owner on Nov 9, 2024. It is now read-only.

Rerunning bootstrap.sh as new user makes ansible use old python path (bad interpreter: Permission denied) #282

Open
2 tasks done
gratituliarity opened this issue Mar 13, 2024 · 0 comments
Assignees

Comments

@gratituliarity
Copy link

  • I've read the FAQ and my problem isn't described there.
  • I've also searched through the existing issues, and my problem hasn't been brought up

Describe the issue
The playbook copies the ansible-easy-vpn dir to the new user account but it cannot be run from there.
The Error states Permission denied because it still tries to use python from the old directory.

Logs

bootstrap.sh: /home/newUser/ansible-easy-vpn/.venv/bin/ansible-galaxy: /home/oldUser/ansible-easy-vpn/.venv/bin/python3: bad interpreter: Permission denied

Environment:

  • Client OS: Linux
  • Debian 12
@gratituliarity gratituliarity changed the title Rerunning playbook as new user uses old python path (bad interpreter: Permission denied) Rerunning bootstrap.sh as new user makes ansible use old python path (bad interpreter: Permission denied) Mar 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants