Jira (PDB-4192) Figure out a different way to detect when puppetserver is up (Docker)
Title: Message Title Nate Wolfe assigned an issue to Nate Wolfe PuppetDB / PDB-4192 Figure out a different way to detect when puppetserver is up (Docker) Change By: Nate Wolfe Assignee: Nate Wolfe Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-6257) Add --allow-authorization-extensions to puppet cert sign
Title: Message Title Nate Wolfe commented on PUP-6257 Re: Add --allow-authorization-extensions to puppet cert sign I think the code paths converge by then, yes. I believe the two exist because one of them implements the "faces" API (or whatever the abstraction was called), so most of their differences are at the API level. Hopefully. 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-6257) Add --allow-authorization-extensions to puppet cert sign
Title: Message Title Nate Wolfe commented on PUP-6257 Re: Add --allow-authorization-extensions to puppet cert sign It does only if you specify --ca-location remote 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-5052) Gatling: Add gatling-jenkins plugin for graphing
Title: Message Title Nate Wolfe commented on PUP-5052 Re: Gatling: Add gatling-jenkins plugin for graphing Maybe you could comment on how the puppet-gatling-jenkins plugin extends the gatling plugin, I'm confused about the difference, since it sounds like the gatling does what we want (historical data across builds) Joe Pinsonault If I remember correctly, the primary thing that our extension does it change it to graph agent runs rather than HTTP requests. Obviously, gatling has no idea that a set of requests comprise an agent run, so it just graphs the requests over time. Our plugin instead aggregates the requests that make up an agent run, and graphs the aggregate value. That way, we could graph 3.x agent runs alongside 4.x agent runs (i.e. same graph) and we can compare them. If the graph was just HTTP requests, we wouldn't be able to compare the agent runs because we can't see them, and (for example) the trend of the catalog request wouldn't differentiate between 3.x requests and 4.x requests. My hunch is that we'll need our plugin to work in order for us to view the results meaningfully. Christopher Price did I get that right? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5052) Gatling: Add gatling-jenkins plugin for graphing
Title: Message Title Nate Wolfe commented on PUP-5052 Re: Gatling: Add gatling-jenkins plugin for graphing My hunch is that we'll need our plugin to work in order for us to view the results meaningfully. I take that back. If we're not going to do multiple agents in the same run, then I think we could live with the HTTP requests graph since we would know that they're all from the same simulation. We'd have to do the math ourselves if we wanted aggregate numbers, but in terms of technical necessity we might be able to use the standard plugin for the purposes of our one-off OPS job. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5052) Gatling: Add gatling-jenkins plugin for graphing
Title: Message Title Nate Wolfe created an issue Puppet / PUP-5052 Gatling: Add gatling-jenkins plugin for graphing Issue Type: Task Assignee: Unassigned Created: 2015/08/19 4:43 PM Priority: Normal Reporter: Nate Wolfe Add the gatling-jenkins plugin so we can get some basic trend visualization. Joe Pinsonault has already started working with this plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-5012) Add feature flag to disable authconfig
Title: Message Title Nate Wolfe assigned an issue to Nate Wolfe Puppet / PUP-5012 Add feature flag to disable authconfig Change By: Nate Wolfe Assignee: NateWolfe Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5012) Add feature flag to disable authconfig
Title: Message Title Nate Wolfe updated an issue Puppet / PUP-5012 Add feature flag to disable authconfig Change By: Nate Wolfe Sprint: ServerEmerald2015-08-19 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5012) Add feature flag to disable authconfig
Title: Message Title Nate Wolfe updated an issue Puppet / PUP-5012 Add feature flag to disable authconfig Change By: Nate Wolfe Scope Change Category: Adopted Scope Change Reason: Bandwidthallowed Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3812) Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type
Title: Message Title Nate Wolfe commented on PUP-3812 Re: Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type Josh Cooper Yeah, I chose Cannot Reproduce because I literally couldn't reproduce it since this behavior is still supported (i.e. this wasn't the bug I thought I was encountering). You're right though, this makes more sense as Fixed or Done, and we shouldn't have re-opened it but instead created a new ticket. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3812) Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type
Title: Message Title Nate Wolfe assigned an issue to Unassigned Puppet / PUP-3812 Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type Change By: Nate Wolfe Assignee: NateWolfe Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3812) Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type
Title: Message Title
Nate Wolfe commented on PUP-3812
Re: Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type
Erik Dasher I cannot reproduce this either. I tried a slimmed-down minimal manifest with the file under question but had no problems backing it up during an agent run.
It was definitely an error when I encountered this in the wild as the file was not backed up or modified with the new contents.
For reference, I was using the following module when the error occurred: https://forge.puppetlabs.com/nwolfe/simmons v0.1.0
...which has the following resource that generated the regression-binary-blob (which was named source-file during the agent run) file:
exec { 'change-source-file':
command = bash -c 'dd if=/dev/urandom bs=512 count=1 ${studio}/source-file',
}
As you can see, the contents are random, so I happened to get (un)lucky during that particular agent run.
I'm going to re-Close this since we're not able to reproduce.
Add Comment
This message was sent by Atlassian JIRA
Jira (PUP-3812) Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type
Title: Message Title
Nate Wolfe updated an issue
Puppet / PUP-3812
Modify file_bucket_file API to use application/octet-stream instead of text/plain for Content-Type
(http://builds.puppetlabs.lan/puppetserver/2.1.0.SNAPSHOT.2015.04.17T0057/ on a RHEL 7 VM)
While playing around with randomly generated binary blobs and backing them up via file_bucket, I encountered the following error:
Error: invalid byte sequence in UTF-8
Error: /Stage[main]/Simmons::Exercise/File[regression-binary-blob]/content: change from {md5}2481e1b1eff9d1c557f2cd32c8e7d059 to {md5}0ad6dbf346ac04c8669f75976024accc failed: invalid byte sequence in UTF-8
After chatting with Erik Dasher about this, we're thinking this might be a regression. I've attached the binary blob file named regression-binary-blob.
Change By:
Nate Wolfe
Attachment:
regression-binary-blob
Add Comment
Jira (PUP-3944) Make sure puppetdb.conf is under $confdir
Title: Message Title Nate Wolfe commented on PUP-3944 Re: Make sure puppetdb.conf is under $confdir Eric Thompson The title is misleading, but I created it while making sure other things were under $confdir. Turns out puppetdb.conf is not something that we have code for installing under $confdir - that's an exercise left to the reader . I didn't know it at the time of creating this ticket, but once we/I came back around to this and realized this was the case, there was nothing to do for this ticket. I believe the comments regarding failing tests were just a red-herring while this ticket was Open but before we realized it was a NOOP. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4420) Executable external facts broken in 4.0.0: not executable on agent
Title: Message Title Nate Wolfe created an issue Puppet / PUP-4420 Executable external facts broken in 4.0.0: not executable on agent Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Unassigned Components: Platform Created: 2015/04/15 6:11 PM Fix Versions: PUP 4.0.1 Priority: Normal Reporter: Nate Wolfe While investigating 3.x-4.x compatibility for SERVER-526 I tried to use an executable external fact, but this did not work in 4.0.0 (it worked in 3.7.5). The file is no longer executable on the agent side, so the agent run spits out a warning saying the fact file was parsed but returned an empty data set. When looking at the HTTP traffic for my executable external fact file, I see the file_metadata response does in fact specify a different mode between 3.7.5 and 4.0.0. Below you'll
Jira (PUP-4420) Executable external facts broken in 4.0.0: not executable on agent
Title: Message Title Nate Wolfe commented on PUP-4420 Re: Executable external facts broken in 4.0.0: not executable on agent Ping Josh Cooper Kylo Ginsberg just because I talked to you guys about this in person. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4073) Child directories don't follow parent directories
Title: Message Title Nate Wolfe created an issue Puppet / PUP-4073 Child directories don't follow parent directories Issue Type: Bug Assignee: Kylo Ginsberg Components: Client Created: 2015/03/03 11:24 AM Labels: AIO Priority: Normal Reporter: Nate Wolfe There are several directories that are rooted under a parent directory, such as the $rundir and $logdir being under $vardir. If you do not rely on the default location of $vardir and specify it explicitly, the children directories do not move with it. For example: $ puppet master --configprint vardir /Users/nwolfe/.puppet/var
Jira (PUP-4073) Child directories don't follow parent directories
Title: Message Title
Nate Wolfe updated an issue
Puppet / PUP-4073
Child directories don't follow parent directories
Change By:
Nate Wolfe
Thereareseveraldirectoriesthatarerootedunderaparentdirectory,suchasthe$rundirand$logdirbeingunder$vardir.Ifyoudonotrelyonthedefaultlocationof$vardirandspecifyitexplicitly,thechildrendirectoriesdonotmovewithit.Forexample:{code:bash}$puppetmaster--configprintvardir/Users/nwolfe/.puppet/var$puppetmaster--configprintrundir/Users/nwolfe/.puppet/var/run$puppetmaster--configprintrundir--vardir=/tmp/Users/nwolfe/.puppet/var/run{code}Iwouldexpecttheoutputtobe:{code:bash}$puppetmaster--configprintrundir--vardir=/tmp/tmp/run{code}Notethatthisbehaviormightbedifferentbetweenrootandnon-root.Thisticketisconcernedwiththenon-rootcase,whichiswhatisusedbyPuppetServerwhenloadingthePuppetrubycodeintoJRuby.IbelievethatintheearlydaysofAIOthisbehaviorwassupported,buttheimplementationintroducedsomesortofcyclicaldependencybetweenvariousclasses/modules , ( specificallythe{{run_mode.rb}}and{{defaults.rb}}ifIremembercorrectly ),sothiswasundone .
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3944) Make sure puppetdb.conf is under $confdir
Title: Message Title Nate Wolfe created an issue Puppet / PUP-3944 Make sure puppetdb.conf is under $confdir Issue Type: Sub-task Assignee: Unassigned Created: 2015/02/02 1:35 PM Priority: Normal Reporter: Nate Wolfe We should make sure that this file is in the proper default location based on the AIO/code-vs-config directory separations. It should be under the $confdir, and is very possible that no changes are necessary but we should still double-check. This is set somewhere in puppetdb. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3943) Make sure console.conf is under $confdir
Title: Message Title Nate Wolfe created an issue Puppet / PUP-3943 Make sure console.conf is under $confdir Issue Type: Sub-task Assignee: Unassigned Created: 2015/02/02 1:35 PM Priority: Normal Reporter: Nate Wolfe We should make sure that this file is in the proper default location based on the AIO/code-vs-config directory separations. It should be under the $confdir, and is very possible that no changes are necessary but we should still double-check. I think this is set somewhere in pe-console-services. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3942) Make sure classifier.yaml is under $confdir
Title: Message Title Nate Wolfe created an issue Puppet / PUP-3942 Make sure classifier.yaml is under $confdir Issue Type: Sub-task Assignee: Unassigned Created: 2015/02/02 1:34 PM Priority: Normal Reporter: Nate Wolfe We should make sure that this file is in the proper default location based on the AIO/code-vs-config directory separations. It should be under the $confdir, and is very possible that no changes are necessary but we should still double-check. I think this is set somewhere in pe-console-services. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3942) Make sure classifier.yaml is under $confdir
Title: Message Title Nate Wolfe commented on PUP-3942 Re: Make sure classifier.yaml is under $confdir Patrick Carlisle Not sure where to look for this path definition. Any ideas? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3944) Make sure puppetdb.conf is under $confdir
Title: Message Title Nate Wolfe commented on PUP-3944 Re: Make sure puppetdb.conf is under $confdir Kenneth Barber Not sure where this path is defined in PuppetDB. Any ideas? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3943) Make sure console.conf is under $confdir
Title: Message Title Nate Wolfe commented on PUP-3943 Re: Make sure console.conf is under $confdir Patrick Carlisle Not sure where to look for this path definition. Any ideas? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3926) Move hieradata directory under $codedir
Title: Message Title Nate Wolfe created an issue Puppet / PUP-3926 Move hieradata directory under $codedir Issue Type: Task Assignee: Unassigned Created: 2015/01/29 2:13 PM Priority: Normal Reporter: Nate Wolfe Modify the default for the hieradata directory to point at $codedir/hieradata. Creating this as a separate ticket since the code changes aren't in Puppet. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3926) Move hieradata directory under $codedir
Title: Message Title Nate Wolfe commented on PUP-3926 Re: Move hieradata directory under $codedir This was done in HI-298 - see the PR at https://github.com/puppetlabs/hiera/pull/232 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3926) Move hieradata directory under $codedir
Title: Message Title Nate Wolfe updated an issue Puppet / PUP-3926 Move hieradata directory under $codedir Change By: Nate Wolfe Issue Type: Task Sub-task Parent: PUP-3809 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3526) re-structure CA REST API
Title: Message Title Nate Wolfe assigned an issue to Unassigned Puppet / PUP-3526 re-structure CA REST API Change By: Nate Wolfe Assignee: NateWolfe Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3520) Move the Puppet extension OIDs definitions
Title: Message Title Nate Wolfe assigned an issue to Nate Wolfe Puppet / PUP-3520 Move the Puppet extension OIDs definitions Change By: Nate Wolfe Assignee: NateWolfe Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3520) Move the Puppet extension OIDs definitions
Title: Message Title Nate Wolfe updated an issue Puppet / PUP-3520 Move the Puppet extension OIDs definitions Change By: Nate Wolfe Sprint: SERVER nextcandidates 2014-11-19 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-283) Improve agent error reporting
Title: Message Title Nate Wolfe commented on an issue Re: Improve agent error reporting Daniel Dreier Oops, I think you got the wrong ticket Add Comment Puppet / PUP-283 Improve agent error reporting When a Puppet run fails for whatever reason (catalog compilation failure/timeout, etc..), it would be nice to have this cause of failure be available as a field in the submitted report. If this was available then one would be able to introspect on it to see the reason for a failed Puppet run, without having to parse the logs field and perform some regex ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
