Jira (PUP-6021) Tidy can not trigger resources

[Varac (JIRA)]

Varac created an issue

Puppet / PUP-6021 Tidy can not trigger resources Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Unassigned Created: 2016/03/08 7:08 AM Environment: puppet apply on debian jessie Priority: Normal Reporter: Varac Hi, i'm copying https://projects.puppetlabs.com/issues/3924 to here, because i can reproduce this with puppet 3.7.2: Hello all, got a strange issue – tidy does not notify resources. tidy {"messages": path => "/var/log", size => "10m", matches => [ "zmd-messages.log.*", "zypper.log-*"] age => "30d", recurse => "true", backup => "false", rmdirs => "true", notify => Exec["restart_syslog"]; } exec {"restart_syslog": command => "/etc/init.d/syslog restart", refreshonly => true; } This should clean all matching Files in /var/log and execute restart_syslog, only if it gets triggered from tidy messages, or? But the exec is ignored. Jan Add Comment

This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)

[Varac (JIRA)]

Varac updated an issue

Puppet / PUP-6021 Tidy can not trigger resources

Change By: Varac

Hi,  i'm copying https://projects.puppetlabs.com/issues/3924 to here, because i can reproduce this with puppet 3.7.2: Hello all, got a strange issue – tidy does not notify resources.

{code:java}

tidy {"messages":             path    => "/var/log",              size    => "10m",              matches => [ "zmd-messages.log.*", "zypper.log-*"]             age => "30d",              recurse => "true",             backup  => "false",              rmdirs  => "true",              notify  => Exec["restart_syslog"];     }              exec {"restart_syslog":         command     => "/etc/init.d/syslog restart",          refreshonly => true;     }

{code}

This should clean all matching Files in /var/log and execute restart_syslog, only if it gets triggered from tidy messages, or? But the exec is ignored. Jan

Add Comment

[Sean McDonald (JIRA)]

Sean McDonald assigned an issue to Varac

Puppet / PUP-6021 Tidy can not trigger resources

Change By: Sean McDonald Assignee: Varac

Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Sean McDonald (JIRA)]

Sean McDonald updated an issue

Puppet / PUP-6021 Tidy can not trigger resources

Change By: Sean McDonald Labels: needs_repro  triaged

Add Comment

[Sean McDonald (JIRA)]

Sean McDonald updated an issue

Puppet / PUP-6021 Tidy can not trigger resources Change By: Sean McDonald Labels: needs_repro

Add Comment

[Moses Mendoza (JIRA)]

Moses Mendoza commented on PUP-6021

Re: Tidy can not trigger resources Can you confirm this is still an issue on the current version of Puppet?

Add Comment

[Sean McDonald (JIRA)]

Sean McDonald updated an issue

Puppet / PUP-6021

Tidy can not trigger resources

Change By: Sean McDonald Team: Agent

Add Comment

[Martin Lausch (JIRA)]

Martin Lausch commented on PUP-6021

Re: Tidy can not trigger resources Faced the same issue: Described my findings and a little workaround very detailed here: https://ask.puppet.com/question/32226/resource-tidy-does-not-notify-exec-resource-at-all/

Add Comment

[Emil (JIRA)]

Emil commented on PUP-6021

Re: Tidy can not trigger resources

Faced the same issue with Puppet 5.4.0. Looking at the code I can only find a 'type' for the tidy resource but there is no 'provider'. Is the problem that the magic is done in the 'type' and not in the 'provider' and when tidy is removing files it is done using the file resource and with the tidy. So when tidy only has a 'type' is does not detect any changes and does therefore not send a notify?

Add Comment

This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-6021

Tidy can not trigger resources

Change By: Josh Cooper Sub-team: Coremunity

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Maximilian Philipps (Jira)]

Maximilian Philipps commented on PUP-6021

Re: Tidy can not trigger resources 2 years later, puppet 6.18.0 and the bug still isn't fixed.

Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Ian Freislich (Jira)]

Ian Freislich commented on PUP-6021

Re: Tidy can not trigger resources

Still present in 7.1.0

Add Comment

This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-6021

Re: Tidy can not trigger resources

I believe the problem is that there is a notify relationship between the tidy resource and the exec resource, but the tidy resource is never "out of sync". So it never notifies the exec. And the tidy type uses "generate" to dynamically add files to the catalog, however, that method does not add containment edges between the file resources and the downstream exec. Switching to "eval_generate" would solve that problem.

Add Comment

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-6021

Tidy can not trigger resources

Change By: Josh Cooper Labels: eval_generate needs_repro

Add Comment

[Glen Newman (Jira)]

Glen Newman commented on PUP-6021

Re: Tidy can not trigger resources Came across this issue (puppet version 6.18.0). Tidy resource cannot notify an exec resource. I noticed though, that turning the tidy into a file resource (with ensure => absent set) does work to notify the exec resource. The documentation for tidy has this note: > This resource type works by generating a file resource for every file that should be deleted and then letting that resource perform the actual deletion. I'm wondering if the "notify" attribute for a tidy resource is not preserved when the file resource is generated?

Add Comment

This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)