https://bugzilla.redhat.com/show_bug.cgi?id=1882750 fixes this for 4.7 https://bugzilla.redhat.com/show_bug.cgi?id=1919069 fix 4.6.z Then there is another one related to this: https://bugzilla.redhat.com/show_bug.cgi?id=1927500 It sounds like the fixes did not address all possible ways this could happen. Is that the reason why the bug was created? If so, let's make this targeted to 4.8 and propagate any new fixes backwards.
Yes, I filed this (as build watcher) on 4.8 because it was happening on the 4.8 lanes too and there was no bug tracking it.
There is a bug for this here: 1929674 that is tracking the PR... Going to duplicate this BZ to 1929674. *** This bug has been marked as a duplicate of bug 1929674 ***