Description of problem: When Importing an ldif file to initialize a suffix, a red message 'Ooops' appears in the head bar, and the file import is not performed, the 'Initialize database via LDIF file' window loops in 'Importing LDIF file' 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. On the 'Database' tab, select a suffix and click on 'Suffix tasks'/'Initialize suffix' 2. On the 'Initialize database via LDIF file' window which appears, select a displayed ldif file, or enter a path to a ldif file 3. Click on 'Import' 4. A popup window 'Initialize database from ldif' opens 5. Click 'yes I'm sure' then 'Initialize database' button Actual results: A red message 'Ooops' appears at the right of the head bar. The 'Initialize database from ldif' window remains opened, nothing happens. When closing the window, we come back to the 'Initialize database via LDIF file' window, which loops on 'Importing LDIF file' without ending. Need to close the window to come back to the web console, which seems to keep on working for the other functionalities. An ldapsearch shows that the ldif file was not imported Expected results: ldif file correctly imported, cockpit windows correctly displayed with a correct behavior Additional info:
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 hanging any more when importing an ldif file from 'Database'/'Suffix tasks'/'Initialize suffix' => 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, 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