Thanks for filing this bug in Ubuntu, and for your troubleshooting and the debian MR.
The logrotate systemd service is actually triggered by a timer, and not by a reboot specifically. You can view when it last run, and when it will run, with the command "systemctl list-timers".
Regarding your troubleshooting and fix, it sounds reasonable. I would probably just check the exit status of the ping command, though.
Thanks for filing this bug in Ubuntu, and for your troubleshooting and the debian MR.
The logrotate systemd service is actually triggered by a timer, and not by a reboot specifically. You can view when it last run, and when it will run, with the command "systemctl list-timers".
Regarding your troubleshooting and fix, it sounds reasonable. I would probably just check the exit status of the ping command, though.
Let's see what debian has to say on that MR.