Jira (PUP-6609) After a Debian puppet package upgrade, parameter error persists on dashboard
Title: Message Title Stephano Zanzin commented on PUP-6609 Re: After a Debian puppet package upgrade, parameter error persists on dashboard Henrik Lindberg run manually means `puppet agent -t`. We found out that the error appears when the puppet agent runs daemon mode, so after disable the daemon mode on the nodes and leaving only the cronjob running `puppet agent -t` the issue disappears. Does that make sense? Thanks a lot for your help. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6609) After a Debian puppet package upgrade, parameter error persists on dashboard
Title: Message Title Stephano Zanzin updated an issue Puppet / PUP-6609 After a Debian puppet package upgrade, parameter error persists on dashboard Change By: Stephano Zanzin Environment: Debian Jessie ruby 2.1.9p490Puppetlabs packages: puppet-agent 1.6.0-1jessiepuppetdb 4.2.0-1puppetlabs1puppetdb-termini 4.2.0-1puppetlabs1puppetserver 2.5.0-1puppetlabs1 ruby 2.1.9p490 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6609) After a Debian puppet package upgrade, parameter error persists on dashboard
Title: Message Title Stephano Zanzin created an issue Puppet / PUP-6609 After a Debian puppet package upgrade, parameter error persists on dashboard Issue Type: Bug Assignee: Unassigned Created: 2016/08/12 2:28 AM Environment: Debian Jessie puppet-agent 1.6.0-1jessie puppetdb 4.2.0-1puppetlabs1 puppetdb-termini 4.2.0-1puppetlabs1 puppetserver 2.5.0-1puppetlabs1 ruby 2.1.9p490 Priority: Blocker Reporter: Stephano Zanzin Hi, After a Puppet upgrade on Debian Jessie using the puppetlabs repository, the error "Failed to apply catalog: no parameter named 'source'" is now being displayed for many of our nodes in the Puppet dashboard. We have a cronjob running the agent every 1 hour in each node, so the point is that when we run the puppet agent manually, the error doesn't happen. The problem is that we don't know if the issue is really happening or if it's being displayed wrongly on the dashboard. Any help is much appreciated. Thanks Add Comment
