Created attachment 1527396 [details] User name appearing multiple times in the user list Description of problem: A new user name appears multiple times in the users' list (under Administration). The number of entries is directly related to the number of times that user tries to login. This happens with both internal and LDAP users. Version-Release number of selected component (if applicable): 4.3 How reproducible: Always Steps to Reproduce: 1. create a local user using ovirt-aaa-jdbc-tool (and Do not grant the user login access from the web admin portal), eg: #ovirt-aaa-jdbc-tool user add guest1 --attribute=firstName=guest #ovirt-aaa-jdbc-tool user password-reset guest1 2. open the web portal and try to login as the new user (guest1). This message should appear: "Unable to log in because the password has expired. Change the password to proceed." 3. Change the password. 4. Try to login with the new password you have created for guest1. You will see the message: "The user guest1@internal is not authorized to perform login" 5. Click on "Administration Portal" or "VM Portal" at least 3 times 6. Log in as the admin user and go to Administration->Users Actual results: The new user name (guest1) appears multiple times in the list, once for each time the user had clicked on either "Administration Portal" or "VM Portal", plus one for the original login attempt. Expected results: The new user name should appear only once in the user list. Additional info: This was also observed with LDAP users. Also, if the user is deleted using ovirt-aaa-jdbc-tool, the web session still adds the user to the to the user list for each login attempt.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Verified on ovirt-engine-4.3.2.1-0.1.el7.noarch
This bugzilla is included in oVirt 4.3.2 release, published on March 19th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.