Description of problem: ======================= The fix[1] for bug 1569129 (which we backported to OSP13 as a downstream-only backport) introduced a capability to Octavia in which it will automatically revoke access to secrets that are no longer used by any Octavia listener. An upstream StoryBoard[2] reported the following: ================================================= If a barbican secret is used by multiple listeners, one as the default container ID and one as an SNI container reference, when either one of those listeners are deleted the "unset_acls" call we be made on the container reference. This can lead to Octavia losing valid access to the container. Also, the code as it is written is not thread safe. At the time of reporting this bug, a fix[3] was already merged into upstream master (Stein) and proposed[4] to stable/rocky. We will need to downstream-backport this to OSP13 since the original patch[1], as mentioned above, was a downstream-only backport as well. Version-Release number of selected component (if applicable): ============================================================= OSP13 [1] https://review.openstack.org/#/c/552549/13/releasenotes/notes/add-ability-setting-barbican-acls-85f36747d4284035.yaml@6 [2] https://storyboard.openstack.org/#!/story/2005041 [3] https://review.openstack.org/#/c/637646/ [4] https://review.openstack.org/#/c/639020/
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/RHBA-2019:1744