Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2240903

Summary:	UI - Creating OU in ldap browser ends in error
Product:	Red Hat Directory Server	Reporter:	bsmejkal
Component:	cockpit-389-ds	Assignee:	LDAP Maintainers <idm-ds-dev-bugs>
Status:	CLOSED MIGRATED	QA Contact:	LDAP QA Team <idm-ds-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	12.3	CC:	idm-ds-dev-bugs, tbordaz, vashirov
Target Milestone:	DS12.5	Keywords:	Triaged
Target Release:	dirsrv-12.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sync-to-jira
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-26 13:50:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description bsmejkal 2023-09-27 07:59:49 UTC

Description of problem:
When creating new OU in LDAP browser, the entry is created but page needs to be reloaded as it ends in error.

Version-Release number of selected component (if applicable):
389-ds-base-2.3.6-4.module+el9dsrv+19950+6ff0d0d4.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Run automated test dirsrvtests/tests/suites/webui/ldap_browser/ldap_browser_test.py::test_create_and_delete_organizational_unit

Manual
2. Go to Ldap Browser Tab, select the suffix, click three dots and select New
3. Select Create a new Organizational Unit
4. Fill the name and finish all the steps

Actual results:
The page ends in Oopps and page needs to be refreshed as the buttons get stuck.
However the entry is created at least.

Expected results:


Additional info:
Test failure can also be observed in upstream main branch.

Comment 2 Viktor Ashirov 2024-06-26 13:50:05 UTC

This BZ has been automatically migrated to Red Hat Issue Tracker https://issues.redhat.com/browse/DIRSRV-54. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.