This was reported upstream in 2016.
Shall we change the OSP version of this BZ to 13? Are you currently working on the backport as a customer is worried about the status of this bug report.
(In reply to Andreas Karis from comment #23) > Shall we change the OSP version of this BZ to 13? Are you currently working > on the backport as a customer is worried about the status of this bug report. I've moved this to 17.0 to target the functional regression test and actual fix landing in master once the V cycle opens up. This isn't a simple rebase however and could take some additional time to land. Once it has landed I'll then clone this bug back to 13 and attempt to backport.
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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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-2022:6543