ansible-collections / netapp

Development area for Netapp collections
49 stars 36 forks source link

na_ontap_aggregate doesn't add disks to a MCCIP aggregate #67

Closed flohzirkus666 closed 3 years ago

flohzirkus666 commented 3 years ago
SUMMARY

When trying to add disks to an existing aggregate on a MCCIP system, Ansible doesn't add any disks to the existing aggregate.

ISSUE TYPE
COMPONENT NAME

na_ontap_aggregate

ANSIBLE VERSION
ansible 2.9.13
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /opt/awx/python-envs/netapp-env/lib64/python3.6/site-packages/ansible
  executable location = /opt/awx/python-envs/netapp-env/bin/ansible
  python version = 3.6.8 (default, Sep 26 2019, 11:57:09) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]```

##### CONFIGURATION
<!--- Paste verbatim output from "ansible-config dump --only-changed" between quotes -->
```paste below
OS / ENVIRONMENT

LSB Version: :core-4.1-amd64:core-4.1-noarch Distributor ID: RedHatEnterpriseServer Description: Red Hat Enterprise Linux Server release 7.8 (Maipo) Release: 7.8 Codename: Maipo

STEPS TO REPRODUCE

We're passing for example a total amount of 20 disks to a pre-existing aggregate that already contains 10 disks. According to the documentation Ansible should add 10 disks to reach a total of 20.

- name: create or add disks to aggregate
      tags: xy
      delegate_to: localhost
      na_ontap_aggregate:
        <<: *login
        state: present
        service_state: online
        name: "{{ item.aggr_data_name }}"
        nodes: "{{ item.node_name }}"
        disk_count: "{{ item.disk_count }}"
        raid_size: "{{ item.max_raidsize }}"
        wait_for_online: true
        time_out: 300
      loop: "{{ aggregates }} "
EXPECTED RESULTS

Aggregate grows from 10 to 20 disks.

ACTUAL RESULTS

Ansible changes nothing.

carchi8py commented 3 years ago

@flohzirkus666 are you using the collection version of ansible 2.9 version of the modules?

If you are using the 2.9 version can you try using ansible 2.10 or use the collection version. We have about a year's worth of bug fixes listed on the page below that might fix the issue your seeing. https://github.com/ansible-collections/netapp/blob/master/ansible_collections/netapp/ontap/README.md

flohzirkus666 commented 3 years ago

Hi @carchi8py,

We're using the latest version of your collection. However we found out, that the error was occuring because the Ops had renamed the collection folder that caused the issue.