From 627c644166e1c6df1be4a0c203860035d6e18472 Mon Sep 17 00:00:00 2001
From: Rafael Guterres Jeffman <rjeffman@redhat.com>
Date: Fri, 3 Jul 2020 16:39:47 -0300
Subject: [PATCH] Added information about Ansible 2.10.0a1 bug on Azure.

Added comment about problem with no_log in Azure CI. While running on CI
using ansible 2.10a the content of attributes with no_log=True is
replaced by ***** on ansible causing test failures.
---
 tests/azure/azure-pipelines.yml | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/tests/azure/azure-pipelines.yml b/tests/azure/azure-pipelines.yml
index 5373de43..9a632105 100644
--- a/tests/azure/azure-pipelines.yml
+++ b/tests/azure/azure-pipelines.yml
@@ -1,3 +1,16 @@
+# Using Ansible 2.10.0a1 under Azure there might happen that the output of a
+# task is changed if a module uses no_log = True for an attribute.
+#
+# For example, if the output of the module should contain "changed: True", and
+# an attribute with no_log set contains the value `hang` it might happen that
+# the output is modified to "c******ed: True", and if this output is further
+# processed (registering the result and comparing the value of `changed`),
+# the test might fail, but not because of module code, but because of unexpected
+# output processing.
+#
+# This behavior was, currently, only reproduced with Ansible 2.10.0a1 running
+# under Azure.
+---
 trigger:
 - master
 
-- 
GitLab