Ah, thanks! This finally revealed something interesting. So pretty much everything is shut down already, but the last step triggers an assertion:
Dec 01 17:23:49 test systemd[1600]: systemd-poweroff.service: Executing: /bin/systemctl --force poweroff
Dec 01 17:23:49 test systemd[1]: [1;31mAssertion 'sd_id128_randomize(&id) >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.[0m
Dec 01 17:23:50 test systemd[1]: [1;31mCaught <ABRT>, dumped core as pid 1612.[0m
Dec 01 17:23:50 test systemd[1]: [1;31mFreezing execution.[0m
Ah, thanks! This finally revealed something interesting. So pretty much everything is shut down already, but the last step triggers an assertion:
Dec 01 17:23:49 test systemd[1600]: systemd- poweroff. service: Executing: /bin/systemctl --force poweroff randomize( &id) >= 0' failed at ../src/ core/dbus. c:657, function bus_on_ connection( ). Aborting.[0m
Dec 01 17:23:49 test systemd[1]: [1;31mAssertion 'sd_id128_
Dec 01 17:23:50 test systemd[1]: [1;31mCaught <ABRT>, dumped core as pid 1612.[0m
Dec 01 17:23:50 test systemd[1]: [1;31mFreezing execution.[0m