Can we get this BZ prioritized for 3.2 release. We have a customer waiting for Bug #1333484 and Bug #1301474?
I can see that Bug #1301474, has already been prioritized for 3.2, It will be good if we can prioritize this bug as well for the same(3.2) release.
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://rhn.redhat.com/errata/RHSA-2017-0486.html