RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2172107 - 'ipa idview-show idviewname' & IPA WebUI takes longer time to return the results in RHEL 8.5
Summary: 'ipa idview-show idviewname' & IPA WebUI takes longer time to return the resu...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Florence Blanc-Renaud
QA Contact: Sudhir Menon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-21 14:15 UTC by Corey Brown
Modified: 2023-12-01 11:45 UTC (History)
10 users (show)

Fixed In Version: ipa-4.9.12-2.module+el8.9.0+18921+013c0de2
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-14 15:32:50 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Pagure freeipa issue 9372 0 None None None 2023-05-02 18:24:09 UTC
Red Hat Issue Tracker FREEIPA-9487 0 None None None 2023-02-21 14:15:51 UTC
Red Hat Issue Tracker RHELPLAN-149536 0 None None None 2023-02-21 14:15:55 UTC
Red Hat Product Errata RHBA-2023:6977 0 None None None 2023-11-14 15:33:36 UTC

Description Corey Brown 2023-02-21 14:15:01 UTC 
Description of problem:
'ipa idview-show idviewname' & IPA WebUI takes longer time to return the results

Version-Release number of selected component (if applicable):
ipa-4.6.8-5.el7_9.12

Always

Steps to Reproduce:
1. Install IPA server, set up IPA-AD trust. 
2. Create IDView  (idview) in IPA with larger number of idoverrides.
3. Run '# time ipa idview-show idviewname' command and see how long it takes.

Actual results:
'ipa idview-show idviewname' & IPA WebUI taking long time to show results, it almost take 1-2.5 minutes which is not acceptable and makes the tool unusable.

Expected results:
'ipa idview-show idviewname' & IPA WebUI should show the results quicker. 

Additional info:
Several things including some sssd tweaks have been tried but it didn't make significant difference yet.
Comment 2 Rob Crittenden 2023-02-21 14:21:22 UTC 
What things, including sssd tweaks, have been tried? What troubleshooting has already been done?
Comment 4 kechoi 2023-03-21 15:36:00 UTC 
Here is the id-view load time and package versions.
 
[root@idma2 ~]# time ipa idview-show Legacy
  ID View Name: Legacy
…
 
real    6m17.204s
user    0m0.495s
sys     0m0.066s
 
[root@idma2 ~]# rpm -qa | grep ipa
python3-ipalib-4.9.10-9.module+el8.7.0+17437+cf46f77f.noarch
redhat-logos-ipa-84.5-1.el8.noarch
ipa-healthcheck-0.7-14.module+el8.7.0+15352+88b578e5.noarch
ipa-server-trust-ad-4.9.10-9.module+el8.7.0+17437+cf46f77f.x86_64
python3-iniparse-0.4-31.el8.noarch
ipa-client-common-4.9.10-9.module+el8.7.0+17437+cf46f77f.noarch
python3-libipa_hbac-2.7.3-4.el8_7.3.x86_64
ipa-server-dns-4.9.10-9.module+el8.7.0+17437+cf46f77f.noarch
ipa-healthcheck-core-0.7-14.module+el8.7.0+15352+88b578e5.noarch
ipa-server-common-4.9.10-9.module+el8.7.0+17437+cf46f77f.noarch
sssd-ipa-2.7.3-4.el8_7.3.x86_64
python3-ipaserver-4.9.10-9.module+el8.7.0+17437+cf46f77f.noarch
libipa_hbac-2.7.3-4.el8_7.3.x86_64
ipa-server-4.9.10-9.module+el8.7.0+17437+cf46f77f.x86_64
ipa-selinux-4.9.10-9.module+el8.7.0+17437+cf46f77f.noarch
python3-ipaclient-4.9.10-9.module+el8.7.0+17437+cf46f77f.noarch
ipa-common-4.9.10-9.module+el8.7.0+17437+cf46f77f.noarch
ipa-client-4.9.10-9.module+el8.7.0+17437+cf46f77f.x86_64
 
[root@idma2 ~]# rpm -qa | grep sssd
sssd-idp-2.7.3-4.el8_7.3.x86_64
python3-sssdconfig-2.7.3-4.el8_7.3.noarch
sssd-kcm-2.7.3-4.el8_7.3.x86_64
sssd-client-2.7.3-4.el8_7.3.x86_64
sssd-common-2.7.3-4.el8_7.3.x86_64
sssd-tools-2.7.3-4.el8_7.3.x86_64
sssd-ipa-2.7.3-4.el8_7.3.x86_64
sssd-winbind-idmap-2.7.3-4.el8_7.3.x86_64
sssd-dbus-2.7.3-4.el8_7.3.x86_64
sssd-common-pac-2.7.3-4.el8_7.3.x86_64
sssd-nfs-idmap-2.7.3-4.el8_7.3.x86_64
sssd-krb5-common-2.7.3-4.el8_7.3.x86_64
Comment 6 Florence Blanc-Renaud 2023-05-02 18:24:08 UTC 
Upstream ticket:
https://pagure.io/freeipa/issue/9372
Comment 7 Rob Crittenden 2023-05-05 18:18:32 UTC 
Fixed upstream
master:
https://pagure.io/freeipa/c/c8c05289f8078257a85f24cca907a094dd793c05
Comment 8 Rob Crittenden 2023-05-08 17:57:05 UTC 
Fixed upstream
ipa-4-10:
https://pagure.io/freeipa/c/3a9a5bdae7cb3dee65ba74b00169badb72fe6dda

ipa-4-9:
https://pagure.io/freeipa/c/ec7d770a256d458d9556a6adbc85b4b7fe2523ef
Comment 16 errata-xmlrpc 2023-11-14 15:32:50 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (idm:client and idm:DL1 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:6977
Note You need to log in before you can comment on or make changes to this bug.