The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #15652

Service noop => true doesn't work

Added by Hari Sekhon about 2 years ago. Updated almost 2 years ago.

Status:DuplicateStart date:07/23/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:service
Target version:-
Affected Puppet version: Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


Description

I have a scenario where puppet is managing config files and services are either subscribed to those files or the files are notifying the service. The file contents need to change it’s a non-functional change and I don’t want the services to restart.

So I initially did

Service { noop => true }

in site.pp but this had no effect the service got restarted anyway.

Then I tried in the module class’s service definition itself to put noop => true but this also didn’t work and when the file content changed it restarted the service.

noop is a metaparam but it looks like puppet isn’t respecting it.

I’m running puppet 2.7.12 but I’ve had this issue way back since I was running 0.24.x. Before anyone says why not just commented out all the subscribe and notify lines, this affects a lot of modules and that would be very inefficient to do. The noop metaparam should theoretically work. Is this a design decision to not respect the metaparam if a dependent resource changes? Surely the metaparam should take precedence to at least give the user the choice.

History

#1 Updated by eric sorenson almost 2 years ago

  • Status changed from Unreviewed to Duplicate

This is a dup of a very old bug, #3763, which we should re-open.

#2 Updated by Andrew Parker almost 2 years ago

  • Target version deleted (2.7.x)

Also available in: Atom PDF