[Puppet - Bug #16121] Cron user change results in duplicate entries on target user

Issue #16121 has been updated by Matthaus Owens. Released in Puppet 3.2.0-rc1 Bug #16121: Cron user change results in duplicate entries on target user https://projects.puppetlabs.com/issues/16121#change-89542 * Author: Chris Henry * Status: Closed * Pri

[Puppet - Bug #16121] Cron user change results in duplicate entries on target user

Issue #16121 has been updated by Charlie Sharpsteen. Keywords set to customer Bug #16121: Cron user change results in duplicate entries on target user https://projects.puppetlabs.com/issues/16121#change-87849 * Author: Chris Henry * Status: In Topic Bran

[Puppet - Bug #16121] Cron user change results in duplicate entries on target user

Issue #16121 has been updated by Felix Frank. To whom it may concern. This appears to be a duplicate of #2251. The discussion over there was rather fruitful, and we concluded that this shouldn't be fixed in the way Stefan did. Instead of removing the crontab from the original file, it should

[Puppet - Bug #16121] Cron user change results in duplicate entries on target user

Issue #16121 has been updated by Stefan Schulte. Assignee changed from Chris Henry to Stefan Schulte Chris - thanks for the input. I was able to verify that a cronjob is not moved from one target to the other. The old crontab will not be marked as modified so if all other cronjobs are insync,

[Puppet - Bug #16121] Cron user change results in duplicate entries on target user

Issue #16121 has been updated by Chris Henry. Peter/Stefan - Is there any more information needed from me about this issue? Bug #16121: Cron user change results in duplicate entries on target user https://projects.puppetlabs.com/issues/16121#change-70782

[Puppet - Bug #16121] Cron user change results in duplicate entries on target user

Issue #16121 has been updated by Chris Henry. Stefan - Ahh thank you for the explanation. That was the difference between my original manifests and this new test one - I did have other cron jobs for the www-data user. I am now getting my original results using the 'test manifest - that is t

[Puppet - Bug #16121] Cron user change results in duplicate entries on target user

Issue #16121 has been updated by Stefan Schulte. Try adding the following to your file cron { 'no_such_cron': ensure => absent, user => 'www-data', } The problem you are hitting now is of another kind: As I said puppet will parse all targets (crontabs) and stores every record in memory.

[Puppet - Bug #16121] Cron user change results in duplicate entries on target user

Issue #16121 has been updated by Chris Henry. creating a simple manifest with the 2 cron jobs to mimic my manifest has a little different behavior. Specifically it does not re-add the root cron job over and over and over - but it still does not delete the www-data user's entry before creatin

[Puppet - Bug #16121] Cron user change results in duplicate entries on target user

Issue #16121 has been updated by Peter Meier. > the parsedfile provider parses a list of records from all known files during > prefetch (this means a record has to be unique across all files). If puppet > detects that the target property is incorrect, the target property is changed > and both

[Puppet - Bug #16121] Cron user change results in duplicate entries on target user

Issue #16121 has been updated by Stefan Schulte. Peter - the parsedfile provider parses a list of records from all known files during prefetch (this means a record has to be unique across all files). If puppet detects that the target property is incorrect, the target property is changed and

[Puppet - Bug #16121] Cron user change results in duplicate entries on target user

Issue #16121 has been updated by Peter Meier. I think you should be able to reproduce that issue with a minimal manifest and `puppet apply`, which should be sufficient to debug things. However, I think the issue is way more down in the core architecture of puppet, as each catalog has no idea

[Puppet - Bug #16121] Cron user change results in duplicate entries on target user

Issue #16121 has been updated by Chris Henry. File puppetd-issue-16121-agent_out.txt added Stefan - Thanks for getting back to me - I've run the puppet agent with verbose and debug enabled but I don't see any output relating to the exact commands puppet is using to manipulate the crontabs.