Description of problem: Under users tab, First Name is not displayed under users table for admin despite being populated Version-Release number of selected component (if applicable): ovirt-engine-4.1.0-0.0.master.20161106231312.git19a3a39.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. Go to users tab and check first name for admin user is displayed as "admin" under the users table Actual results: missing first name Expected results: showing first name Additional info: # ovirt-aaa-jdbc-tool user show admin -- User admin(46c4f180-e88a-496c-8463-c5ef0c8c082d) -- Namespace: * Name: admin ID: 46c4f180-e88a-496c-8463-c5ef0c8c082d Display Name: Email: First Name: admin Last Name: Department: Title: Description: Account Disabled: false Account Locked: false Account Unlocked At: 1970-01-01 00:00:00Z Account Valid From: 2016-11-07 10:57:46Z Account Valid To: 2216-11-07 10:57:46Z Account Without Password: false Last successful Login At: 2016-11-07 15:05:50Z Last unsuccessful Login At: 1970-01-01 00:00:00Z Password Valid To: 2216-09-20 11:03:04Z
Ondro, could you please check?
The problem is that the users table is updated with incorrect first/last name value, everytime user is logged in (as it's updated). This apply to all users. Marking as regression as I remember this used to work right.
The problem is with: - first name - last name - admin/user icon - namespace - e-mail
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
*** Bug 1396824 has been marked as a duplicate of this bug. ***
Add new user updates all attributes fine. But after login Firstname, Lastname and Namespace are empty. tested in ovirt-engine-4.0.6-0.1.el7ev.noarch
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.
Moving back to MODIFIED, engine build has not been updated in this week's repository, so you tested that with an old version, which does not contain the fix.
now it's OK verified in ovirt-engine-4.0.6.1-0.1.el7ev.noarch