Issue #22660 has been updated by Melissa Stone.
Released in Puppet 3.4.0-rc1 ---------------------------------------- Bug #22660: Use consistent puppet agent service name on all platforms https://projects.puppetlabs.com/issues/22660#change-100515 * Author: Nick Fagerlund * Status: Closed * Priority: Normal * Assignee: * Category: * Target version: 3.4.0 * Affected Puppet version: * Keywords: fedora, systemd, rpm, package, agent * Branch: https://github.com/puppetlabs/puppet/pull/1966 ---------------------------------------- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
