Setting to Post and assigning to @jnovy . The fix from the cloned BZ in RHEL 8.7.0.ZeroDay will apply here too.
@ypu and Jindrich, can I get a QA and Dev ack please?
Test with netavark-1.1.0-7.el9_1.x86_64 and aardvark-dns-1.1.0-5.el9_1.x86_64, stress the host with stress command, start 30 container service in the same time several times. The container can up as expected and no error found. And as the fix is already verified by customer in their hardware. Also double confirm that the fix pullreqs are included in the source code. So move this to verified.
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 (netavark bug fix and enhancement update), 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/RHBA-2022:8435