From ac51f0245ba522bade1409814a0b84b80c8e1d88 Mon Sep 17 00:00:00 2001
From: Colleen Murphy <colleen.murphy@suse.de>
Date: Thu, 3 Jan 2019 15:08:45 +0100
Subject: [PATCH] Revert "Don't log puppot module sync"

This reverts commit 7b47277e3e7fba995b88079dfbb7e9c6af2a5081.

It turns out that for some reason this boring operation does actually go
wrong[1], and if logging doesn't happen then we don't know why.

[1] http://logs.openstack.org/00/616000/6/check/infra-puppet-apply-4-ubuntu-xenial/7379d8c/applytest/puppetapplytest44.final.out.FAILED

Change-Id: I2ce9c3d79385fc0a01b3a5fc85fa4bf4128c25bc
---
 tasks/main.yaml | 2 --
 1 file changed, 2 deletions(-)

diff --git a/tasks/main.yaml b/tasks/main.yaml
index cb00cd6..e2981a4 100644
--- a/tasks/main.yaml
+++ b/tasks/main.yaml
@@ -83,7 +83,6 @@
       synchronize:
         src: "{{ mgmt_manifestpath }}"
         dest: "{{ manifest_base }}"
-      no_log: true
 
     - name: ensure hieradata manifest link is present
       file:
@@ -117,7 +116,6 @@
       synchronize:
         src: "{{ mgmt_puppet_module_dir }}"
         dest: "{{ puppet_module_dir }}"
-      no_log: true
 
   when:
     - copy_puppet