This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2151863 - dsidm Error: float() argument must be a string or a number, not 'NoneType'
Summary: dsidm Error: float() argument must be a string or a number, not 'NoneType'
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: 389-ds-base
Version: 11.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: DS11.7
: dirsrv-12.3
Assignee: LDAP Maintainers
QA Contact: LDAP QA Team
Evgenia Martynyuk
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-08 11:25 UTC by Anton Bobrov
Modified: 2024-06-26 13:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-26 13:48:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   DIRSRV-43 0 None None Red Hat Issue Tracker 2024-06-26 13:48:24 UTC
Red Hat Issue Tracker IDMDS-2993 0 None None None 2023-05-03 15:44:49 UTC

Description Anton Bobrov 2022-12-08 11:25:58 UTC 
Description of problem:

# dsidm -D "cn=Directory Manager" ldap://server -b "dc=example,dc=com" account entry-status "uid=user,ou=people,dc=example,dc=com"
Error: float() argument must be a string or a number, not 'NoneType'

The problem occurs when the Account Policy Plug-In is enabled but no account policies exist or assigned to a user which causes get_attr_val_utf8_l() to return None for limit in status() of idm/account.py

The fix would be a simple one-liner to just skip the check in this case eg

        # Locked indirectly through Account Policy plugin
        if process_account_policy and last_login_time and limit is not None:

or something like that.
Comment 1 Viktor Ashirov 2024-06-26 13:48:25 UTC 
This BZ has been automatically migrated to Red Hat Issue Tracker https://issues.redhat.com/browse/DIRSRV-43. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.