Re: dsconf and dsctl bugs

[Mark Reynolds <mreynolds@xxxxxxxxxx>]

On 1/16/20 2:25 PM, Alberto Viana wrote:

Hi Guys,

389-Directory/1.4.3.1.20200116git4f9aafca9 B2020.016.1843

python3-lib389-1.4.3.1-20200116gita08202a5b.el8.noarch

dsconf:

If I try to create an instance got this error:

DEBUG: name 'ensure_list_str' is not defined
Traceback (most recent call last):
  File "/usr/sbin/dscreate", line 75, in <module>
    result = args.func(inst, log, args)
  File "/usr/lib/python3.6/site-packages/lib389/cli_ctl/instance.py", line 71, in instance_create
    if sd.create_from_inf(args.file):
  File "/usr/lib/python3.6/site-packages/lib389/instance/setup.py", line 527, in create_from_inf
    self.create_from_args(general, slapd, backends, self.extra)
  File "/usr/lib/python3.6/site-packages/lib389/instance/setup.py", line 654, in create_from_args
    self._install_ds(general, slapd, backends)
  File "/usr/lib/python3.6/site-packages/lib389/instance/setup.py", line 786, in _install_ds
    args = ' '.join(ensure_list_str(result.args))
NameError: name 'ensure_list_str' is not defined
ERROR: Error: name 'ensure_list_str' is not defined

The workaround was edit /usr/lib/python3.6/site-packages/lib389/instance/setup.py file and add to import ensure_list_str.

After that, everything works fine.

    This was just fixed yesterday :-)

dsctl:

I was facing the "name 'ensure_str' is not defined" problem, even after the fix (https://pagure.io/389-ds-base/c/4f9aafca9a9927812da5e37ce71d79d1fd23b25a?branch=master), the debug shows me no error, but the dsctl tells me that the instance removal failed (but in fact it deletes the instance).

    This was fixed today :-)

I tested with selinux disabled too.

DEBUG: Removing instance test
DEBUG: Checking for instance marker at /etc/dirsrv/slapd-test/dse.ldif
DEBUG: Found instance marker at /etc/dirsrv/slapd-test/dse.ldif! Proceeding to remove ...
DEBUG: Stopping instance test
DEBUG: systemd status -> True
DEBUG: Found instance marker at /etc/dirsrv/slapd-test/dse.ldif! Proceeding to remove ...
DEBUG: Stopping instance test
DEBUG: systemd status -> True
DEBUG: Removing /var/lib/dirsrv/slapd-test/bak
DEBUG: Removing /etc/dirsrv/slapd-test
DEBUG: Removing /etc/dirsrv/slapd-test
DEBUG: Removing /var/lib/dirsrv/slapd-test/db
DEBUG: Removing /var/lib/dirsrv/slapd-test/db/../
DEBUG: Removing /var/lib/dirsrv/slapd-test/changelogdb
DEBUG: Removing /var/lib/dirsrv/slapd-test/ldif
DEBUG: Removing /var/lock/dirsrv/slapd-test
DEBUG: Removing /var/log/dirsrv/slapd-test
DEBUG: Removing /usr/lib64/dirsrv/slapd-test
DEBUG: Removing /etc/sysconfig/dirsrv-test
DEBUG: Removing the systemd symlink
CRITICAL: Instance removal failed

This is caused by the same bug above that was also fixed today.

Mark

_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx

-- 

389 Directory Server Development Team
  

_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx