Jira (PUP-7635) Custom service provider is always selected as default

[Daniel Urist (JIRA)]

Title: Message Title

Daniel Urist created an issue   Puppet / PUP-7635 Custom service provider is always selected as default Issue Type: Bug Affects Versions: PUP 4.10.1 Assignee: Unassigned Components: Types and Providers Created: 2017/06/08 9:59 AM Environment: Server environment: Debian 8 (jessie) puppetserver package v.2.7.2-1puppetlabs1 Client environment: Debian 8 (jessie) puppet package v.4.8.2-5~bpo8+1 (from debian backports) Priority: Normal Reporter: Daniel Urist I'm trying to create a custom service provider to be distributed with a module. I don't want it to ever be selected as the default service provider, but it's always selected as the default over the debian provider. Here is a trivial test case for the service provider: Puppet::Type.type(:service).provide :testdefaultservice, :parent => :init do def startcmd [ "/bin/true" ] end   def stopcmd [ "/bin/true" ] end   def restartcmd [ "/bin/true" ] end   def statuscmd [ "/bin/true" ] end end I get this warning from puppet agent: Warning: Found multiple default providers for service: testdefaultservice, debian; using testdefaultservice Note that my test case contains no "defaultfor" statements (unlike the debian service provider) and its parent is init, which is the same as the debian service provider, so it should be at the same level of specificity. So, why is it being chosen as the default? Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.