#50787 dsconf problems
Closed: wontfix by firstyear. Opened by albertocrj.

Issue Description

When we try to enable a previous added config of atribute uniqueness using dsconf, got the following error:
Error: 'Namespace' object has no attribute 'plugin_cls'

And it seems to affect other functions of dsconf too.

Package Version and Platform

Centos7
389-Directory/1.4.2.4 B2019.348.049
Python 3.6.8

Steps to reproduce

  1. Add a config of attribute uniqueness - dsconf instance_name plugin attr-uniq add "uid-test" --attr-name uid)
  2. Try to enable it - dsconf instance_name plugin attr-uniq enable uid-test

Actual results

Error: 'Namespace' object has no attribute 'plugin_cls'

Expected results

Change nsslapd-pluginEnabled to on


Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.4.1

Hi @albertocrj

I've been able to reproduce this, and am working on a fix. Thanks for reporting it!

@albertocrj Can you tell me which other functions are affected?

https://pagure.io/389-ds-base/pull-request/50845

@firstyear

It also happens in 'dsconf instance_name pwpolicy get' for example.

~# dsconf RNP pwpolicy get
Error: 'PwPolicyManager' object has no attribute 'get_attr_list'

@firstyear
It also happens in 'dsconf instance_name pwpolicy get' for example.
~# dsconf RNP pwpolicy get
Error: 'PwPolicyManager' object has no attribute 'get_attr_list'

This was fixed last week

Metadata Update from @firstyear:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Back porting to 1.4.2 and 1.4.1

e71dc2707..3aae8c429 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

d3c792baf..b6cb5b2e8 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

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

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

Metadata