Details
-
Bug
-
Status: Awaiting deployment (View Workflow)
-
TBD
-
Resolution: Done
-
None
-
None
-
Volaris Sprint 151, Volaris Sprint 153, Volaris Sprint 154
-
0.5
-
Volaris
-
Morning Glory (R2 2022)
-
Architecture issue
Description
Overview:
in multiple tenants environment , where mod-inn-reach is enabled for only 1 tenant , the module is trying to create token for all the other tenants in the environment, even if the module is not enabled for them . as a result , we get an error log of No user found by username ***** ( system user username ) , which is expected result since the tenant which has no inn-reach enabled, does not have a system user for this module .
Steps to Reproduce:
- Log into some multiple tenant environment where mod-innreach is not enabled for all the tenants in the environment
- check module logs, you will find error logs of the module trying to create token for these non inn-reach tenants
Expected Results:
mod-inn-reach should interact only with the tenants which is enabled for themĀ
Actual Results:
mod-inn-reach is trying to create token for all the tenants in the environment
PS : in the attachment, mod-inn-reach is not enabled for tenant id XXXXX
logs-mod-inn-reach.txt
TestRail: Results
Attachments
Issue Links
- relates to
-
MODINREACH-341 Mod-inn-Reach BE MG Hot fix Release
-
- Closed
-