Description of problem: There are several comboboxes (not all) in the RHDS 11.1 Cockpit console on RHEL 8.2 beta, that cause to crash Cockpit if you click in to the fields. Version-Release number of selected component (if applicable): cockpit-389-ds-1.4.2.7-1.module+el8dsrv+5547+8be68086.noarch Steps to Reproduce: 1. Log in to Cockpit. 2. Open the Plugins menu. 3. Select "Attribute Uniqueness". 4. Click "Add Config". 5. Click into the "Attribute Names" field. Actual results: Cockpit crashes. Expected results: The combobox should open and show the list of entries. Additional info: The problem does not seem to exist with all comboboxes of this style. However, it is also 100% reproduceable here: - Plugins / MemberOf , if you click in to the "Group Attribute" field - Plugins / Auto Membership / Add definition, if you click in to "Grouping Attributes" field.
In the console log (press F12) are you seeing typeAhead errors? If so, we already have a fix for this that will be coming out soon. If the crash is not caused by typaAhead then please share the console log errors.
Created attachment 1658228 [details] Screenshot Console I attached a screenshot of the console. The two errors were logged when I clicked into the "Attribute Names" field (Attribute Uniqueness plug-in).
I don't know if this is related, but I found another situation where Cockpit crashes (requires a replication setup): 1. Open the "Monitoring" tab. 2. Select "Replication" entry. 3. On the "Agreements" tab, open the "Actions" menu. 4. Click "View Agreement Details"
(In reply to Marc Muehlfeld from comment #3) > I don't know if this is related, but I found another situation where Cockpit > crashes (requires a replication setup): > > 1. Open the "Monitoring" tab. > 2. Select "Replication" entry. > 3. On the "Agreements" tab, open the "Actions" menu. > 4. Click "View Agreement Details" This works fine for me, what is your setup exactly?
(In reply to mreynolds from comment #4) > (In reply to Marc Muehlfeld from comment #3) > > I don't know if this is related, but I found another situation where Cockpit > > crashes (requires a replication setup): > > > > 1. Open the "Monitoring" tab. > > 2. Select "Replication" entry. > > 3. On the "Agreements" tab, open the "Actions" menu. > > 4. Click "View Agreement Details" > > This works fine for me, what is your setup exactly? I set up a single-master replication environment on RHEL 8.2 beta by following this procedure: http://ccs-jenkins.gsslab.brq.redhat.com:8080/job/doc-Red_Hat_Directory_Server-Administration_Guide-branch-mmuehlfe_RHELPLAN-29954/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#setting_up_single-master_replication_using_the_web_console The only differences: - Both instances run on the same host - The consumer instance uses port 1389 and 1636 Replication works. Status is: "Error (0) Replica acquired successfully: Incremental update succeeded" However, if I try to display the replication agreement details, Cockpit crashes. If you want, you can access my VM via SSH/Cockpit. Ping me on IRC.
Build tested: cockpit-389-ds-1.4.2.12-1.module+el8dsrv+6328+f04d7471.noarch If there is no suffix created, and I try to add attribute uniqueness plugin, clicking on an empty element in Subtree DN causes cockpit to crash. Marking as ASSIGNED.
Created attachment 1680266 [details] attribute uniqueness dialog
Upstream ticket: https://pagure.io/389-ds-base/issue/51169
Build tested: cockpit-389-ds-1.4.2.12-3.module+el8dsrv+6923+6ab1d5c5.noarch It is still crashing with the steps from #c8 TypeError: Cannot read property 'paginationOption' of undefined Moving to ASSIGNED.
The change needs to be included into the new build. https://pagure.io/389-ds-base/issue/51169
with build 389-ds-base-1.4.3.11-1.module+el8dsrv+7557+bc264682.x86_64 cockpit-389-ds-1.4.3.11-1.module+el8dsrv+7557+bc264682.noarch I tried all steps described above, plus more. I didn't reproduce any crash. Marking as Verified
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 (Red Hat Directory Server 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-2020:4911