ubuntu-389-directory-server team mailing list archive

[Jens Almer <2008518@xxxxxxxxxxxxxxxxxx>]

This can be reproduced by creating a second backend and attempting an
import or export.

For example:
dsconf $instance plugin retro-changelog enable
systemctl restart dirsrv@$instance
dsconf -v $instance backend export userRoot

Will result in this error:
Traceback (most recent call last):
  File "/usr/sbin/dsconf", line 138, in <module>
    result = args.func(inst, None, log, args)
  File "/usr/lib/python3/dist-packages/lib389/cli_conf/backend.py", line 287, in backend_export
    dn = _search_backend_dn(inst, be_name)
  File "/usr/lib/python3/dist-packages/lib389/cli_conf/backend.py", line 97, in _search_backend_dn
    if cn == del_be_name or str2dn(suffix) == str2dn(del_be_name):
  File "/usr/lib/python3/dist-packages/ldap/dn.py", line 52, in str2dn
    return ldap.functions._ldap_function_call(None,_ldap.str2dn,dn,flags)
  File "/usr/lib/python3/dist-packages/ldap/functions.py", line 55, in _ldap_function_call
    result = func(*args,**kwargs)
ldap.DECODING_ERROR
ERROR: Error:

-- 
You received this bug notification because you are a member of Ubuntu
389 Directory Server, which is subscribed to 389-ds-base in Ubuntu.
https://bugs.launchpad.net/bugs/2008518

Title:
  dsconf backend task decoding error

Status in 389-ds-base package in Ubuntu:
  Confirmed

Bug description:
  I'm running into a bug using 389-ds-base.  This was described in
  https://github.com/389ds/389-ds-base/issues/5353, and appears fixed
  with 2.0.16. If possible, it'd be great to have that updated.  I know
  you don't do rolling updates, but I thought I'd make you aware someone
  has hit this issue and would appreciate it included in the next
  release.  Cheers!

  Thanks!
  -James Moore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2008518/+subscriptions