There are five minor issues with test_secret_stores tests: 1) There is a typo in some test cases. They are calling unset_peferred_secret_store instead of unset_p<r>eferred_secret_store 2) Set and unset preferred secret stores API calls in the SecretStoresClient expect 200 response status code when in fact they should expect 204 instead [1]. 3) test_get_preferred_secret_store test expects to get preferred secret store when in fact none is set for the project. 4) skip_checks() function did not call super's skip_checks() 5) test_set_unset_preferred_secret_store test expects to get preferred secret store for a project when there is no preferred secret store set for it. [1] https://docs.openstack.org/barbican/rocky/api/reference/store_backends.html#post-v1-secret-stores-secret-store-id-preferred
The Fixed in version package contains the desired change. The package is available in the latest phase2 compose. The test_secret_stores tests were executed successfully on a recent 17.1 deployment using the Fixed in version package.
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.1 (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-2023:4577