We are using systemd service files to start the buildmaster and buildslave services but due to how they're written, they can't be set to start on boot.

If you try to enable the services:
$ systemctl enable buildslave.service
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).

Fix the unit files such that they can be enabled to start at boot

== Service Templates ==
[[https://bitbucket.org/fedoraqa/ansible-playbooks/src/3b1e132b7a3c9a0959c64c0e09951a6c28ffac99/common/templates/buildmaster/buildmaster.service.j2?at=master|buildmaster service template]]
[[https://bitbucket.org/fedoraqa/ansible-playbooks/src/3b1e132b7a3c9a0959c64c0e09951a6c28ffac99/common/templates/buildslave/buildslave.service.j2?at=master|buildslave service template]]