Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1776227
Description of problem: When I try to get local password policy entry using dsconf, it fails with an error. Version-Release number of selected component (if applicable): 389-ds-base-1.4.2.4-3.module+el8.2.0+4718+1b57dca2.x86_64 python3-lib389-1.4.2.4-3.module+el8.2.0+4718+1b57dca2.noarch How reproducible: always Steps to Reproduce: 1. dsconf -D "cn=Directory Manager" ldap://localhost localpwp addsubtree ou=people,dc=example,dc=com Enter password for cn=Directory Manager on ldap://localhost: Successfully created subtree password policy 2. dsconf -D "cn=Directory Manager" ldap://localhost localpwp get ou=people,dc=example,dc=com Enter password for cn=Directory Manager on ldap://localhost: Error: 'PwPolicyManager' object has no attribute 'get_attr_list' Actual results: Error is returned instead of attributes: Error: 'PwPolicyManager' object has no attribute 'get_attr_list' Expected results: Local password policy should be returned. Additional info:
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1776227
Metadata Update from @mreynolds: - Issue assigned to mreynolds
https://pagure.io/389-ds-base/pull-request/50819
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Commit 2a67848 relates to this ticket
9d3bde5..d971bac 389-ds-base-1.4.2 -> 389-ds-base-1.4.2
9f3f5d5..51c604f 389-ds-base-1.4.1 -> 389-ds-base-1.4.1
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/3872
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.