The problem with saying that the test still fails in some job is that the test failure is really generic (what it indicates is that data path is broken at some point, but it can be millions of reasons, from ovs bridges to l3 router issues to issues on tempest node). With that, I don't think we can meaningfully track them all with a single bug. The bug I was pursuing before was fixed. Whatever will come up with new failure reports is probably some different bug.
I guess we could change this bug report title to reflect the actual root cause, in which case it will match the fact that this bug is not overarching for all possible failures of the test class, today or in the future.
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.