[SERVER-54772] Tenant migration access blocker get by DB name may return a wrong one Created: 24/Feb/21 Updated: 15/Mar/21 Resolved: 15/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Shuvalov (Inactive) | Assignee: | Andrew Shuvalov (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | pm-1791_non-cloud-blocking, pm-1791_other_required | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Sprint: | Sharding 2021-03-08, Sharding 2021-03-22 |
| Participants: |
| Description |
|
Just looking at the code the method `getTenantMigrationAccessBlockerForDbName()` may return a wrong blocker. Example: if we have unrelated tenants 'joe' and 'joe_doe' requesting a blocker for DB that belongs to tenant 'joe_doe' and has prefix 'joe_doe_' may actually return a first blocker for tenant 'joe' because the literal prefix 'joe_' will match the DB name. |