245rc1, analyze blame reports ~3 years for service unit times

[cmurf]

systemd version the issue has been seen with

systemd-245~rc1-1.fc32.x86_64

Used distribution

Fedora Rawhide

Expected behaviour you didn't see

actual times

Unexpected behaviour you saw

$ systemd-analyze
Startup finished in 1.367s (kernel) + 1.210s (initrd) + 6.668s (userspace) = 9.246s 
graphical.target was never reached
$ systemd-analyze blame
2y 11month 3w 5d 8h 7min 53.958s plymouth-read-write.service                                                              
2y 11month 3w 5d 8h 7min 53.958s avahi-daemon.service                                                                     
2y 11month 3w 5d 8h 7min 53.958s systemd-remount-fs.service                                                           
2y 11month 3w 5d 8h 7min 53.958s systemd-homed.service                                                                    
2y 11month 3w 5d 8h 7min 53.958s dev-mqueue.mount                                                                         
2y 11month 3w 5d 8h 7min 53.957s firewalld.service                                                                        
2y 11month 3w 5d 8h 7min 53.957s sysroot.mount                                                                            
2y 11month 3w 5d 8h 7min 53.957s import-state.service                                                                     
2y 11month 3w 5d 8h 7min 53.957s systemd-logind.service                                                                   
2y 11month 3w 5d 8h 7min 53.957s initrd-parse-etc.service                                                                 
2y 11month 3w 5d 8h 7min 53.957s systemd-vconsole-setup.service                                                           
2y 11month 3w 5d 8h 7min 53.957s systemd-user-sessions.service                                                            
2y 11month 3w 5d 8h 7min 53.957s cups.service                                                                             
2y 11month 3w 5d 8h 7min 53.956s dracut-cmdline.service                                                                   
2y 11month 3w 5d 8h 7min 53.956s systemd-fsck@dev-disk-by\x2duuid-8b4ba1a4\x2d963d\x2d4341\x2d93a2\x2df350f0db086a.service
2y 11month 3w 5d 8h 7min 53.956s user@1000.service                                                                        
2y 11month 3w 5d 8h 7min 53.956s kmod-static-nodes.service                                                                
2y 11month 3w 5d 8h 7min 53.955s polkit.service                                                                           
2y 11month 3w 5d 8h 7min 53.955s sys-fs-fuse-connections.mount                                                            
2y 11month 3w 5d 8h 7min 53.955s dracut-initqueue.service                                                                 
2y 11month 3w 5d 8h 7min 53.955s dracut-pre-udev.service                                                                  
2y 11month 3w 5d 8h 7min 53.955s systemd-journald.service                                                                 
2y 11month 3w 5d 8h 7min 53.954s sssd.service                                                                             
2y 11month 3w 5d 8h 7min 53.954s systemd-tmpfiles-setup.service                                                           
2y 11month 3w 5d 8h 7min 53.954s dev-vda3.swap                                                                            
2y 11month 3w 5d 8h 7min 53.953s initrd-cleanup.service                                                                   
2y 11month 3w 5d 8h 7min 53.953s nfs-convert.service                                                                      
2y 11month 3w 5d 8h 7min 53.953s abrtd.service                                                                            
2y 11month 3w 5d 8h 7min 53.953s plymouth-switch-root.service                                                             
2y 11month 3w 5d 8h 7min 53.953s boot-efi.mount               

Steps to reproduce the problem

1. Rawhide is up to date
2. dnf install kernel 5.5.2 fc31 and then dnf install systemd-245 from koji
   I did not rebuild the initramfs so systemd-244 starts up in the initramfs and switches to 245 at switchroot...

$ rpm -qa | grep systemd
systemd-bootchart-233-6.fc32.x86_64
systemd-pam-245~rc1-1.fc32.x86_64
systemd-245~rc1-1.fc32.x86_64
systemd-udev-245~rc1-1.fc32.x86_64
systemd-rpm-macros-245~rc1-1.fc32.noarch
rpm-plugin-systemd-inhibit-4.15.1-2.fc32.x86_64
systemd-libs-245~rc1-1.fc32.x86_64
systemd-container-245~rc1-1.fc32.x86_6

I see this same behavior in two identically configured systems: one baremetal, one VM.

[ml-]

related? 47cc458

[cmurf]

It's still a problem in systemd-245-1.fc33.x86_64

[yuwata]

related? 47cc458

Yeah. Thanks.

[yuwata]

It's still a problem in systemd-245-1.fc33.x86_64

It does not include the commit.

[mbiebl]

probably worth cherry-picking that fix in v245-stable

[mbiebl]

hah, @keszybz was already quicker then me: systemd/systemd-stable@084df9c