Support defining a custom reboot command

[pbolduc]

Proposed Changes

This change adds an optional custom_reboot_command. On Diet Pi, there is no dbus installed. See Diet Pi Release Notes.

DietPi ships without dbus and with logind masked by default, as we do not see their features being used on a typical DietPi system. Instead, dbus is installed and logind unmasked on demand on certain software installs or when chosen via dietpi.txt. However, the newer systemd version since Bookworm attempts dbus > logind communication in any case when calling poweroff/reboot/halt, despite no wall message being sent, e.g. to handle shutdown inhibitors (like open SSH session being able to prevent shutdown), and throws errors if either dbus is not reachable or logind not running. Until in case dbus or logind are further tied into common system commands or features, we solved the issue by creating shell functions for poweroff/reboot/halt which call the respective systemd target directly to bypass logind (and hence dbus), but fall back to the original commands, depending on given command-line parameters.

If custom_reboot_command is defined, the reboot_command parameter will be passed to the ansible.builtin.reboot module. If custom_reboot_command is not defined, then reboot_command is omitted and the default behavior occurs.

• Add commented out variable to sample/group_vars/all.yml with comments
• Add reboot_command: "{{ custom_reboot_command | default(omit) }}" to each reboot module usage.

Fixes one problem in #463

Checklist

• Tested locally
• Ran site.yml playbook
• Ran reset.yml playbook
• Did not add any unnecessary changes
• Ran pre-commit install at least once before committing
• 🚀

[pbolduc]

Is this workflow failure a transient issue? Dont understand why adding optional reboot command would cause,

INFO     Pruning extra files from scenario ephemeral directory
Error: Process completed with exit code 1.

[timothystewart6]

Is this workflow failure a transient issue? Dont understand why adding optional reboot command would cause,

INFO     Pruning extra files from scenario ephemeral directory
Error: Process completed with exit code 1.

Yes, this happens a lot with the ipv6 test. Going to update a few things in a PR. If this keeps happening I am leaning towards disabling that test.