Time not synchronized via sys-net

[sjvudp]

How to file a helpful issue

Qubes OS release

4.1.1

Brief summary

When the network cable is not plugged in when booting Qubes OS (at least), and the cable is plugged in later (and network connection was established successfully), then the system dime as displayed in the top of the GUI is not correct.
sys-net (Fedora 36) has the clocksync service enabled.

Steps to reproduce

The only indication I found in the logs of sys-net was:
[2022-09-18 22:25:37] Logfile Opened
...
[2022-09-18 22:25:41] [ 0.284631] PM: RTC time: 20:25:41, date: 2022-09-18
...
[2022-09-18 22:25:42] [ 0.760552] rtc_cmos 00:02: registered as rtc0
[2022-09-18 22:25:42] [ 0.760602] rtc_cmos 00:02: setting system clock to 2022-09-18T20:25:42 UTC (1663532742)
[2022-09-18 22:25:42] [ 0.760630] rtc_cmos 00:02: alarms up to one day, 114 bytes nvram, hpet irqs
...
[2022-09-18 22:25:49] Fedora Linux 36 (Thirty Six)
[2022-09-18 22:25:49] Kernel 5.15.63-1.fc32.qubes.x86_64 on an x86_64 (hvc0)
[2022-09-18 22:25:49]
...
[ 31.198175] r8169 0000:00:06.0 ens6: Link is Up - 1Gbps/Full - flow control rx/tx
[2022-09-18 22:26:12] [ 31.198205] IPv6: ADDRCONF(NETDEV_CHANGE): ens6: link becomes ready
...
[2022-09-18 22:26:15] [ 34.283062] systemd-journald[266]: Time jumped backwards, rotating.
...
[2022-09-18 22:41:07] [ 926.560952] audit: type=1131 audit(1663526471.083:132): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

So you see nothing changed the clock. The clock was expected to jump back two hours as the RTC runs local time (CEST):

[master@dom0 ~]$ sudo timedatectl
               Local time: Sun 2022-09-18 22:32:41 CEST
           Universal time: Sun 2022-09-18 20:32:41 UTC 
                 RTC time: Sun 2022-09-18 20:32:41     
                Time zone: Europe/Berlin (CEST, +0200) 
System clock synchronized: no                          
              NTP service: inactive                    
          RTC in local TZ: no 

Expected behavior

Clock should be corrected.

Actual behavior

Clock isn't corrected.

Status in sys-net is:

● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled>
    Drop-In: /usr/lib/systemd/system/systemd-timesyncd.service.d
             └─30_qubes.conf
     Active: active (running) since Sun 2022-09-18 22:25:45 CEST; 1h 24min left
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 431 (systemd-timesyn)
     Status: "Initial synchronization to time server 167.86.115.96:123 (2.fedor>
      Tasks: 2 (limit: 381)
     Memory: 964.0K
        CPU: 5ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─ 431 /usr/lib/systemd/systemd-timesyncd

Sep 18 22:25:45 sys-net systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization...
Sep 18 22:25:45 sys-net systemd[1]: Started systemd-timesyncd.service - Network Time Synchronization.
Sep 18 20:26:18 sys-net systemd-timesyncd[431]: Initial synchronization to time server 167.86.115.96:123 (2.fedora.pool.ntp.org).