[PUP-4503] systemd should be the default provider for Debian Jessie Created: 2015/04/30  Updated: 2015/06/24  Resolved: 2015/05/20

Status: Closed
Project: Puppet
Component/s: None
Affects Version/s: None
Fix Version/s: PUP 4.2.0

Type: Bug Priority: Normal
Reporter: Lee Packham Assignee: Melissa Stone
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by PUP-4540 Stock Puppet shipping with Ubuntu Viv... Closed
Relates
relates to PUP-2023 Debian/Ubuntu service provider improv... Resolved
Template:
Story Points: 3
Sprint: RE 2015-05-20
Release Notes: New Feature

 Description   

There is, unfortunately, a bug in systemd on Debian Jessie where older sysvinit scripts can't detect the enabled status. Therefore you should not just enable that as the default.

I wrote a version of a provider based on systemd that can check enabled via both systemd AND sysvinit and then the enable/disable in systemd does the right thing.

https://gist.github.com/leepa/9818b46b29b161413824

This is a bug because Puppet 3.7.5 does not work correctly at all on Debian Jessie because of this.



 Comments   
Comment by Mathieu Parent [ 2015/05/07 ]

I proposed the related https://github.com/puppetlabs/puppet/pull/3900

Comment by Melissa Stone [ 2015/05/11 ]

Lee Packham can you give me a test case for this? What services are you seeing this with?

Comment by Melissa Stone [ 2015/05/11 ]

I believe I have a potential fix for this, at https://github.com/puppetlabs/puppet/pull/3915. Feel free to test it out and let me know if it does or does not fix the issue you're seeing

Comment by Lee Packham [ 2015/05/11 ]

Any service that has a systemd AND sysvinit profile. So, Docker is a good example.

Comment by Past Haus [ 2015/05/19 ]

Merged in https://github.com/puppetlabs/puppet/commit/aaaf037128d6e1e19975e15261f356fabf5377a6

Comment by Melissa Stone [ 2015/05/19 ]

Eric Thompson just fyi this is ready for test. I'm not sure if you still don't have much visibility into these tickets on the releng board, but if you do, apologies for the repetition!

Comment by Melissa Stone [ 2015/05/20 ]

This has made it through CI. I'm not sure if you want to do any functional review, Eric Thompson, but for now I'm closing this ticket

Comment by Kurt Wall [ 2015/05/20 ]

Melissa Stone You can feel free to assign it to the QA group at which point it will show up for us. Dropping the QA label on it will also help. John Duarte this points to a larger workflow problem for platform, I think – we have no inherent visibility into tickets coming out of RelEng.

Generated at Mon Oct 14 05:49:11 PDT 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.