Issue #22660 has been updated by Jason Antman. Status changed from Unreviewed to Accepted
Yes, this appears to be a bug. Looking at https://github.com/puppetlabs/puppet/pull/1166 my impression is that the change was unintended (which is backed up by the fact that fedora < 17, which still uses SysV Init instead of Systemd, still has the agent called "puppet"). I've added the author and committer as watchers to see if they can shed any additional light on this (niels? matthaus?). Marking as accepted for now. Assuming there's no other feedback for an intentional reason this was done, I'll try and circle back today with a PR to fix. The fedora packaging spec specifically allows symlinks for name changes (https://fedoraproject.org/wiki/Packaging:Systemd#Naming) so we should probably have the spec file install the puppet.unit file, and for the forseeable future, symlink puppetagent.spec to it so we don't break users who have already adjusted to this. ---------------------------------------- Bug #22660: Use consistent puppet agent service name on all platforms https://projects.puppetlabs.com/issues/22660#change-98249 * Author: Nick Fagerlund * Status: Accepted * Priority: Normal * Assignee: * Category: * Target version: * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- For unknown reasons, the puppet agent service was renamed to `puppetagent` as part of #16144... but only on Fedora. Everywhere else it's `puppet`. This inconsistency is bad and pointless. 1. Let's restore `puppet` as the agent's service name on Fedora. It's possible systemd supports some form of aliasing or symlinking; if so, we should change the name to `puppet` and use aliasing to keep `puppetagent` working until Puppet 4 (when we can remove it). If aliasing is infeasible, we should ship duplicate service configs to re-enable `puppet`. 2. Can anyone give a really really good reason for changing the name of the agent service and inconveniencing everybody? Is `puppet` confusing somehow? If so, we should change it EVERYWHERE at the same time on the Puppet 4 boundary. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- 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.
