-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
make test_galaxy fails #11486
Comments
i'm still in the process of reworking the interaction with roles for the install function, most of the other functionality is there. |
closing as dupe of #11179 |
semifocused
added a commit
to 47lining/ansible
that referenced
this issue
Sep 28, 2015
…ests pass. It appears that all roles are installed as intended, but an ansible playbook issue remains when finding dependent roles. Partially addresses ansible#11486.
willthames
added a commit
to willthames/ansible
that referenced
this issue
Oct 22, 2015
ansible-playbook now works when run with a playbook that includes a role that includes another role specified using csv format Updated one of the roles used in the tests to fix broken tests - `make test_galaxy` now works Fixes ansible#11486. Also addresses the problem alluded to in ansible#10620.
photoninger
pushed a commit
to photoninger/ansible
that referenced
this issue
Oct 26, 2015
ansible-playbook now works when run with a playbook that includes a role that includes another role specified using csv format Updated one of the roles used in the tests to fix broken tests - `make test_galaxy` now works Fixes ansible#11486. Also addresses the problem alluded to in ansible#10620.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A lot of code that was at the heart of ansible-galaxy has been ripped out and not replaced.
This means that make test_galaxy trivially fails
We need something to replace ansible.utils.role_yaml_parse and ansible.utils.role_spec_parse, and make test_galaxy should pass its tests (those tests exist for a reason!)
The text was updated successfully, but these errors were encountered: