Targeting this initially for z1.
@David, please let us know when will this fix be in 3.0.z1?
Resolved in v12.2.4 upstream.
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/RHBA-2018:1259