true night
I am running following tasks to create volume
- name: Volume Create "{{ vol_type }}"
na_ontap_volume:
state: present
name: "{{ vol_name_inner }}"
vserver: "{{ vserver_inner }}"
aggregate_name: "{{ selected_aggr }}"
type: "{{ vol_type }}"
size: "{{ size_inner }}"
percent_snapshot_space: "{{ snap_reserve_inner | int }}"
size_unit: mb
size_change_threshold: 0
policy: default
#encrypt: "{{ is_encrypted_inner| default('false',true)|bool }}"
encrypt: yes
snapshot_policy: "{{ snapshot_policy_inner }}"
space_guarantee: none
#junction_path: "/{{ vol_name_inner }}"
volume_security_style: ntfs
comment: "{{ vol_comment_inner }}"
wait_for_completion: True
hostname: "{{ filer_mgmt_addr_inner }}"
username: "{{ storage_user }}"
password: "{{ storage_password }}"
https: true
validate_certs: false
on one filer I got a very strange error:
"An exception occurred during task execution. To see the full traceback, use -vvv. The error was: netapp_lib.api.zapi.zapi.NaApiError: NetApp API failed. Reason - 13001:The Onboard Key Manager is already configured. To sync any nodes with the Onboard Key Manager configuration, run the "security key-manager onboard sync" command. Provide the cluster-wide passphrase initially configured for the cluster"
it seems that this is related to the encryption setting.
I am worried that na_ontap_volume might be trying to enable system wide setting if for some reason filer is not ready for volume encryption
viral scarab