mso_schema_site_anp_epg_domain module issue?

[Albert Short]

Hello all,

I have tried using the mso_schema_site_anp_epg_domain module today with the code syntax below but keep getting the following error message.

Any ideas on what the issues? Or has someone else seen this before?

# ansible-playbook test_mso.yml -vvv

ansible-playbook 2.8.6

  config file = /******/ansible.cfg

  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']

  ansible python module location = /usr/local/lib/python3.6/site-packages/ansible

  executable location = /usr/local/bin/ansible-playbook

  python version = 3.6.8 (default, Aug  7 2019, 17:28:10) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]

Using /******/ansible.cfg as config file

host_list declined parsing /******/hosts as it did not pass it's verify_file() method

script declined parsing /******/hosts as it did not pass it's verify_file() method

auto declined parsing /******/hosts as it did not pass it's verify_file() method

Parsed /******/hosts inventory source with ini plugin

ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.

The error appears to be in '/******/test_mso.yml': line 146, column 7, but may

be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

    - name: Add a new VMM Domain Association to a Schema Site EPG

      ^ here

---

- name: Test Play

  hosts: busmsc

  tasks:

    - name: Add a new VMM Domain Association to a Schema Site EPG

      mso_schema_site_anp_epg_domain:

        host: "{{ ansible_host }}"

        username: "{{ ansible_user1 }}"

        password: "{{ ansible_password1 }}"

        validate_certs: no

        ########################################################################

        schema: sch-user-app

        site: SC0 - BUS

        template: tmpl-user-scx-app

        anp: ap-scx-app

        epg: epg-scx-v12-icmp_server

        domain_association_type: vmmDomain

        domain_profile: pafw_vds

        deployment_immediacy: lazy

        resolution_immediacy: pre-provision

        state: present

      # delegate_to: localhost

    - name: Deploy a schema template

      mso_schema_template_deploy:

        host: "{{ ansible_host }}"

        username: "{{ ansible_user1 }}"

        password: "{{ ansible_password1 }}"

        validate_certs: no

        ########################################################################

        schema: sch-user-{{app_name}}

        template: tmpl-user-{{site}}-{{app_name}}

        state: deploy

      # delegate_to: localhost

    - name: Deploy a schema Site template

      mso_schema_template_deploy:

        host: "{{ ansible_host }}"

        username: "{{ ansible_user1 }}"

        password: "{{ ansible_password1 }}"

        validate_certs: no

        ########################################################################

        schema: sch-v00-aci-network

        template: tmpl-v00-aci-scx

        state: deploy

[Thomas Renzy]

Hi Albert,

Is this the full playbook?

Is the error that was being reported the first task on the playbook you copied?

Thanks,

Thomas

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/809cf9e4-433d-4be8-9811-24e395f2237f%40googlegroups.com.

[Albert Short]

Thomas, yes this is the whole playbook. I have watered it down & tested it as is in the playbooked copied to try & use a process of elimination.

The deploy tasks work, as they are part of the bigger play, which deploys successfully as I have been building.

I therefore assume it is related to the first task. I have even tested it without the deploy module, but get the same result.

Regards

Albert Short

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CA%2B8veMFWx%3DTWSKbgfF3eUtn0GZzu33bByNh-1xihX32mC8sq8w%40mail.gmail.com.

[Ompragash]

Hi Albert,

The module which you're trying to use was added in Ansible v2.9 and you current Ansible version is V2.8 which is why it's failing. So you can try upgrading Ansible to the latest version and re-run the playbook.

Regards,

Ompragash

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAKCbL1pMRGta6Jr7USyB8SRhNEQp_mYozUsxWW2GzqweWkd2hg%40mail.gmail.com.

[Albert Short]

FFS, ~@**%%

should have checked that. you go a bit script blind from looking at it too long.

Thanks

Regards

Albert Short

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAEFccTXxR4CevsUHmvxtrnSYBMFihgn8Aa_nia99ej_NR9p4QA%40mail.gmail.com.