Why did my physical system's clock had a huge time jump into the future?

Issue

• There was a suspicious forward time jump detected on a physical server. The system's date jumped forward several months:

  Apr 26 15:55:02 hostname chronyd[74033]: Selected source 10.238.136.5
  Apr 25 22:22:15 hostname chronyd[74033]: Selected source 10.238.103.5
  Apr 25 22:22:13 hostname chronyd[74033]: System clock was stepped by 33548.732982 seconds
  Apr 25 13:03:04 hostname chronyd[74033]: System clock wrong by 33548.732982 seconds, adjustment started
  Apr 25 13:03:04 hostname chronyd[74033]: Selected source 10.238.136.5
  Apr 25 13:03:00 hostname systemd[1]: Started NTP client/server.
  Apr 25 13:03:00 hostname chronyd[74033]: Frequency 0.644 +/- 0.023 ppm read from /var/lib/chrony/drift
  Apr 25 13:03:00 hostname chronyd[74033]: generatecommandkey directive is no longer supported
  Apr 25 13:03:00 hostname chronyd[74033]: commandkey directive is no longer supported
  Apr 25 13:03:00 hostname chronyd[74033]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 +DEBUG)
  Apr 25 13:03:00 hostname systemd[1]: Starting NTP client/server...
  Apr 25 13:03:00 hostname systemd[1]: Stopped NTP client/server.
  Apr 25 13:03:00 hostname chronyd[2272]: chronyd exiting
  Apr 25 13:03:00 hostname systemd[1]: Stopping NTP client/server...
  Apr 25 10:06:13 hostname chronyd[2272]: System clock wrong by 34364.678742 seconds, adjustment started
  Apr 25 10:06:13 hostname chronyd[2272]: Selected source 10.238.136.5
  Apr 25 10:04:03 hostname chronyd[2272]: Can't synchronise: no selectable sources
  Apr 25 10:04:03 hostname chronyd[2272]: Backward time jump detected!
  Jul 09 01:19:08 hostname chronyd[2272]: System clock wrong by -6414352.999122 seconds, adjustment started
  Jul 09 01:19:08 hostname chronyd[2272]: Selected source 10.238.136.5