Description of problem: Backport upstream commit to collect users timezone and browser locale options to spacewalk-debug spacewalk.master 4d8908158431fcc6a4c1b25710d8829ecd3a0faa Version-Release number of selected component (if applicable): Red Hat Satellite 5.7 [root@orbital ~]# cat spacewalk-debug/users-preferences login | timezone | locale -----------+-------------------------+-------- admin | United States (Eastern) | en_US alice | United States (Eastern) | bob | United States (Eastern) | FPLtest | United States (Eastern) | mmello | United States (Eastern) | pt_BR ro-user | United States (Eastern) | test_user | United States (Eastern) | (7 rows)
Moving to MODIFIED as the patch is available in upstream.
Tested on spacewalk-backend-2.3.3-44. The file "users-preferences" is present in the spacewalk-debug.tar.bz2 archive. Problem is that for the first user (created on freshly installed Satellite during the first connection to the WebUI), there is no timezone info present in the db. Subsequently, the "users-preferences" file is empty - containing only column headers, but no user info. Only after updating the user in WebUI Users -> Users List is timezone information for the first user saved (and then exported) to the database. User created using the WebUI Users -> Users -> Create user has timezone information present right from the beginning - no problem there. Users-preferences file should contain timezone info for first user, hence FailedQA. I have filled missing timezone information problem as BZ1380403.
spacewalk-.github: d44717aeba6f279f62c3bfe828f27cbc58aac87f
Tested again on spacewalk-backend-2.3.3-45. The "users-preferences" file contains list of all users this time, no matter if they have or have not the timezone info in the DB. Issue with the missing timezone is still valid, see the BZ1380403. VERIFIED
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-2662.html