Sync bitbucket and GitHub

ansible-collections · Apr 13, 2022 · 781f020 · 781f020
1 parent 988ea6e
commit 781f020
Show file tree

Hide file tree

Showing 2 changed files with 34 additions and 7 deletions.
diff --git a/CHANGELOG.rst b/CHANGELOG.rst
@@ -5,6 +5,17 @@ NetApp ONTAP Collection Release Notes
 .. contents:: Topics
 
 
+v21.18.1
+========
+
+Bugfixes
+--------
+
+- na_ontap_iscsi - fixed error starting iscsi service on vserver where Service, adapter, or operation already started.
+- na_ontap_lun - Fixed KeyError on options ``force_resize``, ``force_remove`` and ``force_remove_fenced`` in Zapi.
+- na_ontap_lun - Fixed ``force_remove`` option silently ignored in REST.
+- na_ontap_snapshot_policy - Do not validate parameter when state is ``absent`` and fix KeyError on ``comment``.
+
 v21.18.0
 ========
 

diff --git a/changelogs/changelog.yaml b/changelogs/changelog.yaml
@@ -26,13 +26,14 @@ releases:
       - na_ontap_vserver_cifs_security - fix int and boolean options when modifying
         vserver cifs security.
       minor_changes:
-      - "Added REST support to existing modules.\n  By default, the module will use
-        REST if the target system supports it, and the options are supported.  Otherwise,
-        it will switch back to ZAPI.\n  This behavior can be controlled with the ``use_rest``
-        option.\n  Always - to force REST.  The module fails and reports an error
-        if REST cannot be used.\n  Never - to force ZAPI.  This could be useful if
-        you find some incompatibility with REST, or want to confirm the behavior is
-        identical between REST and ZAPI.\n  Auto - the default, as described above.\n"
+      - "Added REST support to existing modules.\n  By default, the module will use\
+        \ REST if the target system supports it, and the options are supported.  Otherwise,\
+        \ it will switch back to ZAPI.\n  This behavior can be controlled with the\
+        \ ``use_rest`` option.\n  Always - to force REST.  The module fails and reports\
+        \ an error if REST cannot be used.\n  Never - to force ZAPI.  This could be\
+        \ useful if you find some incompatibility with REST, or want to confirm the\
+        \ behavior is identical between REST and ZAPI.\n  Auto - the default, as described\
+        \ above.\n"
       - na_ontap_cluster_config - role updated to support a cleaner playbook
       - na_ontap_command - ``vserver`` - to allow command to run as either cluster
         admin or vserver admin.  To run as vserver admin you must use the vserver
@@ -1452,6 +1453,21 @@ releases:
     - DEVOPS-4834.yaml
     - DEVOPS-4864.yaml
     release_date: '2022-04-05'
+  21.18.1:
+    changes:
+      bugfixes:
+      - na_ontap_iscsi - fixed error starting iscsi service on vserver where Service,
+        adapter, or operation already started.
+      - na_ontap_lun - Fixed KeyError on options ``force_resize``, ``force_remove``
+        and ``force_remove_fenced`` in Zapi.
+      - na_ontap_lun - Fixed ``force_remove`` option silently ignored in REST.
+      - na_ontap_snapshot_policy - Do not validate parameter when state is ``absent``
+        and fix KeyError on ``comment``.
+    fragments:
+    - DEVOPS-4872.yaml
+    - DEVOPS-4879.yaml
+    - DEVOPS-4975.yaml
+    release_date: '2022-04-13'
   21.2.0:
     changes:
       bugfixes: