503 errors when tenants are specified

[exalate-issue-sync]

Describe the bug :

When a tenant is specified, the calls are finishing with 503

To Reproduce :

Steps to reproduce the behavior:

1. Create a simple echo api
2. Define tenant in the gw's gravitee.yml Attachment - image.png
3. and first is the tenant checked at the api we are calling
4. then getting the 503 in postman Attachment - image.png
5. Did an additional test, created another tenant, checked that one, 503 again
6. When none of the tenants is selected/checked, the call in postman is 200 Attachment - image.png

Tested in 3.20.11