For some reason systemd is complaining about the StartLimitIntervalSec option in the resolv-prepender service. Maybe our version of systemd doesn't have that? In any case, there are repeated instances of this message in the journal:

Feb 28 22:46:12 ostest-master-0 systemd[1]: /etc/systemd/system/on-prem-resolv-prepender.service:9: Unknown key name 'StartLimitIntervalSec' in section 'Service', ignoring.

There are a couple of things to look at here: 1) Clean up the message. This mostly cosmetic. 2) Make sure the lack of this parameter isn't going to cause problems for the service. We included that specifically to prevent the service from restarting too quickly, and if it's not there we could run into issues. To my knowledge it hasn't caused any problems so it's probably fine, but we added it for a reason so we should make sure anyway.