> On 17 Dec 2019, at 06:17, Alberto Viana <albertocrj@xxxxxxxxx> wrote: > > Hi Mark, > > No problems at all, the idea is to contribute to the project. We're happy to have you here to help and contribute. Welcome! Appreciate the bug report :) > > Thanks!! > > Alberto Viana > > On Mon, Dec 16, 2019 at 12:19 PM Mark Reynolds <mreynolds@xxxxxxxxxx> wrote: > > > On 12/16/19 10:13 AM, Alberto Viana wrote: >> Hi Guys, >> >> I'm trying to config and enable uniqueness attribute plugin: >> >> ~# dsconf RNP plugin attr-uniq add "uid-test" --attr-name uid >> Successfully created the cn=uid-test,cn=plugins,cn=config >> >> if I try to enable it: >> ~# dsconf RNP plugin attr-uniq enable uid-test >> Error: 'Namespace' object has no attribute 'plugin_cls' >> >> Researching on google seems to be a python3 argparse bug (https://bugs.python.org/issue16308), but I'm not sure. >> >> My python version: >> Python 3.6.8 >> >> The workaround was use the "enable" option: >> ~# dsconf plugin attr-uniq add "uid-test" --enabled on --attr-name uid >> >> ~# dsconf RNP plugin attr-uniq show uid-test >> >> dn: cn=uid-test,cn=plugins,cn=config >> cn: uid-test >> nsslapd-plugin-depends-on-type: database >> nsslapd-pluginDescription: Enforce unique attribute values >> nsslapd-pluginEnabled: on >> nsslapd-pluginId: NSUniqueAttr >> nsslapd-pluginInitfunc: NSUniqueAttr_Init >> nsslapd-pluginPath: libattr-unique-plugin >> nsslapd-pluginType: betxnpreoperation >> nsslapd-pluginVendor: 389 Project >> nsslapd-pluginVersion: none >> objectClass: top >> objectClass: nsslapdplugin >> objectClass: extensibleObject >> uniqueness-attribute-name: uid >> >> But the problem seems to be in other dsconf functions too and is really annoying :/ >> Should I file a ticket? > Please! These are definitely bugs in our code. Keep in mind these tools are very new and some things got missed (obviously). We'll fix them all ASAP - just keep filing tickets. > > Thanks for your patience! > >> >> Thanks!! >> >> >> _______________________________________________ >> 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 — Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 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
