dsconf problems

[389-ds-bot]

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

• Created at 2019-12-16 21:27:22 by albertocrj
• Closed at 2020-02-03 01:48:40 as fixed
• Assigned to nobody

---

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

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-01-16 17:43:51

Metadata Update from @mreynolds389:

• Custom field origin adjusted to None
• Custom field reviewstatus adjusted to None
• Issue set to the milestone: 1.4.1

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2020-01-23 03:14:45

Hi @albertocrj

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

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2020-01-23 03:40:36

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

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2020-01-23 03:44:57

#3899

[389-ds-bot]

Comment from albertocrj at 2020-01-23 18:55:44

@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'

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-01-23 18:59:24

@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

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2020-02-03 01:48:41

Metadata Update from @Firstyear:

• Issue close_status updated to: fixed
• Issue status updated to: Closed (was: Open)

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-05-08 23:06:49

Back porting to 1.4.2 and 1.4.1

e71dc27..3aae8c4 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

d3c792b..b6cb5b2 389-ds-base-1.4.1 -> 389-ds-base-1.4.1