Description of problem: Instance fails to start after restart when creating an attribute uniqueness. This is because the new entry is missing 'uniqueness-subtrees' attribute (subtree was correctly filled in webUI form). Workaround is to manually create 'uniqueness-subtrees' : 'dc=example,dc=com' for 'cn=telephonenumber uniqueness,cn=plugins,cn=config' to make the instance start. 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 'Plugins' tab click on 'Attribute Uniqueness' 2. Click on 'Add config' and create a custom attribute uniqueness (e.g. for telephoneNumber) 3. Restart the instance Actual results: Instance fails to start. Expected results: Attribute 'uniqueness-subtrees' should be created and instance starts successfully. Additional info: [24/Mar/2020:09:07:15.314654140 -0400] - ERR - plugin_dependency_startall - Failed to start betxnpreoperation plugin telephonenumber uniqueness [24/Mar/2020:09:07:15.384467419 -0400] - ERR - NSUniqueAttr - uniqueness_entry_to_config - Objectclass for subtree entries is not defined [24/Mar/2020:09:07:15.388398325 -0400] - ERR - plugin_dependency_startall - Failed to start betxnpreoperation plugin telephone uniqueness [24/Mar/2020:09:07:15.391326663 -0400] - ERR - NSUniqueAttr - uniqueness_entry_to_config - Objectclass for subtree entries is not defined [24/Mar/2020:09:07:15.399010028 -0400] - ERR - plugin_dependency_startall - Failed to start betxnpreoperation plugin telephonenumber uniqueness [24/Mar/2020:09:07:15.409427137 -0400] - ERR - plugin_dependency_startall - Failed to resolve plugin dependencies [24/Mar/2020:09:07:15.413010024 -0400] - ERR - plugin_dependency_startall - betxnpreoperation plugin telephonenumber uniqueness is not started
Build tested: 389-ds-base-1.4.2.12-1.module+el8dsrv+6328+f04d7471.x86_64 cockpit-389-ds-1.4.2.12-1.module+el8dsrv+6328+f04d7471.noarch Created attribute uniqueness is not missing the 'uniqueness-subtrees' attribute. Instance starts correctly after restart. 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