Alex - yes, his patch should be in the composes starting on 6/28 and since, the FixedInVersion should have been set at that time and the bug moved to MODIFIED and eventually ON_QA. it looks like somewhere along the BZ states weren't set, but the patch should still be there as ReleaseDelivery would have imported it from stable/stein. Can you just confirm that fixes are https://review.opendev.org/#/c/667295/ are in a OSP-15 compose that you have? We can then set the bug state and FIV.
(In reply to Bob Fournier from comment #10) > Alex - yes, his patch should be in the composes starting on 6/28 and since, > the FixedInVersion should have been set at that time and the bug moved to > MODIFIED and eventually ON_QA. it looks like somewhere along the BZ states > weren't set, but the patch should still be there as ReleaseDelivery would > have imported it from stable/stein. > > Can you just confirm that fixes are https://review.opendev.org/#/c/667295/ > are in a OSP-15 compose that you have? We can then set the bug state and > FIV. Bob, I can confirm as well that changes are in the compose, so I think we should update this BZ to reflect that.
Updating FIV and state to reflect that this fix is available.
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/RHEA-2019:2811