Ryan, could you provide the git rebase command you used for this bug, without the command, I don't know how to 100% verify this bug to make sure we get all upstream fixes into downstream.

The command was "git checkout ovirt-4.0 && git rebase master"

I don't actually know that there's a good way to verify this from a QE perspective, unfortunately.

(In reply to Ryan Barry from comment #2)
> The command was "git checkout ovirt-4.0 && git rebase master"
> 
> I don't actually know that there's a good way to verify this from a QE
> perspective, unfortunately.

Yes, to verify this bug, here need to provide which commit we need to rebase or detail bugs list. OR strict check all commits one by one.

So I would like to let devel do bug verification to make sure all expected commits are rebased correct.

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/RHBA-2016-1688.html