Horizon cannot display >1.5K users from LDAP
Bug #1494806 reported by
Paul Karikh
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
In Progress
|
High
|
Nikita Konovalov | ||
7.0.x |
Won't Fix
|
Medium
|
MOS Maintenance | ||
8.0.x |
Won't Fix
|
High
|
Unassigned | ||
9.x |
Won't Fix
|
High
|
Unassigned |
Bug Description
If Keystone is set up with LDAP and there is a lot of users (look like 1500 users if an the threshold value), Horizon can't fetch all users from domain and shows error "Error: Unable to retrieve user list."
There is no issues if number of users in LDAP is much smaller.
Also fetching 1K users from LDAP takes too long time (in comparsion with MySQL).
Affected pages:
identity/users
identity/domains (cannot list domain members)
Upstream bug is here: https:/
tags: | added: horizon |
Changed in mos: | |
assignee: | nobody → Paul Karikh (pkarikh) |
summary: |
- Horizon cannot fetch lots users when deployed with LDAP + Horizon cannot fetch >1.5K users when is deployed with LDAP |
summary: |
- Horizon cannot fetch >1.5K users when is deployed with LDAP + Horizon cannot fetch >1.5K users when it is deployed with LDAP |
summary: |
- Horizon cannot fetch >1.5K users when it is deployed with LDAP + Horizon cannot display >1.5K users from LDAP |
description: | updated |
Changed in mos: | |
milestone: | none → 8.0 |
importance: | Undecided → High |
status: | New → Confirmed |
description: | updated |
description: | updated |
tags: | added: enhancement |
tags: | added: customer-found |
Changed in mos: | |
status: | Confirmed → In Progress |
Changed in mos: | |
milestone: | 8.0 → 9.0 |
tags: | added: release-notes |
tags: |
added: 8.0 release-notes-done removed: release-notes |
tags: | added: wontfix-feature |
Changed in mos: | |
milestone: | 9.0 → 10.0 |
Changed in mos: | |
assignee: | Boris Bobrov (bbobrov) → nobody |
Changed in mos: | |
assignee: | nobody → Nikita Konovalov (nkonovalov) |
no longer affects: | mos/10.0.x |
To post a comment you must log in.
Here is Keystone patch which should help us to fix (or workaround, at least) this problem: https:/ /review. openstack. org/#/c/ 234849/