@Shadow00Caster Figured I’d add to here so others can follow.
We found that the system was in a really weird state. This state broke the root user password and it was not allowing services to be started properly. Worked together and reset the root user password. The installer still failed and we found the issue was due to how the OS was booting and starting services. It was using init as the service starter, but the command systemctl exists on the system. The service was failing with dbus messages because the systemd side was not what was used to load services on the system.
I’ve added a few checks just to ensure all will be well for the next release cycle.
Essentially I’m now checking three things.
Does the systemctl command exist? (command -v systemctl) Is the system booted to use systemd? (ps -p 1 -o comm= | grep systemd) Is the systemctl variable already set?