This BZ only deals with the problem in 3.10. Moving it to ON_QA base don that fact. I'll start a backport to 3.9 separately.
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-2018:2697