Cyber Recovery - Time zone is changed after applying operating system security patch

Affects: All Cyber Recovery OVA versions prior to 19.13

On running the Cyber Recovery OVA, the user sees the time zone change after running an operating system security patch update.

The time zone changes to the default value stored in /etc/sysconfig/clock. 

The system time setting changes back to the default configuration after deployment. The assets, copy, logs, and schedule might have a different time zone than expected. 

There is a SLES issue where upgrading the time zone packages does not preserve the custom time zone. 

The following SLES article describes the issue.
https://www.suse.com/support/kb/doc/?id=000018825 (External Link)

The issue is addressed in v19.13 as part of a new installation or upgrade. See the 19.13 release notes for more information.

Do not apply the operating system update for a Cyber Recovery virtual appliance deployment before you update to Cyber Recovery version 19.13.
This ensures that the time zone does not change after applying the security patch,

Workaround (CR 19.12 or earlier):
 

1. Check the current settings in the /etc/sysconfig/clock file that match the output of datetimectl.
2. Change the time zone value to a different value by using the datetimectl set-timezone command.
3. Update to CR v19.13 by using the crsetup.sh --upgrade command.
4. After the update, remove the /etc/sysconfig/clock file from the host.
5. Run the operating system update for the CR virtual appliance. Verify that the time zone value remains the same as in step 2.