-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
AWX not syncing Gitlab project: ORIGIN not a git repository #15672
Comments
I tried to change credentials type, even if project is public. Switched between:
Same error. |
Full job log: `ansible-playbook [core 2.15.12] PLAYBOOK: project_update.yml *************************************************** PLAY [Update source tree if necessary] ***************************************** TASK [Delete project directory before update] ********************************** TASK [Update project using git] ************************************************ PLAY RECAP ********************************************************************* |
@batreseau for extra testing, are you able to point this at a public/private github repo to test? This error seems pretty generic of not being able to find the repo. And to double check, since you redacted the URLs, can you confirm that the command that you ran in the task container is the same that was run by the playbook? We were unable to reproduce on devel. |
@thedoubl3j thank you for you answer ! Im redeploying with 24.5.0 and will test again . |
So, what an interesting afternoon ... But i finally made it worked :) To make it quick : root cause was permissions issue on projects folder . Deployed on kubernetes as RWX pvc, it's using NFS protocol to provision volume. On NFS backend, Root Squash Security was enabled with a rule that say: if storage domain =! client domain, rewrite root perms to nobody. After patching, going back to 24.6.1, permissions were as expected in container and clone worked. Thank you @thedoubl3j for time spent on my issue. Best regard |
glad you got things working @batreseau |
Please confirm the following
[email protected]
instead.)Bug Summary
Hello community !
I'm facing an issue configuringAWX to pull from a Gitlab instance.
More context:
Thank you for help you can provide :)
AWX version
24.6.1
Select the relevant components
Installation method
kubernetes
Modifications
no
Ansible version
core 2.15.12
Operating system
Oracle Linux 9
Web browser
Chrome, Edge
Steps to reproduce
Expected results
Project is downloaded from gitlab and ready to be used
Actual results
Project sync failed to be performed with following error :
{ "cmd": "/usr/bin/git ls-remote origin -h refs/heads/main", "rc": 128, "stdout": "", "stderr": "fatal: 'origin' does not appear to be a git repository\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n", "msg": "fatal: 'origin' does not appear to be a git repository\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.", "invocation": { "module_args": { "dest": "/var/lib/awx/projects/_10__test", "repo": "https://mygitlab.corp/myrepo.git", "version": "main", "force": true, "track_submodules": false, "remote": "origin", "clone": true, "update": true, "verify_commit": false, "gpg_whitelist": [], "accept_hostkey": false, "accept_newhostkey": false, "bare": false, "recursive": true, "single_branch": false, "refspec": null, "reference": null, "depth": null, "key_file": null, "ssh_opts": null, "executable": null, "umask": null, "archive": null, "archive_prefix": null, "separate_git_dir": null } }, "stdout_lines": [], "stderr_lines": [ "fatal: 'origin' does not appear to be a git repository", "fatal: Could not read from remote repository.", "", "Please make sure you have the correct access rights", "and the repository exists." ], "_ansible_no_log": false, "changed": false }
Additional information
If i'm connecting in awx-tasks container and performing:
/usr/bin/git ls-remote https://mygitlab.corp/myrepo.git -h refs/heads/main
Its working well .
The text was updated successfully, but these errors were encountered: