Jira (PUP-6609) After a Debian puppet package upgrade, parameter error persists on dashboard
Title: Message Title Geoff Nichols commented on PUP-6609 Re: After a Debian puppet package upgrade, parameter error persists on dashboard Thanks for reporting this issue. However, we haven’t been able to reproduce this against the current version of Puppet, and are closing this issue now as Cannot Reproduce. If you have additional information or reproduction scenarios that may be of use, please comment in this ticket with details. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 Doug Rosser updated an issue Puppet / PUP-6609 After a Debian puppet package upgrade, parameter error persists on dashboard Change By: Doug Rosser Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 Doug Rosser commented on PUP-6609 Re: After a Debian puppet package upgrade, parameter error persists on dashboard Stephano Zanzin Were you able to reproduce the issue running the agents as daemons? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 Doug Rosser assigned an issue to Stephano Zanzin Puppet / PUP-6609 After a Debian puppet package upgrade, parameter error persists on dashboard Change By: Doug Rosser Assignee: Doug Rosser Stephano Zanzin Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 Doug Rosser assigned an issue to Doug Rosser Puppet / PUP-6609 After a Debian puppet package upgrade, parameter error persists on dashboard Change By: Doug Rosser Assignee: Doug Rosser Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 Karen Van der Veer updated an issue Puppet / PUP-6609 After a Debian puppet package upgrade, parameter error persists on dashboard Change By: Karen Van der Veer CS Priority: Needs Priority 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 Karoly Czovek commented on PUP-6609 Re: After a Debian puppet package upgrade, parameter error persists on dashboard Henrik Lindberg this is seems to a jessie/systemd incompatibility, once i killed all the old puppet agents, and restarted them on some test servers - and I could not reproduce the issue. Might be the package was failed to restart the running daemon but the underlaying files were changed. (we updated from 4.5 -> 4.6, but i guess at 4.6 the legacy sysV init scripts were translated to systemd config file in this release) The daemon now is running fine with --trace --verbose without errors on the selected test servers 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 Henrik Lindberg commented on PUP-6609 Re: After a Debian puppet package upgrade, parameter error persists on dashboard Ping Kylo Ginsberg does problem sound familiar? 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 Henrik Lindberg commented on PUP-6609 Re: After a Debian puppet package upgrade, parameter error persists on dashboard The ruby stacktrace that is logged agent side (I assume it is the agent that errors) when running as a daemon would be of great value in understanding what the cause of the problem is. Stephano Zanzin, can you try a run and dig out the stacktrace from the log on the agent? 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 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 Henrik Lindberg commented on PUP-6609 Re: After a Debian puppet package upgrade, parameter error persists on dashboard Since this is 4.6.0, it could be PUP-6608 which will cause classes to not evaluate when included in the catalog via a resource style _expression_. But it does not sound quite like that problem since it works when being "run manually" (although the ticket does not say what that means - is that a puppet apply, or applying the old catalog?). It could also be caused by a probem with create_resources that in 4.6.0, if an explicit undef is given as a value will not set that value if the parameter does not have a default value _expression_ (and if it has a default value _expression_ it will use that value (as it should)). Those are the regressions (I am aware of) in 4.6.0 that causes hard to detect root cause when puppet fails. 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 Chris Price commented on PUP-6609 Re: After a Debian puppet package upgrade, parameter error persists on dashboard Stephano Zanzin can you clarify what you mean when you say "Puppet dashboard"? Henrik Lindberg does this error sound familiar at all? 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
