Description of problem: On a fresh installation of Satellite, there is an admin user created during the first access to the WebUI. This user has no timezone info in the Satellite database. Only when updated using the user management in WebUI, the timezone is updated and saved correctly. Version-Release number of selected component (if applicable): spacewalk-backend-2.3.3-44 How reproducible: always Steps to Reproduce: 1. Install a fresh Satellite 5.7 server. 2. Connect with a web browser and create the first user (admin). 3. Run "spacewalk-debug" (spacewalk-backend-2.3.3-44 or higher required, older versions didn't export users-preferences file). 4. Check "users-preferences" file from spacewalk-debug output. There are only column names present, but no users. 5. Instead of spacewalk-debug you can use directly this SQL command: SELECT w.login as login, tz.display_name as timezone, ui.preferred_locale as locale FROM web_contact w, rhntimezone tz, rhnuserinfo ui WHERE ui.timezone_id = tz.id AND ui.user_id = w.id ORDER BY login Actual results: No timezone info in the database for the first satellite user right after its creation. Expected results: Timezone info present in the database for the first satellite user right after its creation. Additional info: This bug manifested itself while testing BZ1372721 which added users-preferences export.
If the timezone is not set in the DB, what timezone is used according to UI timestamps?
(In reply to Tomas Lestach from comment #1) > If the timezone is not set in the DB, what timezone is used according to UI > timestamps? Default timezone of the Satellite server. In my original case it was EDT timezone. After changing systemwide timezone to Europe/Prague and doing rhn-satellite restart, timestamps switched to the CEST timezone for the admin user.
To expand scope of this issue, this is relevant for user accounts created directly by "user.create" API call as well. Same problem as for the first user - users created by the API call has no timezone information set in the DB.
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog. This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.