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.

Sign up for GitHub

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

Jump to bottom

ansible-galaxy install throws an error when the role-file option is used. #11179

Closed
bandesz opened this issue Jun 5, 2015 · 6 comments
Closed

ansible-galaxy install throws an error when the role-file option is used. #11179

bandesz opened this issue Jun 5, 2015 · 6 comments
Labels
bug This issue/PR relates to a bug. P1 Priority 1 - Immediate Attention Required; Release Immediately After Fixed
Milestone
2.0

Comments

@bandesz
Copy link

bandesz commented Jun 5, 2015

Issue Type:

Bug Report

Ansible Version:
ansible 2.0.0 (devel a4ebee4b16) last updated 2015/06/05 11:02:21 (GMT +000)
  lib/ansible/modules/core: (detached HEAD b138411671) last updated 2015/06/05 11:02:40 (GMT +000)
  lib/ansible/modules/extras: (detached HEAD 1276420a3a) last updated 2015/06/05 11:03:14 (GMT +000)
  v1/ansible/modules/core: (detached HEAD f8d8af17cd) last updated 2015/06/05 11:04:10 (GMT +000)
  v1/ansible/modules/extras: (detached HEAD 495ad450e5) last updated 2015/06/05 11:04:48 (GMT +000)
  configured module search path = None
Environment:

Debian 8.0

Summary:

ansible-galaxy install throws an error when the role-file option is used.

Steps To Reproduce:
$ ansible-galaxy install -r requirements-roles-3rd.yml -p ./roles-3rd/
Expected Results:

Great success.

Actual Results:
Traceback (most recent call last):
  File "/home/vagrant/ansible/bin/ansible-galaxy", line 66, in <module>
    sys.exit(cli.run())
  File "/home/vagrant/ansible/lib/ansible/cli/galaxy.py", line 134, in run
    self.execute()
  File "/home/vagrant/ansible/lib/ansible/cli/__init__.py", line 96, in execute
    fn()
  File "/home/vagrant/ansible/lib/ansible/cli/galaxy.py", line 321, in execute_install
    role_name = self.args.pop(0).strip()
IndexError: pop from empty list
@bandesz bandesz mentioned this issue Jun 5, 2015
Closed
@bcoca bcoca added bug_report P1 Priority 1 - Immediate Attention Required; Release Immediately After Fixed labels Jun 5, 2015
@bcoca
Copy link
Member

bcoca commented Jun 5, 2015

I had not finished implementing all galaxy functions, this is high on my todo list.

@bcoca bcoca added this to the v2 milestone Jun 6, 2015
@dkinzer
Copy link

dkinzer commented Jun 16, 2015

I'm getting this same error:

#ansible --version:
ansible 2.0.0 (devel 4705a79a98) last updated 2015/06/16 11:04:58 (GMT -400)
  lib/ansible/modules/core: (detached HEAD 9acc7c402f) last updated 2015/06/16 11:05:01 (GMT -400)
  lib/ansible/modules/extras: (detached HEAD 2f967a949f) last updated 2015/06/16 11:05:03 (GMT -400)
  v1/ansible/modules/core: (detached HEAD f8d8af17cd) last updated 2015/06/16 11:05:04 (GMT -400)
  v1/ansible/modules/extras: (detached HEAD 495ad450e5) last updated 2015/06/16 11:05:06 (GMT -400)
  configured module search path = None
#uname
Linux linux 3.13.0-53-generic #89-Ubuntu SMP Wed May 20 10:34:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

@bcoca
Copy link
Member

bcoca commented Jun 16, 2015

expected, as I mentioned above this has not been implemented yet

This was referenced Jul 4, 2015
Closed
Closed
@chouseknecht
Copy link
Contributor

@bcoca - started looking into 11548 and ended up here. After getting past the error on line 321 (Index error: pop form empty list) I hit the missing 'role_yaml_parse', which used to be part of ansible.utils.

Guessing maybe things are not completely done with the move to v2. I'm way out of the loop as far as the strategy with the bits left in v1/utils. Is there anything I can do to help?

Would love to chat and catch up. Will be starting back at Ansible on 7/20 to work on Galaxy. In the meantime, feel free to reach out to me - chouseknecht at gmail.

--Chris

@bcoca
Copy link
Member

bcoca commented Jul 11, 2015

v1/ is there for testing convenience, it won't survive the release of 2.0 and won't be included anywhere, this was left so people did not have to switch to the last_v1 tag to test if an issue was cause by the v2 engine.

I'll get back to this next week and see where we are at, some people had already started adding this back.

@bcoca bcoca closed this as completed in 96bcf50 Jul 29, 2015
@jimi-c
Copy link
Member

jimi-c commented Jul 29, 2015

Closing This Ticket

Hi!

We believe the above commit should resolve this problem for you. This will also be included in the next major release.

If you continue seeing any problems related to this issue, or if you have any further questions, please let us know by stopping by one of the two mailing lists, as appropriate:

Because this project is very active, we're unlikely to see comments made on closed tickets, but the mailing list is a great way to ask questions, or post if you don't think this particular issue is resolved.

Thank you!

@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.
Assignees
No one assigned
Labels
bug This issue/PR relates to a bug. P1 Priority 1 - Immediate Attention Required; Release Immediately After Fixed
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
6 participants
@jimi-c @dkinzer @bcoca @bandesz @chouseknecht @ansibot