You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Very basic playbook, calling na_ontap_info with no gather_subsets fails on job schedules with ontap 9.1.
Documentation for this module says supported for ontap 9.1 onwards.
Using gather_subset to exclude job_schedule_cron_info does work, so the issue is minor and isolated.
I totally understand that this is not likely worth the effort to fix due to 9.1 being way out of support - perhaps just document it.
This problem is likely caused by cron jobs moving from outside into a cluster vserver. Example cli outputs to highlight this:
Ontap 9.1
cluster91::> cron show
(job schedule cron show)
Name Description
---------------- -----------------------------------------------------
4hour @0:13,4:13,8:13,12:13,16:13,20:13
5min @:00,:05,:10,:15,:20,:25,:30,:35,:40,:45,:50,:55
8hour @2:15,10:15,18:15
daily @0:10
hourly @:05
weekly Sun@0:15
6 entries were displayed.
Ontap 9.7 (has the cluster column in the table)
cluster97::> cron show
(job schedule cron show)
Cluster Name Description
------------- ----------- -----------------------------------------------------
cluster97
5min @:00,:05,:10,:15,:20,:25,:30,:35,:40,:45,:50,:55
8hour @2:15,10:15,18:15
daily @0:10
hourly @:05
monthly 1@0:20
<snip as cluster has way more schedules by default>
Component Name
na_ontap_info
Ansible Version
$ ansible --version[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version: 3.6.8 (default, Aug 13 2020, 07:46:32) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]. This feature will be removed from ansible-core in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.ansible [core 2.11.9] config file = /home/myuseraccount/netapp-test/ansible.cfg configured module search path = ['/home/myuseraccount/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /home/myuseraccount/venvs/vmware-netapp/lib64/python3.6/site-packages/ansible ansible collection location = /home/myuseraccount/.ansible/collections:/usr/share/ansible/collections executable location = /home/myuseraccount/venvs/vmware-netapp/bin/ansible python version = 3.6.8 (default, Aug 13 2020, 07:46:32) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] jinja version = 3.0.3 libyaml = True
I'll need to talk with the rest of the team, but I'm not sure we'll have a fix for this. It look like key 'job-schedule-cluster' was added to the zapi job-schedule-cron-get-iter sometime after 9.1
Thank you that's great.
For my purposes I'm just excluding it with gather_subset "!job_schedule_cron_info" until I can upgrade all my remaining 9.1 systems (apart from any FAS2240 stuck on 9.1 of course).
Summary
Very basic playbook, calling na_ontap_info with no gather_subsets fails on job schedules with ontap 9.1.
Documentation for this module says supported for ontap 9.1 onwards.
Using gather_subset to exclude job_schedule_cron_info does work, so the issue is minor and isolated.
I totally understand that this is not likely worth the effort to fix due to 9.1 being way out of support - perhaps just document it.
This problem is likely caused by cron jobs moving from outside into a cluster vserver. Example cli outputs to highlight this:
Ontap 9.1
Ontap 9.7 (has the cluster column in the table)
Component Name
na_ontap_info
Ansible Version
ONTAP Collection Version
ONTAP Version
Playbook
Steps to Reproduce
Playbook has hardcoded host/username/password as it's very basic.
Expected Results
The module should run without exception and register the results in the named variable.
Excluding a subset shouldn't be required to work.
Running against a cluster running 9.5 or 9.7 works without issue. I don't have a 9.3 cluster to test with to see if that works.
Actual Results
The text was updated successfully, but these errors were encountered: