How to specify tag with molecule test

[krimitalel]

Hello,

is there a way to specify tag when executing molecule test ( ex molecule test -- --tags foo,bar ) ?

apparently, it works only with molecule converge ( molecule converge -- tags foo,bar )

[lanceofwhichwedream]

I'd like to see this added as well

[liuyangc3]

I guess only molecule converge and idempotence needs the tags. but idempotence does not support ansible tags args yet.

[marcelbrueckner]

Had the same issue and solved it by creating a separate scenario for which I define default tags. This is done by adding ansible.cfg modifications or Ansible environment variables to the provisioner configuration* in molecule.yml.

* links to Molecule v2 documentation, but is perfectly valid for current Molecule v3 (which's documentation is crap) as well

provisioner:
  name: ansible
  # Either via config option
  config_options:
    tags:
      run: tag1,tag2,tag3
  # or env
  env:
    ANSIBLE_RUN_TAGS: tag1,tag2,tag3

Assuming your scenario is called use-tags and the respective converge.yml looks like this:

---
- name: Converge
  hosts: all

  tasks:
    - debug:
        msg: This message appears because of either tag1, tag2 or tag3
      tags:
        - tag1
        - tag2
        - tag3
    - debug:
        msg: This message should not appear
      tags:
        - tag-not-defined-in-default-tag-list
    - debug:
        var: ansible_run_tags
      tags:
        - always

Then molecule converge -s use-tags will result in:

PLAY [Converge] ****************************************************************

TASK [Gathering Facts] *********************************************************
ok: [instance]

TASK [debug] *******************************************************************
ok: [instance] => {
    "msg": "This message appears because of either tag1, tag2 or tag3"
}

TASK [debug] *******************************************************************
ok: [instance] => {
    "ansible_run_tags": [
        "tag1",
        "tag3",
        "tag2"
    ]
}

PLAY RECAP *********************************************************************
instance          : ok=3    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

[sparsick]

I tried your answer. Unfortunately, I get always

INFO     Running tag1 > converge

PLAY [Converge] ****************************************************************

TASK [Gathering Facts] *********************************************************
fatal: [instance]: UNREACHABLE! => {"changed": false, "msg": "Failed to create temporary directory. In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo ~/.ansible/tmp `\"&& mkdir \"` echo ~/.ansible/tmp/ansible-tmp-1676533208.7835898-20945-71609450033956 `\" && echo ansible-tmp-1676533208.7835898-20945-71609450033956=\"` echo ~/.ansible/tmp/ansible-tmp-1676533208.7835898-20945-71609450033956 `\" ), exited with result 1", "unreachable": true}

The scenario without tags run as expected.

I created a repository with the whole example: https://github.com/sparsick/ansible-molecule-tags

[omula]

Tags are also applied to create which makes molecule-podman not work.
In order to make it work I created a copy of create.yml in my collection and modified all tasks to have the tag always.

[markfaine]

This works but not with molecule verify when using Ansible as the verifier.

[zhan9san]

Hi

This issue would be addressed in ansible-community/molecule-plugins#120 and #3866.