Jira (PUP-6492) Reports are not stored for current node
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6492 Reports are not stored for current node Change By: Karen Van der Veer Sprint: Server Emerald 2016-07-27 , Server Emerald 2016-08-10 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-6492) Reports are not stored for current node
Title: Message Title Eric Sorenson commented on PUP-6492 Re: Reports are not stored for current node ping Julien Pivotto, can you try to answer jeremy's questions 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-6492) Reports are not stored for current node
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6492 Reports are not stored for current node Change By: Karen Van der Veer Sprint: Server Emerald 2016-07-27 , Server Emerald 2016-08-10 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-6492) Reports are not stored for current node
Title: Message Title Jeremy Barlow assigned an issue to Julien Pivotto Puppet / PUP-6492 Reports are not stored for current node Change By: Jeremy Barlow Assignee: Jeremy Barlow Julien Pivotto 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-6492) Reports are not stored for current node
Title: Message Title Kurt Wall commented on PUP-6492 Re: Reports are not stored for current node This ticket isn't a state that it can be properly analyzed for risk, so I will leave it untouched vis-â-vis QA's risk analysis. 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-6492) Reports are not stored for current node
Title: Message Title Jeremy Barlow commented on PUP-6492 Re: Reports are not stored for current node Julien Pivotto I'm not quite sure I understand your exact steps but have included some info below with some steps I attempted to reproduce the behavior you are seeing. https://docs.puppet.com/puppet/latest/reference/configuration.html#reports states: This setting is relevant to puppet master and puppet apply. This is what I've experienced as well. I haven't seen adding "--reports=store" to the "puppet apply" command line to have any practical effect. Is this not what you have seen? I did some testing with puppet-agent 1.5.2 installed on two different CentOS 7 nodes, one of which also had puppetserver 2.4.0 installed. I did some agent runs on both nodes, making requests to the node running puppetserver. The default /etc/puppetlabs/puppet/puppet.conf file after installation was used. This file doesn't define values for the "report" or "reports" settings and so would use "true" and "store", respectively, by default. When I run "puppet apply" with "--reports=store" on either of the nodes, a yaml report file for the node is written to the /opt/puppetlabs/puppet/cache/reports/ directory on the local node. When I run "puppet agent" from either of the nodes, a yaml report file for the node is written to the /opt/puppetlabs/server/data/puppetserver/reports/ directory on the node running puppetserver. This is due to the vardir setting under the [master] section of the "puppet.conf" file being set to "/opt/puppetlabs/server/data/puppetserver". Does the above not match the behavior you have been seeing? What versions of puppet-agent and puppetserver have you been using? What operating systems are you using for your agent and master/server nodes? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6492) Reports are not stored for current node
Title: Message Title Jeremy Barlow assigned an issue to Jeremy Barlow Puppet / PUP-6492 Reports are not stored for current node Change By: Jeremy Barlow Assignee: Jeremy Barlow 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-6492) Reports are not stored for current node
Title: Message Title Archana Sridhar updated an issue Puppet / PUP-6492 Reports are not stored for current node Change By: Archana Sridhar Story Points: 1 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-6492) Reports are not stored for current node
Title: Message Title Archana Sridhar updated an issue Puppet / PUP-6492 Reports are not stored for current node Change By: Archana Sridhar Sprint: Server Emerald 2016- 08 07 - 10 27 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-6492) Reports are not stored for current node
Title: Message Title Archana Sridhar updated an issue Puppet / PUP-6492 Reports are not stored for current node Change By: Archana Sridhar Sprint: Server Emerald 2016- 07 08 - 27 10 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-6492) Reports are not stored for current node
Title: Message Title Chris Price updated an issue Puppet / PUP-6492 Reports are not stored for current node Change By: Chris Price Sprint: Server Emerald 2016-07-27 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-6492) Reports are not stored for current node
Title: Message Title Chris Price updated an issue Puppet / PUP-6492 Reports are not stored for current node Change By: Chris Price Sub-team: emerald 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-6492) Reports are not stored for current node
Title: Message Title Julien Pivotto created an issue Puppet / PUP-6492 Reports are not stored for current node Issue Type: Bug Assignee: Unassigned Components: Puppet Server Created: 2016/07/12 12:57 AM Priority: Normal Reporter: Julien Pivotto In a 4 nodes environment, When Running Puppet agent --test, with report = true and reports = store in the directory /opt/puppetlabs/puppet/cache/reports I only see reports for the 3 nodes that are NOT the puppetserver On the Puppet server, the agent reports for the server host itself are not saved in /opt/puppetlabs/puppet/cache/reports Add Comment
