Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

molecule init role my-role-name failed

See original GitHub issue

Issue Type

Bug report

Molecule and Ansible details

% ansible --version && molecule --version
ansible 2.8.10
  config file = None
  configured module search path = ['/home/shirokih/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/shirokih/.local/lib/python3.6/site-packages/ansible
  executable location = /home/shirokih/.local/bin/ansible
  python version = 3.6.9 (default, Nov  7 2019, 10:44:02) [GCC 8.3.0]
molecule 3.0.3
   ansible==2.8.10 python==3.6

Molecule installation method (one of):

Ansible installation method (one of):

Detail any linters or test runners used:

Desired Behavior

molecule init role my-role creates diras and finiched with $0

Actual Behaviour

molecule init role my-role
--> Initializing new role my-role...
ERROR: Galaxy failed to create role: Command '['ansible-galaxy', 'init', '-v', '--offline', 'my-role']' returned non-zero exit status 250.: No config file found; using defaults
ERROR! Unexpected Exception, this is probably a bug: no filter named 'comment_ify'
to see the full traceback, use -vvv

because of

% ansible-galaxy init -vvv --offline my-role
ansible-galaxy 2.8.10
  config file = None
  configured module search path = ['/home/shirokih/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/shirokih/.local/lib/python3.6/site-packages/ansible
  executable location = /home/shirokih/.local/bin/ansible-galaxy
  python version = 3.6.9 (default, Nov  7 2019, 10:44:02) [GCC 8.3.0]
No config file found; using defaults
Opened /home/shirokih/.ansible_galaxy
ERROR! Unexpected Exception, this is probably a bug: no filter named 'comment_ify'
the full traceback was:

Traceback (most recent call last):
  File "/home/shirokih/.local/bin/ansible-galaxy", line 110, in <module>
    exit_code = cli.run()
  File "/home/shirokih/.local/lib/python3.6/site-packages/ansible/cli/galaxy.py", line 149, in run
    self.execute()
  File "/home/shirokih/.local/lib/python3.6/site-packages/ansible/cli/__init__.py", line 94, in execute
    fn()
  File "/home/shirokih/.local/lib/python3.6/site-packages/ansible/cli/galaxy.py", line 246, in execute_init
    template_env.get_template(src_template).stream(inject_data).dump(dest_file)
  File "/home/shirokih/.local/lib/python3.6/site-packages/jinja2/environment.py", line 883, in get_template
    return self._load_template(name, self.make_globals(globals))
  File "/home/shirokih/.local/lib/python3.6/site-packages/jinja2/environment.py", line 857, in _load_template
    template = self.loader.load(self, name, globals)
  File "/home/shirokih/.local/lib/python3.6/site-packages/jinja2/loaders.py", line 127, in load
    code = environment.compile(source, name, filename)
  File "/home/shirokih/.local/lib/python3.6/site-packages/jinja2/environment.py", line 638, in compile
    self.handle_exception(source=source_hint)
  File "/home/shirokih/.local/lib/python3.6/site-packages/jinja2/environment.py", line 832, in handle_exception
    reraise(*rewrite_traceback_stack(source=source))
  File "/home/shirokih/.local/lib/python3.6/site-packages/jinja2/_compat.py", line 28, in reraise
    raise value.with_traceback(tb)
  File "/home/shirokih/.local/lib/python3.6/site-packages/ansible/galaxy/data/default/collection/galaxy.yml.j2", line 3, in template
    {{ option.description | comment_ify }}

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:8 (3 by maintainers)

Top GitHub Comments

3reactions

freeseachercommented, Apr 15, 2020

but 3+ version rely on broken dependency and it is a bug.

2reactions

ssbarneacommented, Apr 15, 2020

It should be obvious that comment_ify is not part of molecule but part of galaxy. Unless you can raise a PR to reproduce the error on CI, I will keep this closed as not a bug.

PS. Molecule 2.22 works for you because that version does not rely on galaxy to initialize roles for it.

Top Results From Across the Web

Getting Started Guide — Molecule Documentation

Getting Started Guide . The following guide will step through an example of developing and testing a new Ansible role. After reading...

molecule error: computed fully qualified role name does not ...

I ran into this problem myself and found I needed a namespace: entry in my meta/main.yml. Adding these lines did the trick for...

molecule-hetznercloud - PyPI

A Hetzner Cloud plugin for Molecule. This plugin allows you to do molecule init role myrolename -d hetznercloud and have Molecule provision on-demand...

Molecule - Back 2 Code

molecule init role -r molecule-role # also init a scenario in an existing role $ molecule init scenario -r my-role-name ...

Molecule for existing Ansible roles - - Rackspace

The parameters to init scenario are almost exactly the same as init role and result in the same Molecule directory structure as if...