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

Django_manage: manage.py must run via python #15443

Closed
swasher opened this issue Apr 16, 2016 · 1 comment
Closed

Django_manage: manage.py must run via python #15443

swasher opened this issue Apr 16, 2016 · 1 comment
Labels
bug This issue/PR relates to a bug.

Comments

@swasher
Copy link

swasher commented Apr 16, 2016

ISSUE TYPE
  • Bug Report
ANSIBLE VERSION
<!--- ansible 2.0.1.0 -->

but apply to all verions (i think)

CONFIGURATION

No specific configs

OS / ENVIRONMENT

Ubuntu 15.10 inside vagrant, with Django project on share folder

SUMMARY

I use ansible with vagrant, and my django project live in vagrant share. Vagrant prevent change file permission on share folders, so it always 664. File permission can not be changed per file.

Ansible try run django manage command as (migrate as example):

"cmd": "./manage.py migrate --noinput"

and fall with error

"msg": "[Errno 13] Permission denied", "rc": 13}

because manage.py is not executable (664).

Right way to launch manage with "python" command:

python manage.py migrate --noinput
@jctanner
Copy link
Contributor

jctanner commented Apr 25, 2016

Hi!

Thanks very much for your interest in Ansible. It sincerely means a lot to us.

On September 26, 2014, due to enormous levels of contribution to the project Ansible decided to reorganize module repos, making it easier
for developers to work on the project and for us to more easily manage new contributions and tickets.

We split modules from the main project off into two repos, http://github.com/ansible/ansible-modules-core and http://github.com/ansible/ansible-modules-extras

If you would still like this ticket attended to, we will need your help in having it reopened in one of the two new repos, and instructions are provided below.

We apologize that we are not able to make this transition happen seamlessly, though this is a one-time change and your help is greatly appreciated --
this will greatly improve velocity going forward.

Both sets of modules will ship with Ansible, though they'll receive slightly different ticket handling.

To locate where a module lives between 'core' and 'extras'

Additionally, should you need more help with this, you can ask questions on:

Thank you very much!

@ansibot ansibot added bug This issue/PR relates to a bug. and removed bug_report labels Mar 7, 2018
@ansible ansible locked and limited conversation to collaborators Apr 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug This issue/PR relates to a bug.
Projects
None yet
Development

No branches or pull requests

4 participants