On 20.07.2016 [11:13:13 -0000], Ivan Suzdal wrote: > @Nish, from my point of view it's absolutely expected behavior. In this > request, we trying to change default puppet service provider from > 'upstart' to 'systemd'. So when you change your init system from > 'systemd' to 'upstart' - puppet shall fall. Probably we can add another > init system checks, but it's looks like overcomplicating of existing > code.
Yes, I understand that. But "change default puppet service provider from 'upstart' to 'systemd'" is what I'm referring to -- where do you see this? I need an explicit test-case so I can figure out where things are wrong (esp. in the development release) and why. As I mentioned in my last comment, *if* the upstart package was not installed to begin with, I see no issues with puppet in 16.04. Was this a 14.04 -> 16.04 issue? More clearly, what is the basis (test case) for the OP statement of "puppet thinks it's still upstart"? -- 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
