#51228 dsidm user status fails with Error: 'nsUserAccount' object has no attribute 'is_locked'
Closed: wontfix by spichugi. Opened by vashirov.

Issue Description

Create a user using dsidm user create and try to get its status using dsidm user status:

dsidm -b dc=example,dc=com myinst user status 
Enter uid to check : test
Error: 'nsUserAccount' object has no attribute 'is_locked'

Package Version and Platform

389-ds-base-1.4.3.8+


Metadata Update from @vashirov:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1862971

Metadata Update from @mreynolds:
- Issue priority set to: normal
- Issue set to the milestone: 1.4.2

Metadata Update from @spichugi:
- Issue assigned to spichugi

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

ea39a99eb..c5b60d6d9 master -> origin/master
59a811178..674dc76bf 389-ds-base-1.4.2 -> 389-ds-base-1.4.2
5e4d1625e..357d28bd2 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

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

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

cbcdf0506..52a09cedc master -> origin/master
a50b01494..f2e70bbe1 389-ds-base-1.4.2 -> 389-ds-base-1.4.2
cd7b96f21..2cd634ebe 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

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

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