openSUSE-MicroOS.armv7l-16.0.0-RaspberryPi2-Snapshot20200528.raw

Booted and wondered why systemd-analyze wouldn't show me results. Turns out
transactional-update.timer was started immediately at first boot.

Maybe related to missing rtc on rpi? So the time warp caused by chrony catching
up triggered it?

# systemctl status transactional-update.timer
* transactional-update.timer - Daily update of the system
     Loaded: loaded (/usr/lib/systemd/system/transactional-update.timer;
enabled; vendor preset: enabled)
     Active: active (waiting) since Thu 2020-04-23 14:15:38 UTC; 1 months 10
days ago
    Trigger: Thu 2020-06-04 01:38:53 UTC; 11h left
   Triggers: * transactional-update.service
       Docs: man:transactional-update(8)


If so why April 23rd rather than end of May when the image was created?

# l /var/lib/chrony
total 0
drwxr-x--- 1 chrony chrony   0 May  2 22:23 ./
drwxr-xr-x 1 root   root   268 Jun  3 13:56 ../

Can and do we want to do something about this behavior or a matter of
documentation again?