The Local time and RTC time are different when using the timedatectl command

Is there any RTC hardware issue or this is normal behavior?

```
[root@localhost RTC]# timedatectl
Local time: Wed 2024-07-31 00:20:55 UTC
Universal time: Wed 2024-07-31 00:20:55 UTC
RTC time: Wed 2024-07-31 00:20:56
Time zone: UTC (UTC, +0000)
System clock synchronized: no
NTP service: inactive
RTC in local TZ: no
[root@localhost RTC]# timedatectl
Local time: Wed 2024-07-31 00:20:57 UTC
Universal time: Wed 2024-07-31 00:20:57 UTC
RTC time: Wed 2024-07-31 00:20:57
Time zone: UTC (UTC, +0000)
System clock synchronized: no
NTP service: inactive
RTC in local TZ: no
[root@localhost RTC]# timedatectl
Local time: Wed 2024-07-31 00:20:57 UTC
Universal time: Wed 2024-07-31 00:20:57 UTC
RTC time: Wed 2024-07-31 00:20:58
Time zone: UTC (UTC, +0000)
System clock synchronized: no
NTP service: inactive
RTC in local TZ: no
```

Start by reproducing the reported timedatectl output and compare Local time, Universal time, and RTC time across repeated runs. Check the issue's UTC configuration and determine whether the one-second difference is expected behavior or indicates a clock problem; done means documenting the explanation or identifying a confirmed defect.

Written by the indexing model from the issue text.