+++ This bug was initially created as a clone of Bug #2214294 +++ Description of problem: maxsequence is not handled correctly in the ipapwpolicy module. There is a typo in the parameter name. Version-Release number of selected component (if applicable): ansible-freeipa-1.10.0 How reproducible: Always Steps to Reproduce: 1. Change or set maxsequence with ipapolicy module Actual results: maxsequence is not changed Expected results: maxsequence is changed --- Additional comment from Thomas Woerner on 2023-06-12 13:58:20 UTC --- Upstream PR #1081 Fix typo in ipapwpolicy.py https://github.com/freeipa/ansible-freeipa/pull/1081 Upstream PR #1082 pwpolicy test: Fix maxsequence test https://github.com/freeipa/ansible-freeipa/pull/1082
Verified ansible-2.9.27-1.el8ae.noarch ansible-freeipa-1.11.0-1.el8.noarch PASSED ansible_freeipa_tests/pwpolicy/test_pwpolicy.py::Testpwpolicy::test_pwpolicy_update_maxsequence PASSED ansible_freeipa_tests/pwpolicy/test_pwpolicy.py::Testpwpolicy::test_pwpolicy_update_maxsequence_0 PASSED ansible_freeipa_tests/pwpolicy/test_pwpolicy.py::Testpwpolicy::test_pwpolicy_update_maxsequence_with_nagetive_number PASSED ansible_freeipa_tests/pwpolicy/test_pwpolicy.py::Testpwpolicy::test_pwpolicy_update_maxsequence_maxnumber PASSED ansible_freeipa_tests/pwpolicy/test_pwpolicy.py::Testpwpolicy::test_pwpolicy_update_maxsequence_reset PASSED ansible_freeipa_tests/pwpolicy/test_pwpolicy.py::Testpwpolicy::test_pwpolicy_update_maxsequence_with_nonnumeric Based on the above test results, marking the bug Verified