Description of problem: Unable to create a suffix with countryName either via dscreate or the admin console
Version-Release number of selected component (if applicable): 389-ds-base-1.4.1.10-1.module+el8dsrv+4575+0d8b81fc.x86_64 389-ds-base-libs-1.4.1.10-1.module+el8dsrv+4575+0d8b81fc.x86_64
How reproducible: The issue can easily be reproduced
Steps to Reproduce: 1. Install RHDS11 packages 2. Create a file called rhds11-inst2.inf similar to the following using the template:
[general] config_version = 2 full_machine_name = rhds11.test.net start = True [slapd] instance_name = rhds11-inst2 port = 10389 root_password = xxxxxx secure_port = 10636 [backend-userroot] create_suffix_entry = True suffix = c=uk [backend-east] create_suffix_entry = True suffix = o=east [backend-west] create_suffix_entry = True suffix = o=west [backend-south] create_suffix_entry = True suffix = o=south
Run "dscreate -v from-file /var/tmp/rhds11-inst2.inf"
The following error is observed on the console where the dscreate command is executed: ldap.OBJECT_CLASS_VIOLATION: {'desc': 'Object class violation', 'info': 'attribute "c" not allowed\n'} ERROR: Error: Object class violation - attribute "c" not allowed
1. 2. 3.
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1807419
I am also addressing this issue in this issue:
https://pagure.io/389-ds-base/issue/50921
https://pagure.io/389-ds-base/pull-request/50929
commit 742922b
commit 5d162fc -> 1.4.2
60818c0..aa8c123 389-ds-base-1.4.1 -> 389-ds-base-1.4.1
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Commit c48f4d9 relates to this ticket
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3981
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.