Jira (PUP-1201) Renaming puppetagent.service to puppet.service causes puppetagent.service to be left running after upgrading to 3.4

[Michael Stahnke (JIRA)]

Title: Message Title

Michael Stahnke commented on an issue   Re: Renaming puppetagent.service to puppet.service causes puppetagent.service to be left running after upgrading to 3.4 Hey Releng, let's fix some stuff. Add Comment   Puppet / PUP-1201 Renaming puppetagent.service to puppet.service causes puppetagent.service to be left running after upgrading to 3.4 Because of https://tickets.puppetlabs.com/browse/PUP-1200, users who are utilizing systemd as their init system will be left with two agents running forever. As part of the upgrade process, we need to: 1. stop puppetagent.service 2. disable puppetagent.service 3. remove puppetagent.service from the system 4. enable puppet.service 5. start puppet.s... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.