Creating a replication manager account fails.
389-ds-base-1.4.0.18-20181016gita8c37ead5.fc28.x86_64
# dsconf -D "cn=Directory Manager" ldap://server.example.com replication create-manager --name "cn=demorepl" --passwd "demo"
Error: {'desc': 'No such object'}
Creating the replication manager account should succeed.
This also fails with the same error in Cockpit.
UI repl-manager creation is also failing for me. But CLI is okay. The '-h' states:
--name NAME The NAME of the new replication manager entry under cn=config: "cn=NAME,cn=config"
So you have to specify --name "demorepl" and it will work. Also, it is possible to specify full DN. But I'd say we should have better-formatted error message here.
--name "demorepl"
Metadata Update from @spichugi: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
For the UI part, looks like it fails in the different command: if we create repl-manager before replica entry is created, it fails to get the replica entry.
CMD: Creating replication manager: /home/spichugi/src/389-ds-base/src/lib389/cli/dsconf -j ldapi://%2fvar%2frun%2fslapd-local1.socket replication create-manager --name=cn=repl,cn=config --passwd=passwd123 CMD: Adding replication manager to configuration: /home/spichugi/src/389-ds-base/src/lib389/cli/dsconf -j ldapi://%2fvar%2frun%2fslapd-local1.socket replication set --repl-add-bind-dn=cn=repl,cn=config --suffix=dc=example,dc=com
In the CLI:
Traceback (most recent call last): File "/sbin/dsconf", line 128, in <module> result = args.func(inst, None, log, args) File "/usr/local/lib/python3.6/site-packages/lib389/cli_conf/replication.py", line 233, in set_repl_config replica = replicas.get(args.suffix) File "/usr/local/lib/python3.6/site-packages/lib389/replica.py", line 1273, in get replica = super(Replicas, self).get(selector, dn) File "/usr/local/lib/python3.6/site-packages/lib389/_mapped_object.py", line 905, in get raise ldap.NO_SUCH_OBJECT("No object exists given the filter criteria %s" % selector) ldap.NO_SUCH_OBJECT: No object exists given the filter criteria dc=example,dc=com
@spichugi Could we check if the string is a DN, then trust it, or if not, just follow that path? We probably need some better validatio about if the container of the DN exists too ...
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.0
Metadata Update from @mreynolds: - Issue priority set to: major - Issue set to the milestone: 1.4.3 (was: 1.4.0)
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/3040
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 - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.