Thanks Milan, After some investigation, I found the issue, and what I think we should do is open a separate ticket to deal with what you found, since this one is a pretty high priority thing that needs to get in to the build. Erik.
Ok then I am moving this into VERIFIED and opening a new ticket
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-2016:0159