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

Git submodule does not show the error message #8596

Closed
abrahammartin opened this issue Aug 13, 2014 · 3 comments
Closed

Git submodule does not show the error message #8596

abrahammartin opened this issue Aug 13, 2014 · 3 comments
Labels
bug This issue/PR relates to a bug.

Comments

@abrahammartin
Copy link

Issue Type:

Feature Idea

Ansible Version:

ansible 1.6.10

Environment:

N/A

Summary:

I had a wrong permission in one of the files inside my .git folder but the git submodule didn't show the error message, only a very generic "msg: Failed to download remote objects and refs". I believe that the git submodule should show the error message that git is showing, so you do not have to log in and execute the command by yourself to check the error and see what happened.

Steps To Reproduce:

Just change the permissions of some files inside the .git to some that the ansible user cannot read/write

Expected Results:

The actual error

Actual Results:

"msg: Failed to download remote objects and refs"

@mpdehaan
Copy link
Contributor

Can you please show the line you are using from the playbook task entry?

Thanks!

@abrahammartin
Copy link
Author

@mpdehaan
Copy link
Contributor

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 6, 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

3 participants