#na_ontap_volume_clone module error

1 messages · Page 1 of 1 (latest)

wicked mason
#

I've been fighting with this most of the day. I have a working playbook with some roles to take a snapshot, clone a volume, and then set the export policy. It all runs great locally on my workstation.

Our Ansible AWX environment is giving module errors though. I found that there was an issue with KeyError: volume fixed in collection 20.1.0, but I verified that my environment is pulling in the latest collection when it builds out to run.

I'm fairly new to AWX usage, so its also possible I missed something there. Below is my role giving me the issue, as well as the Traceback I'm getting.

Most of these variables are coming from a survey or are hard set for now. parent_volumes is a textarea with one volume per line. I've done some debugging and verified it looks like vol1\nvol2\nvol3\nvol4 and splits properly.

- name: create volume clone
  na_ontap_volume_clone:
    state: present
    vserver: "{{ dest_vserver }}"
    parent_vserver: "{{ parent_vserver }}"
    parent_volume: "{{ item }}"
    parent_snapshot: "{{ snapshot_name }}"
    name: "{{ item }}_clone"
    hostname: "{{ netapp_hostname }}"
    username: "{{ netapp_username }}"
    password: "{{ netapp_password }}"
    https: "{{ https }}"
    validate_certs: "{{ validate_certs }}"
  loop:
    "{{ parent_volumes.split('\n') | string }}"

traceback is in a reply

hard shoal
#

AWX Execution Environments and target host can be challenge to troubleshoot. Are your sure the Ansible and Python Version match your local environment?

wicked mason
#

That's my suspicion too. The KeyError: volume matched up with a bug fixed in netapp.ontap collection 20.1.0.