Description of problem: Resync the downstream image with the latest upstream code. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
@Seb, is BZ 1476835 dup of this bz? if not what is the difference between two?
@Harish, it's not a dump, it's just a new resync. There has been to many commits since the last resync and I cannot open on BZ for each. So it's easier (not ideal I know) this way.
Sébastien, would you please explain to the QE team what exactly is changing in this BZ? "Steps to Reproduce:", "Actual results:", "Expected results:" are blank above. The QE team has no context to provide the qa_ack here or test this BZ to verify that this BZ is resolved. Why should they accept these changes?
@Ken, sorry about that, actual there is nothing in particular to test. We just need to make sure all the scenario work. This is a resync, so it's not a bug but more an update of the image. Thanks.
No specific tests other than basic test scenarios planned for 3.0 will be executed.
Planned tests have passed.
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-2017:3388