Issue

• Puppet agent getting automatically in a failed state after a successful restart.

  [root@compute-node ~]# systemctl  status puppet
  ● puppet.service - Puppet agent
     Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled; vendor preset: disabled)
     Active: failed (Result: start-limit) since Wed 2017-11-22 16:35:07 CET; 20h ago
    Process: 795029 ExecStart=/usr/bin/start-puppet-agent agent $PUPPET_EXTRA_OPTS --no-daemonize (code=exited, status=1/FAILURE)
   Main PID: 795029 (code=exited, status=1/FAILURE)
  
  Nov 22 16:35:07 compute-node.openstack.local start-puppet-agent[795029]: from /usr/share/ruby/monitor.rb:195:in `mon_exit'
  Nov 22 16:35:07 compute-node.openstack.local start-puppet-agent[795029]: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:143:in `ensure ...quire'
  Nov 22 16:35:07 compute-node.openstack.local start-puppet-agent[795029]: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:143:in `require'
  Nov 22 16:35:07 compute-node.openstack.local start-puppet-agent[795029]: from <internal:abrt_prelude>:2:in `<compiled>'
  Nov 22 16:35:07 compute-node.openstack.local systemd[1]: puppet.service: main process exited, code=exited, status=1/FAILURE
  Nov 22 16:35:07 compute-node.openstack.local systemd[1]: Unit puppet.service entered failed state.
  Nov 22 16:35:07 compute-node.openstack.local systemd[1]: puppet.service failed.
  Nov 22 16:35:07 compute-node.openstack.local systemd[1]: start request repeated too quickly for puppet.service
  Nov 22 16:35:07 compute-node.openstack.local systemd[1]: Failed to start Puppet agent.
  Nov 22 16:35:07 compute-node.openstack.local systemd[1]: puppet.service failed.
  Hint: Some lines were ellipsized, use -l to show in full.