Creating a replication manager account fails (dsconf + Cockpit)

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49981

• Created at 2018-10-16 15:47:36 by mmuehlfeldrh
• Assigned to nobody

---

Issue Description

Creating a replication manager account fails.

Package Version and Platform

389-ds-base-1.4.0.18-20181016gita8c37ead5.fc28.x86_64

Steps to reproduce

# dsconf -D "cn=Directory Manager" ldap://server.example.com replication create-manager --name "cn=demorepl" --passwd "demo"

Actual results

Error: {'desc': 'No such object'}

Expected results

Creating the replication manager account should succeed.

Additional information

This also fails with the same error in Cockpit.

[389-ds-bot]

Comment from spichugi (@droideck) at 2018-10-16 16:06:09

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.

[389-ds-bot]

Comment from spichugi (@droideck) at 2018-10-16 16:06:11

Metadata Update from @droideck:

• 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

[389-ds-bot]

Comment from spichugi (@droideck) at 2018-10-16 16:15:16

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/droideck/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/droideck/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

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2018-10-17 00:58:16

@droideck 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 ...

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2019-02-07 17:45:01

Metadata Update from @mreynolds389:

• Issue set to the milestone: 1.4.0

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-02-12 16:46:26

Metadata Update from @mreynolds389:

• Issue priority set to: major
• Issue set to the milestone: 1.4.3 (was: 1.4.0)