On all Junos OS Evolved platforms, Time-zone info changes to default UTC(Universal Time Coordinated) after upgrade is done with restart-upgrade. This issue is applicable to all images(official release and JSU), and happens only with restart-upgrade.
Step 1. The time-zone on PTX10008/22.4R2.11-EVO is now IST(Indian Standard Time).
{master}
user@ptx10008-re0> show version
Hostname: ptx10008-re0
Model: ptx10008
Junos: 22.4R2.11-EVO
Yocto: 3.0.2
Linux Kernel: 5.2.60-yocto-standard-g5039935
JUNOS-EVO OS 64-bit [junos-evo-install-ptx-x86-64-22.4R2.11-EVO]
user@ptx10008-re0> show configuration groups default system time-zone
Apr 09 06:51:30 <<------------------------------------------------------------- IST time
time-zone Asia/Calcutta;
user@ptx10008-re0> request system software validate-restart /var/tmp/junos-evo-install-ptx-x86-64-22.4R2-J6.1-EVO.iso
Apr 09 06:52:12
Validating software image and getting ISSU services impact /var/tmp/junos-evo-install-ptx-x86-64-22.4R2-J6.1-EVO.iso...
Download and Validate in Progress
re0: Running pre-checks for 'junos-evo-install-ptx-x86-64-22.4R2-J6.1-EVO'
re0: Pre-checks pass successfully, copying files to software area
re0: Starting validation : /var/tmp/junos-evo-install-ptx-x86-64-22.4R2-J6.1-EVO.iso
re0: Validating version : junos-evo-install-ptx-x86-64-22.4R2-J6.1-EVO
re0: Running prechecks for JSU image...
re0: JSU base release 22.4R2.11-EVO matches with Current Release: 22.4R2.11-EVO.
re0: Starting JSU package installation...
re0: Copying Files from base version junos-evo-install-ptx-x86-64-22.4R2.11-EVO ...
re0: Copying Files from JSU image...
re0: Signing files...
re0: Running post install commands...
re0: Post install sequence was successful.
re1: Running pre-checks for 'junos-evo-install-ptx-x86-64-22.4R2-J6.1-EVO'
re1: Pre-checks pass successfully, copying files to software area
re1: Running post install commands...
re1: Post install sequence was successful.
re0: Updating all nodes...
re0: Other nodes have been updated successfully
re0: Gathering impact report...
re0: Installation was successful
Image validation succeeded. ISSU impact report:
*** Restart Apps list ***
hwdre
arpd
Validate cleanup succeeded.
Image validation succeeded.
Step 2. Installing 22.4R2-J6.1-EVO on 22.4R2.11-EVO with restart option.
user@ptx10008-re0> request system software add /var/tmp/junos-evo-install-ptx-x86-64-22.4R2-J6.1-EVO.iso restart
Apr 09 06:58:27
Adding software images. This process can take several minutes. Please be patient...
re0: Starting upgrade : /var/tmp/junos-evo-install-ptx-x86-64-22.4R2-J6.1-EVO.iso
re0: Upgrade version : junos-evo-install-ptx-x86-64-22.4R2-J6.1-EVO
re0: Boot version is now 'junos-evo-install-ptx-x86-64-22.4R2-J6.1-EVO'
re1: Boot version is now 'junos-evo-install-ptx-x86-64-22.4R2-J6.1-EVO'
Image validation and installation succeeded. Restarting Applications.
Activating active instance of app hwdre on node re0
Activating active instance of app hwdre on node re1
Activating active instance of app arpd on node re0
Activating active instance of app arpd on node re1
Image activation succeeded for hwdre on node re0
Stopping active instance of app hwdre on node re0
Image activation succeeded for hwdre on node re1
Stopping active instance of app hwdre on node re1
Image activation succeeded for arpd on node re0
Stopping active instance of app arpd on node re0
Image activation succeeded for arpd on node re1
Stopping active instance of app arpd on node re1
App hwdre stopped on node re1
Starting active instance of app hwdre on node re1
App arpd stopped on node re1
Starting active instance of app arpd on node re1
App arpd stopped on node re0
Starting active instance of app arpd on node re0
App hwdre stopped on node re0
Starting active instance of app hwdre on node re0
App arpd started/restarted on node re1
App arpd started/restarted on node re0
App hwdre started/restarted on node re1
App hwdre started/restarted on node re0
*** Restart Summary ***
*** Restart Success ***
hwdre (re0)
hwdre (re1)
arpd (re0)
arpd (re1)
Please check the status of applications using 'show system alarms'
user@ptx10008-re0>
user@ptx10008-re0> show system uptime
Apr 09 07:06:07
Current time: 2024-04-09 07:06:07 IST <<---------------------------------------- IST time
Time Source: NTP CLOCK
Node booted: 2024-04-09 06:39:58 IST (00:26:09 ago)
System booted: 2024-04-09 06:41:16 IST (00:24:51 ago)
Protocols started: 2024-04-09 06:41:27 IST (00:24:40 ago)
Last configured: 2024-04-09 06:50:11 IST (00:15:56 ago) by user
7:06AM up 26 min, 2 users, load averages: 0.69, 1.38, 1.31
Apr 09 07:06:26
user@ptx10008-re0> exit
Apr 09 07:07:00
Step 3. Time-zone information changes to default UTC time after logout and re-login the system.
user@ptx10008-re0> set cli timestamp
Apr 09 01:38:12 <<----------------------------------------------------------------- UTC time
CLI timestamp set to: %b %d %T
Apr 09 01:38:17
Current time: 2024-04-09 01:38:17 UTC <<--------------------------------------- UTC time zone
Node booted: 2024-04-09 01:09:58 UTC (00:28:19 ago)
System booted: 2024-04-09 01:11:16 UTC (00:27:01 ago)
Protocols started: 2024-04-09 01:11:27 UTC (00:26:50 ago)
Last configured: 2024-04-09 01:20:11 UTC (00:18:06 ago) by user
1:38AM up 28 min, 2 users, load averages: 0.56, 1.08, 1.21
This issue is fixed via PR1803511, and can be worked around by reboot-upgrade.