Vector is in CrashLoopBackOff state due to a 'Timestamp out of range' panic error

Issue

• Vector is in CrashLoopBackOff state due to a 'Timestamp out of range' panic error, with the following trace:

  $ oc -n openshift-logging get pod collector-XXXXX
  NAME              READY   STATUS             RESTARTS   AGE
  collector-XXXXX   0/1     CrashLoopBackOff   9          24m
  
  $ oc -n openshift-logging logs collector-XXXXX
  2025-07-22T06:07:46.285044293Z Creating the directory used for persisting Vector state /var/lib/vector/openshift-logging/collector
  2025-07-22T06:07:46.286758472Z Starting Vector process...
  2025-07-22T06:07:46.686681923Z 2025-07-22T06:07:46.686630Z  WARN vector::config::loading: Transform "output_default_lokistack_route._unmatched" has no consumers
  2025-07-22T06:07:48.892448681Z thread 'vector-worker' panicked at src/sinks/loki/sink.rs:256:68:
  2025-07-22T06:07:48.892448681Z Timestamp out of range
  2025-07-22T06:07:48.892448681Z note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
  2025-07-22T06:07:48.895109349Z 2025-07-22T06:07:48.895071Z ERROR sink{component_kind="sink" component_id=output_default_lokistack_application component_type=loki}: vector::topology: An error occurred that Vector couldn't handle: the task panicked and was aborted.