Red Hat Bugzilla – Bug 1373111
Extend ovirt-aaa-jdbc-tool output to display current lock status on accounts
Last modified: 2017-03-22 07:22:22 EDT
====================== RFE TEMPLATE ======================== 1. Proposed title of this feature request Extend ovirt-aaa-jdbc-tool output to display current lock status on accounts 3. What is the nature and description of the request? An active account was locked out. While the CLI output showed that the lockout had recently been reset, the account was in actual fact still locked out. Displaying the current lockout status of the account would immediately highlight the issue. 4. Why does the customer need this? (List the business requirements here) 5. How would the customer like to achieve this? (List the functional requirements here) Add lockout status to the CLI output 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? - No 8. Does the customer have any specific timeline dependencies and which release would they like to target ? As soon as possible. 9. Is the sales team involved in this request and do they have any additional input? - No 10. List any affected packages or components. 11. Would the customer be able to assist in testing this functionality if implemented? Yes
Fix will be included in ovirt-engine-extension-aaa-jdbc-1.1.1
Fix is contained in ovirt-engine-extension-aaa-jdbc-1.1.1
Build found in erratum: ovirt-engine-extension-aaa-jdbc-1.1.1-1.el7ev
Wrong bug, please discard Verified status and last comment
# ovirt-aaa-jdbc-tool user show admin | grep Locked Account Locked: false # yum list ovirt-engine-extension-aaa-jdbc Installed Packages ovirt-engine-extension-aaa-jdbc.noarch 1.1.1-1.el7ev @4.0.5-2
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2793.html