We are still not able to reproduce the issue, so retargeting to 4.1.7 for now, but we are continuing investigations and we can release as 4.1.6 async if ready soon
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2017:3138