(PUP-5257) Update client init script for EL4#4252
Conversation
6fe16f7 to
45d83fb
Compare
|
Ouch, this is the third puppet/mco service related issue. We'll be fixing https://tickets.puppetlabs.com/browse/PUP-5057 in the sprint starting today. |
|
@geoffnichols Can we get a PUP ticket? |
45d83fb to
a502b9a
Compare
|
@joshcooper Updated to add a PUP ticket. |
ext/redhat/client.init
Outdated
There was a problem hiding this comment.
Why do we even bother calling status if we're just going to set RETVAL to 3?
There was a problem hiding this comment.
I think I was confused here. Update in progress...
719baf2 to
4c7e29e
Compare
4c7e29e to
c5c2e65
Compare
ext/redhat/client.init
Outdated
There was a problem hiding this comment.
Hmm, this doesn't account for the "service dead but pid file exists" case.
60670bf to
55da2ff
Compare
|
We probably need to ensure that the pidfile is created as well in the EL-4 case |
55da2ff to
417d667
Compare
Prior to this commit, managing the AIO puppet-agent's puppet service using `puppet resource` fails on EL4. Because EL4's /etc/init.d/functions do not take pid as an argument, we're not able to use the built-in 'status' or 'killproc' functions, as these will check the status of and/or kill the `puppet resource` process itself. This commit updates the EL init script to allow use of `puppet resource` to manage the puppet service on EL4, while continuing to use the built-in 'status' and 'killproc' functions on EL5 and EL6.
417d667 to
5b9835f
Compare
There was a problem hiding this comment.
@shrug Updated to ensure we're creating $piddir when starting the service.
|
👍 |
|
Is an mco fix needed as well? Once puppet and mco services can be managed on el/centos-4, we can revert e23bb92. |
|
@joshcooper It doesn't appear that an mco fix is needed. |
|
👍 |
|
@joshcooper This has a couple of thumbs up from RE, but we'd like someone from Client to merge if this looks ok. |
|
👍 |
…hat_client_init (PUP-5257) Update client init script for EL4
Prior to this commit, managing the AIO
puppet-agent's puppet service using
puppet resourcefails on EL4.Because EL4's /etc/init.d/functions do not
take pid as an argument, we're not able to
use the built-in 'status' or 'killproc'
functions, as these will check the status of
and/or kill the
puppet resourceprocessitself.
This commit updates the EL init script to
allow use of
puppet resourceto manage thepuppet service on EL4, while continuing to
use the built-in 'status' and 'killproc'
functions on EL5 and EL6.