Hi Jake,
Thanks for your answer, you got it! I didn't pay attention to the traceback and overlooked that the error was happing in Barbican client... The error was a Barbican httpd misconfiguration after the upgrade (a Python path not updated for the new Python version, 3.9). httpd log file was explict about it.
Cheers,
Michel
Le 01/05/2024 à 02:28, Jake Yip a écrit :
On 1/5/2024 2:47 am, Michel Jouvin wrote:
I had a new look at the problem and found nothing to help as far as I can say... The keystone client error mentions a 403 status but I cannot find any trace of a matching request on the keystone server. All the requests from the Magnum/Heat server are completing with a 200 status according to the keystone (httpd) server logs...
Are there any errors in Barbican? The trace shows barbicanclient.
- Jake