** Description changed:

+ [Impact]
+ 
+  * Puppet incorrectly detects the service manager on Ubuntu 16.04 and
+ 16.10 as upstart, rather than systemd.
+ 
+  * Various puppet-driven commands fail as they do not use the systemd
+ interfaces.
+ 
+ [Test Case]
+ 
+  * # upstart is required to confuse Puppet
+ apt install -y puppet upstart tftpd-hpa
+ 
+ # fails without fix
+ puppet apply -e "service { 'tftpd-hpa': ensure => stopped }"
+ 
+ # install fixed package
+ 
+ # works
+ puppet apply -e "service { 'tftpd-hpa': ensure => stopped }"
+ 
+ [Regression Potential]
+ 
+  * Currently, puppet is unable to apply configurations to 16.04, 16.10
+ and 17.04 (fix is in -proposed for 17.04) when upstart is installed.
+ This change will make puppet correctly use systemd for service
+ manipulation, and I believe the likelihood of regression is low.
+ 
+  * The primary source of regressions would be users who have modified
+ their puppet installations to work around this issue. I believe they
+ will be generally unaffected by fixing the underlying issue.
+ 
+ ---
+ 
  AFAIK, Ubuntu has systemd as default init system since 15.04 release. 
Although, puppet thinks it's still upstart.
  This behavior is already fixed in upstream puppet code. Please, add this 
patch to Xenial puppet package.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570472

Title:
  Set systemd as default service provider

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to