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

Bug 1817554

Summary: cockpit crashes when creating new sasl mapping
Product: Red Hat Directory Server Reporter: sgouvern
Component: cockpit-389-dsAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: RHDS QE <ds-qe-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 11.0CC: lkrispen, spichugi, tbordaz
Target Milestone: ---   
Target Release: dirsrv-11.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.4.2.11-1.module+el8dsrv+6254+69a018e7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-29 08:04:41 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 sgouvern 2020-03-26 15:01:29 UTC
Description of problem:
'Cockpit had an unexpected internal error.' when creating a new sasl mapping


Version-Release number of selected component (if applicable):
cockpit-389-ds-1.4.2.9-1.module+el8dsrv+6001+1cbc6dcf.noarch

How reproducible:
always

Steps to Reproduce:
1. Go to 'SASL settings and mappings'
2. Click 'Create new mapping'
3. Enter value for each field
4. Click 'create mapping'

Actual results:
message 'Ooops!' at the top right of the console
New mapping appears in the Sasl mappings table

Expected results:
cockpit does not crash

Additional info:

Javascript console details :
CMD: loadConfig: Get SASL settings ==> dsconf -j inst1 config get
index.js:sourcemap:83 CMD: loadMechs: Get supported SASL mechanisms ==> dsconf -j inst1 sasl get-mechs
index.js:sourcemap:83 CMD: get_and_set_sasl: Get SASL mappings ==> dsconf -j inst1 sasl list --details
index.js:sourcemap:83 CMD: createMapping: Create sasl mapping ==> dsconf -j inst1 sasl create --cn=example_map --nsSaslMapFilterTemplate=cn=\1 --nsSaslMapRegexString=\(.*\) --nsSaslMapBaseDNTemplate=ou=people,dc=example,dc=com --nsSaslMapPriority=100
index.js:sourcemap:83 CMD: loadConfig: Get SASL settings ==> dsconf -j inst1 config get
index.js:sourcemap:83 Uncaught TypeError: e.props.addNotification is not a function
    at Function.<anonymous> (index.js:sourcemap:83)
    at s (cockpit.js:sourcemap:979)
    at cockpit.js:sourcemap:991
    at n (cockpit.js:sourcemap:897)
index.js:sourcemap:83 CMD: loadMechs: Get supported SASL mechanisms ==> dsconf -j inst1 sasl get-mechs
index.js:sourcemap:83 CMD: get_and_set_sasl: Get SASL mappings ==> dsconf -j inst1 sasl list --details
index.js:sourcemap:83 CMD: loadConfig: Get SASL settings ==> dsconf -j inst1 config get

Comment 3 sgouvern 2020-04-20 06:54:16 UTC
With cockpit-389-ds-1.4.2.12-1.module+el8dsrv+6328+f04d7471.noarch / 389-ds-base-1.4.2.12-1.module+el8dsrv+6328+f04d7471.x86_64

No more crash when creating a new SASL mapping

=> marking as verified

Comment 5 errata-xmlrpc 2020-04-29 08:04:41 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, 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:1961