| Setting the systemd START_TIMEOUT to 14400 is only useful for long migrations, but is not long enough for some installs, and it can mask startup issues with puppetdb when no-migrations are present. The end goal of this work is to enable the installer to upgrade PuppetDB via the upgrade subcommand, thus bypassing the systemd timeout, and start the puppetdb service with a shorter systemd start timeout, like 5 minutes. To do this PuppetDB upgrade will be triggered by a Puppet exec iff this subcommand exits non-zero before it is restarted by the full service restart that normally happens during Puppet applied PE infrastructure changes. |
