This issue is not reproducible on 3.12.2-13.el7rhgs.x86_64 RHGS systems.
Also, have done sanity check around the fix and scenario. Hence, marking this BZ as Verified sanity only.
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.