Jira (PUP-9935) service_provider for debian wrong on buster
Title: Message Title
Tobias Wolter updated an issue
Puppet / PUP-9935
service_provider for debian wrong on buster
Change By:
Tobias Wolter
*Puppet Version:* 6.7.2*Puppet Server Version:* n/a*OS Name/Version:* Debian 10Services cannot be managed correctly on Debian buster because the `service_provider` code does not consider buster a systemd distribution.*Desired Behavior:*Puppet using systemd.*Actual Behavior:* ``` {code} Debug: Executing: '/usr/sbin/service puppet status'dpkg: error: --compare-versions takes three arguments: Type dpkg --help for help about installing and deinstalling packages [*];Use 'apt' or 'aptitude' for user-friendly package management;Type dpkg -Dhelp for a list of dpkg debug flag values;Type dpkg --force-help for a list of forcing options;Type dpkg-deb --help for help about manipulating *.deb files;Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !Debug: Executing: '/usr/sbin/update-rc.d -f puppet remove'Debug: Executing: '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .'Error: Execution of '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .' returned 1: update-rc.d: error: unable to read /etc/init.d/puppetError: /Stage[main]/Profile::Base/Service[puppet]/enable: change from 'true' to 'false' failed: Execution of '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .' returned 1: update-rc.d: error: unable to read /etc/init.d/puppet ``` {code} The cause is following code in `/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/systemd.rb`: defaultfor :operatingsystem => :debian, :operatingsystemmajrelease => ["8", "stretch/sid", "9", "buster/sid"]This should not be a whitelist anymore. IMHO, it should be set as the Debian default, especially as PE 2018.1, as the oldest still supported version, has a minimum OS requirement of Debian 8 ('jessie') for the agent, which is a systemd distribution.
Add Comment
Jira (PUP-9935) service_provider for debian wrong on buster
Title: Message Title
Tobias Wolter updated an issue
Puppet / PUP-9935
service_provider for debian wrong on buster
Change By:
Tobias Wolter
*Puppet Version:* 6.7.2*Puppet Server Version:* n/a*OS Name/Version:* Debian 10Services cannot be managed correctly on Debian buster because the `service_provider` code does not consider buster a systemd distribution.*Desired Behavior:*Puppet using systemd.*Actual Behavior:*{code}Debug: Executing: '/usr/sbin/service puppet status'dpkg: error: --compare-versions takes three arguments: Type dpkg --help for help about installing and deinstalling packages [*];Use 'apt' or 'aptitude' for user-friendly package management;Type dpkg -Dhelp for a list of dpkg debug flag values;Type dpkg --force-help for a list of forcing options;Type dpkg-deb --help for help about manipulating *.deb files;Options marked [*] produce a lot of output - pipe it through 'less' or 'more' !Debug: Executing: '/usr/sbin/update-rc.d -f puppet remove'Debug: Executing: '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .'Error: Execution of '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .' returned 1: update-rc.d: error: unable to read /etc/init.d/puppetError: /Stage[main]/Profile::Base/Service[puppet]/enable: change from 'true' to 'false' failed: Execution of '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .' returned 1: update-rc.d: error: unable to read /etc/init.d/puppet{code}The cause is following code in ` * /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/systemd.rb ` * : {code} defaultfor :operatingsystem => :debian, :operatingsystemmajrelease => ["8", "stretch/sid", "9", "buster/sid"] {code} This should not be a whitelist anymore. IMHO, it should be set as the Debian default, especially as PE 2018.1, as the oldest still supported version, has a minimum OS requirement of Debian 8 ('jessie') for the agent, which is a systemd distribution.
Add Comment
Jira (PUP-9935) service_provider for debian wrong on buster
Title: Message Title Tobias Wolter created an issue Puppet / PUP-9935 service_provider for debian wrong on buster Issue Type: Bug Affects Versions: PUP 6.7.2 Assignee: Unassigned Components: Catalog Application Created: 2019/08/01 6:00 AM Labels: debian Priority: Major Reporter: Tobias Wolter Puppet Version: 6.7.2 Puppet Server Version: n/a OS Name/Version: Debian 10 Services cannot be managed correctly on Debian buster because the `service_provider` code does not consider buster a systemd distribution. Desired Behavior: Puppet using systemd. Actual Behavior: ``` Debug: Executing: '/usr/sbin/service puppet status' dpkg: error: --compare-versions takes three arguments:Type dpkg --help for help about installing and deinstalling packages [*]; Use 'apt' or 'aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Options marked [*] produce a lot of output - pipe it through 'less' or 'more' ! Debug: Executing: '/usr/sbin/update-rc.d -f puppet remove' Debug: Executing: '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .' Error: Execution of '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .' returned 1: update-rc.d: error: unable to read /etc/init.d/puppet Error: /Stage[main]/Profile::Base/Service[puppet]/enable: change from 'true' to 'false' failed: Execution of '/usr/sbin/update-rc.d puppet stop 00 1 2 3 4 5 6 .' returned 1: update-rc.d: error: unable to read /etc/init.d/puppet ``` The cause is
Jira (PUP-6713) Vim should highlight data types in a class definition
Title: Message Title Tobias Wolter commented on PUP-6713 Re: Vim should highlight data types in a class definition If this triggers a syntax file overhaul, be advised that heredocs are broken in a similar fashion. 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.
Jira (PUP-6713) Vim should highlight data types in a class definition
Title: Message Title Tobias Wolter commented on PUP-6713 Re: Vim should highlight data types in a class definition Reporter here, spent a couple of minutes trying to fix it with setting a syntax region that recognizes the brackets after the data type, but that didn't seem to lead anywhere due to lack of vimfu on my side. 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.
