Package[centrifydc] doesn't notify Service[centrifydc]

[dekimsey]

I found that CentrifyDC doesn't get restarted after package updates. Is the package already doing this? I would think one would want to trigger a restart of the service after upgrades.

[dekimsey]

For my reference, saw this behavior on some hosts, looks like CentOS 5 ones.

config_report: 93842229

Level | Resource | message
-- | -- | --
notice | /Stage[main]/Centrify::Install/Package[centrifydc]/ensure | ensure changed '5.1.3-482' to '0:5.4.0-286'
notice | Puppet | Applied catalog in 73.71 seconds

config_report: 93842228

Level | Resource | message
-- | -- | --
notice | /Stage[main]/Centrify::Install/Package[centrifydc]/ensure | ensure changed '5.4.0-286' to '0:5.4.3-905'
notice | /Stage[main]/Centrify::Config/File[centrifydc_config]/seluser | seluser changed 'user_u' to 'system_u'
notice | /Stage[main]/Centrify::Adjoin::Password/Exec[adjoin_with_password] | Triggered 'refresh' from 1 events
notice | /Stage[main]/Centrify::Adjoin::Password/Exec[run_adflush_and_adreload] | Triggered 'refresh' from 2 events
notice | /Stage[main]/Centrify::Service/Service[centrify-sshd] | Triggered 'refresh' from 1 events
notice | /Stage[main]/Centrify::Service/Service[centrifydc] | Triggered 'refresh' from 1 events
notice | Puppet | Applied catalog in 72.23 seconds

[onzyone]

Looks like the services should have restarted. Did the service name change? notice | /Stage[main]/Centrify::Service/Service[centrifydc] | Triggered 'refresh' from 1 events

... NVM ... I see what you are saying, based on the first report ...

[dekimsey]

I was unclear, it only happened on a different host (CentOS 7 IIRC).

[onzyone]

I do not have a test bed setup ... is it posable to run puppet apply locally with a --debug and --trace flags?