Jira (PUP-4045) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
Title: Message Title Stephen Gelman commented on PUP-4045 Re: Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket I couldn't use ignore because it only matches the filename, not the patch and the socket was a non-unique name. I worked around it locally by adding an empty "when socket" case here: https://github.com/puppetlabs/puppet/blob/3daa532/lib/puppet/file_serving/metadata.rb#L121 I don't think this is an acceptable solution long term so I am not going to PR it but i wanted to throw it out there in case it helps someone. One solution might be to change ignore to allow it to match on a path instead of just a filename. 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 (HI-346) Remove Windows platform specific gems win32console / win32-dir from Gemfile
Title: Message Title Ethan Brown updated an issue Hiera / HI-346 Remove Windows platform specific gems win32console / win32-dir from Gemfile Change By: Ethan Brown Summary: Remove Windows platform specific gems win32console / win32-dir from Gemfile is outdated 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 (HI-346) Gemfile is outdated
Title: Message Title Ethan Brown updated an issue Hiera / HI-346 Gemfile is outdated Change By: Ethan Brown Fix Version/s: HI 4.0.0 Fix Version/s: HI 3.3.z 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 (HI-346) Gemfile is outdated
Title: Message Title Ethan Brown commented on HI-346 Re: Gemfile is outdated Josh Cooper / Moses Mendoza I have put up a PR that removes all the win32 stuff from the Hiera gem. This should help pave the way for some similar cleanup work in Facter that we're going to want to do as well. 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-7451) Puppet HTTP client should respect Retry-After headers
Title: Message Title
Charlie Sharpsteen created an issue
Puppet / PUP-7451
Puppet HTTP client should respect Retry-After headers
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2017/04/17 5:19 PM
Priority:
Normal
Reporter:
Charlie Sharpsteen
If a HTTP request made through the Puppet::Network::HTTP library returns a 503 "Service Unavailable" or 429 "Too Many Requests" response code that includes a Retry-After header, then the agent should sleep for the number of seconds specified in the header and then retry the request.
This would enable Puppet Server to automatically re-splay thundering herds of agents as discussed in SERVER-1767.
Relevant HTTP standards:
The 503 (Service Unavailable) status code indicates that the server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay. The server MAY send a Retry-After header field (Section 7.1.3) to suggest an appropriate amount of time for the client to wait before retrying the request.
http://tools.ietf.org/html/rfc7231#section-6.6.4
The 429 status code indicates that the user has sent too many requests in a given amount of time ("rate limiting").
The response representations SHOULD include details explaining the condition, and MAY include a Retry-After header indicating how long to wait before making a new request.
http://tools.ietf.org/html/rfc6585#section-4
Jira (HI-569) Hiera filecache class should not store nil when an exception is thrown
Title: Message Title
Thomas Kishel created an issue
Hiera / HI-569
Hiera filecache class should not store nil when an exception is thrown
Issue Type:
Bug
Affects Versions:
HI 3.2.2
Assignee:
Unassigned
Created:
2017/04/17 5:18 PM
Priority:
Normal
Reporter:
Thomas Kishel
The error is caused by:
https://github.com/puppetlabs/hiera/blob/3.2.2/lib/hiera/backend/yaml_backend.rb#L22
Steps to reproduce:
1. Install PE 2016.4.3 with a simple hiera_include('classes') inside of node default in site.pp. 2. Configure common.yaml with classes: [] 3. Change permissions on common.yaml from 644 to 640. 4. Perform two puppet agent runs. 5. Notice the cryptic error message on the second run.
Expected behavior:
The helpful error message returned in the first agent run should always be returned.
Actual behavior:
The helpful error message is only returned once and is buried by subsequent agent reports. The cryptic error message is returned on all subsequent agent runs and makes troubleshooting extremely time consuming and costly.
Potential fix:
The filecache class should not store nil when an exception is thrown. Doing so results in the cryptic error message on all subsequent runs.
I suspect the root cause of the bug is here:
Jira (PDB-3467) possible memory leak in reports querying (maybe querying in general)
Title: Message Title
Wyatt Alt updated an issue
PuppetDB / PDB-3467
possible memory leak in reports querying (maybe querying in general)
Change By:
Wyatt Alt
Using the dataset here, which is from my install at homehttps://drive.google.com/drive/folders/0B324sr-dZ3nLfmhkaFdrT3B3ck1Cd2k2QmxISWFzdXJxcWo5S1JucS1nRlNqYzFBeHZHcTAI can cause PDB to OOM on a 256mb heap by issuing{code}curl -X GET http://localhost:8080/pdb/query/v4/reports > /dev/null{code}the dataset has about 5800 reports in it, so that should not happen. I haven't dug around to see if there are any super huge reports in there, but I doubt there's anything outside the bounds of normal.The response appears to stream out of the database, since results start coming pretty much immediately. I haven't done any digging beyond that.edit:This is on a centos 7 vm running the latest PDB promoted to PE (along with the rest of the PE services). It has 6 gigs of ram and two vcpus. The underlying system is fairly quiet. Note that 256 mb is the default heap for pe-puppetdb.
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 (PDB-3467) possible memory leak in reports querying (maybe querying in general)
Title: Message Title
Wyatt Alt updated an issue
PuppetDB / PDB-3467
possible memory leak in reports querying (maybe querying in general)
Change By:
Wyatt Alt
Using the dataset here, which is from my install at homehttps://drive.google.com/drive/folders/0B324sr-dZ3nLfmhkaFdrT3B3ck1Cd2k2QmxISWFzdXJxcWo5S1JucS1nRlNqYzFBeHZHcTAI can cause PDB to OOM on a 256mb heap by issuing{code}curl -X GET http://localhost:8080/pdb/query/v4/reports > /dev/null{code}the dataset has about 5800 reports in it, so that should not happen. I haven't dug around to see if there are any super huge reports in there, but I doubt there's anything outside the bounds of normal.The response appears to stream out of the database, since results start coming pretty much immediately. I haven't done any digging beyond that.edit:This is on a centos 7 vm running the latest PDB promoted to PE (along with the rest of the PE services) . It has 6 gigs of ram and two vcpus. The underlying system is fairly quiet.
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 (PDB-3467) possible memory leak in reports querying (maybe querying in general)
Title: Message Title
Wyatt Alt updated an issue
PuppetDB / PDB-3467
possible memory leak in reports querying (maybe querying in general)
Change By:
Wyatt Alt
Using the dataset here, which is from my install at homehttps://drive.google.com/drive/folders/0B324sr-dZ3nLfmhkaFdrT3B3ck1Cd2k2QmxISWFzdXJxcWo5S1JucS1nRlNqYzFBeHZHcTAI can cause PDB to OOM on a 256mb heap by issuing{code}curl -X GET http://localhost:8080/pdb/query/v4/reports > /dev/null{code}the dataset has about 5800 reports in it, so that should not happen. I haven't dug around to see if there are any super huge reports in there, but I doubt there's anything outside the bounds of normal.The response appears to stream out of the database, since results start coming pretty much immediately. I haven't done any digging beyond that. edit:This is on a centos 7 vm running the latest PDB promoted to PE. It has 6 gigs of ram and two vcpus. The underlying system is fairly quiet.
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 (PDB-3467) possible memory leak in reports querying (maybe querying in general)
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3467 possible memory leak in reports querying (maybe querying in general) Issue Type: Bug Assignee: Unassigned Created: 2017/04/17 4:59 PM Priority: Major Reporter: Wyatt Alt Using the dataset here, which is from my install at home https://drive.google.com/drive/folders/0B324sr-dZ3nLfmhkaFdrT3B3ck1Cd2k2QmxISWFzdXJxcWo5S1JucS1nRlNqYzFBeHZHcTA I can cause PDB to OOM on a 256mb heap by issuing curl -X GET http://localhost:8080/pdb/query/v4/reports > /dev/null the dataset has about 5800 reports in it, so that should not happen. I haven't dug around to see if there are any super huge reports in there, but I doubt there's anything outside the bounds of normal. The response appears to stream out of the database, since results start coming pretty much immediately. I haven't done any digging beyond that.
Jira (HI-346) Gemfile is outdated
Title: Message Title Ethan Brown commented on HI-346 Re: Gemfile is outdated https://github.com/puppetlabs/hiera/search?utf8=%E2%9C%93=win32= is a good search to use to find the bits for removal. win32-dir gem looks to be used only for the resolution of Dir::COMMON_APPDATA win32console can be removed because I don't think we care anymore about a 32-bit gem on Windows and colorization - no one on Windows has any compelling reason to run a dev workflow against Ruby 1.9.3 This removes the need for us to ship any Windows platform-specific gems any longer. 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-2915) Running puppet device results in Connecting with ssh to a network device requires the 'net/ssh' ruby library on both Windows and Linux
Title: Message Title Ethan Brown commented on PUP-2915 Re: Running puppet device results in Connecting with ssh to a network device requires the 'net/ssh' ruby library on both Windows and Linux There is a PR up for puppet-agent to bump the dependency at https://github.com/puppetlabs/puppet-agent/pull/1032 - still under discussion given there are other gems that require a particular version of net-ssh. 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 (FACT-1606) split the external_facts/fact_precedence tests into multiple files
Title: Message Title Eric Delaney created an issue Facter / FACT-1606 split the external_facts/fact_precedence tests into multiple files Issue Type: Task Assignee: Eric Delaney Created: 2017/04/17 4:00 PM Priority: Normal Reporter: Eric Delaney Need to split the existing 5 tests in tests/external_facts/fact_precedence.rb into 4 other tests. The 5th test is a duplicate of an already existing test which can be dropped. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3466) (maint) Run integration tests against puppetserver master branch
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3466 (maint) Run integration tests against puppetserver master branch Issue Type: Bug Assignee: Unassigned Created: 2017/04/17 3:39 PM Priority: Normal Reporter: gepetto-bot 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
Jira (PUP-7258) Ensure JSON on Agents defaults to native implementation
Title: Message Title Moses Mendoza commented on PUP-7258 Re: Ensure JSON on Agents defaults to native implementation merged to master at https://github.com/puppetlabs/puppet/commit/897972c1eac8a86287ca958d100fc041bbf8a5dc 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-7256) Ensure console pretty printing maintains pre-JSON formatting
Title: Message Title Moses Mendoza commented on PUP-7256 Re: Ensure console pretty printing maintains pre-JSON formatting merged to master at https://github.com/puppetlabs/puppet/commit/908d1491a89455ed8d2f3629da3d14e405e55bc5 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 (FACT-1578) Facter incorrectly converts integers causing negative values to be stored in PDB
Title: Message Title Josh Cooper updated an issue Facter / FACT-1578 Facter incorrectly converts integers causing negative values to be stored in PDB Change By: Josh Cooper Fix Version/s: FACT 3.6.z Fix Version/s: FACT 3.6.4 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 (FACT-1578) Facter incorrectly converts integers causing negative values to be stored in PDB
Title: Message Title Josh Cooper updated an issue Facter / FACT-1578 Facter incorrectly converts integers causing negative values to be stored in PDB Change By: Josh Cooper Fix Version/s: FACT 3.6.z 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 (PDB-3423) schema-info: don't assume there's only one index for each table/key-combination
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3423 schema-info: don't assume there's only one index for each table/key-combination Change By: Rob Browning Sprint: Hopper PuppetDB 2017-04-19 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 (PDB-3423) schema-info: don't assume there's only one index for each table/key-combination
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3423 schema-info: don't assume there's only one index for each table/key-combination Change By: Rob Browning Assignee: Rob Browning 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 (PDB-3465) PuppetDB 4.2.3.2 release (PE-only)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3465 PuppetDB 4.2.3.2 release (PE-only) Change By: Russell Mull Story Points: 1 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 (PDB-3465) PuppetDB 4.2.3.2 release (PE-only)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3465 PuppetDB 4.2.3.2 release (PE-only) Change By: Russell Mull Team: Systems Engineering 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 (PDB-3465) PuppetDB 4.2.3.2 release (PE-only)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3465 PuppetDB 4.2.3.2 release (PE-only) Change By: Russell Mull Sprint: PuppetDB 2017-04-19 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 (PDB-3465) PuppetDB 4.2.3.2 release (PE-only)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3465 PuppetDB 4.2.3.2 release (PE-only) Change By: Russell Mull Fix Version/s: PDB 4.2.3.2 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 (PDB-3465) PuppetDB 4.2.3.2 release (PE-only)
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3465 PuppetDB 4.2.3.2 release (PE-only) Issue Type: Task Assignee: Unassigned Created: 2017/04/17 1:48 PM Priority: Normal Reporter: Russell Mull 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
Jira (PDB-3323) Checking if a report exists before inserting it is SLOW
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3323 Checking if a report exists before inserting it is SLOW Change By: Russell Mull Fix Version/s: PDB 4.2.3.2 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 (PDB-2939) Don't try to store the same report twice
Title: Message Title Russell Mull commented on PDB-2939 Re: Don't try to store the same report twice Renamed this from "Investigate convergence test timeout on 2016-08-02", as this is what the solution ended up being. This will make it easier to keep track of the changes in the tagged versions. 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 (PDB-2939) Don't try to store the same report twice
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2939 Don't try to store the same report twice Change By: Russell Mull Fix Version/s: PDB 4.2.3.2 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 (PDB-2939) Don't try to store the same report twice
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2939 Don't try to store the same report twice Change By: Russell Mull Summary: Investigate convergence test timeout on 2016-08-02 Don't try to store the same report twice 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 (PDB-2939) Investigate convergence test timeout on 2016-08-02
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2939 Investigate convergence test timeout on 2016-08-02 Change By: Russell Mull Fix Version/s: PDB 4.2.3.2 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 (PDB-2939) Investigate convergence test timeout on 2016-08-02
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2939 Investigate convergence test timeout on 2016-08-02 Change By: Russell Mull Fix Version/s: PDB 4.2.3.2 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 (PDB-3440) (maint) Workaround for bundler bug in '--without group' feature
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3440 (maint) Workaround for bundler bug in '--without group' feature Change By: Russell Mull Fix Version/s: PDB 4.4.1 Fix Version/s: PDB 4.2.3.2 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 (PDB-3464) Make a deterministic version of the sync convergence test
Title: Message Title
Russell Mull updated an issue
PuppetDB / PDB-3464
Make a deterministic version of the sync convergence test
Change By:
Russell Mull
These should:{code} - Generate commands to be sent to both puppetdbs - Leverage the generators used for the command commutativity tests - Sometimes send the same command to both, sometimes not - Sometimes send the smae commands to both, but in different orders - Check that the two can sync with each other and the end - Be as reproducible as we can possibly make them- No "sleep" command like the old one- Submit each command synchronously{code}
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 (PDB-3464) Make a deterministic version of the sync convergence test
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3464 Make a deterministic version of the sync convergence test Change By: Russell Mull Sprint: Hopper 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 (PDB-3464) Make a deterministic version of the sync convergence test
Title: Message Title
Russell Mull updated an issue
PuppetDB / PDB-3464
Make a deterministic version of the sync convergence test
Change By:
Russell Mull
These should: {code} - Generate commands to be sent to both puppetdbs - Sometimes send the same command to both, sometimes not - Check that the two can sync with each other and the end - Be as reproducible as we can possibly make them- No "sleep" command like the old one- Submit each command synchronously {code}
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 (PDB-3464) Make a deterministic version of the sync convergence test
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3464 Make a deterministic version of the sync convergence test Change By: Russell Mull These should: - Generate commands to be sent to both puppetdbs - Sometimes send the same command to both, sometimes not - Check that the two can sync with each other and the end - Be as reproducible as we can possibly make them- No "sleep" command like the old one- Submit each command synchronously 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 (PDB-3464) Make a deterministic version of the sync convergence test
Title: Message Title
Russell Mull updated an issue
PuppetDB / PDB-3464
Make a deterministic version of the sync convergence test
Change By:
Russell Mull
These should:{code} - Generate commands to be sent to both puppetdbs - Leverage the generators used for the command commutativity tests - Sometimes send the same command to both, sometimes not - Check that the two can sync with each other and the end - Be as reproducible as we can possibly make them- No "sleep" command like the old one- Submit each command synchronously{code}
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 (PDB-3464) Make a deterministic version of the sync convergence test
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3464 Make a deterministic version of the sync convergence test Change By: Russell Mull These should: - Generate commands to be sent to both puppetdbs - Sometimes send the same command to both, sometimes not - Check that the two can sync with each other and the end - Be as reproducible as we can possibly make them- No "sleep" command like the old one- Submit each command synchronously 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 (PDB-3464) Make a deterministic version of the sync convergence test
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3464 Make a deterministic version of the sync convergence test Issue Type: Improvement Assignee: Unassigned Created: 2017/04/17 11:52 AM Priority: Normal Reporter: Russell Mull 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,
Jira (PUP-6560) Master puppet CI pipeline fails because gettext gem is not found
Title: Message Title John Duarte updated an issue Puppet / PUP-6560 Master puppet CI pipeline fails because gettext gem is not found Change By: John Duarte Summary: Master puppet CI pipeline fails becuase because gettext gem is not found 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 (PDB-3460) (maint) Add jdk 7 slot for integration tests in travis
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3460 (maint) Add jdk 7 slot for integration tests in travis Change By: Russell Mull Fix Version/s: PDB 4.4.1 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 (PDB-2265) puppetdb docs should push module install, over other methods
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2265 puppetdb docs should push module install, over other methods Change By: Russell Mull Fix Version/s: PDB 4.4.1 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 (PDB-3457) Fix sensitive-params test pg_dump auth
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3457 Fix sensitive-params test pg_dump auth Change By: Russell Mull Fix Version/s: PDB 4.4.1 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 (PDB-3462) (maint) Simplify synchronized-command-processing integration helper
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3462 (maint) Simplify synchronized-command-processing integration helper Change By: Russell Mull Team: Systems Engineering 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 (PDB-2583) use fewer database connections in test fixtures
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2583 use fewer database connections in test fixtures Change By: Russell Mull Fix Version/s: PDB 4.4.1 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 (PDB-3463) (docs) Fix some Markdown syntax errors
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3463 (docs) Fix some Markdown syntax errors Issue Type: Bug Assignee: Unassigned Created: 2017/04/17 11:18 AM Priority: Normal Reporter: gepetto-bot 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
Jira (PDB-3462) (maint) Simplify synchronized-command-processing integration helper
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3462 (maint) Simplify synchronized-command-processing integration helper Change By: Russell Mull Sprint: PuppetDB 2017-04-19 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 (PDB-3462) (maint) Simplify synchronized-command-processing integration helper
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3462 (maint) Simplify synchronized-command-processing integration helper Change By: Russell Mull Fix Version/s: PDB 4.4.1 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-4242) Add deprecation warnings for manifests declaring things in wrong namespace
Title: Message Title Eric Sorenson commented on PUP-4242 Re: Add deprecation warnings for manifests declaring things in wrong namespace If the deprecation didn't make it in for 4.10, this can't go in for 5.0.0, right? I believe the fixVersion should be kicked out to 5.y - Henrik Lindberg can you confirm? 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-7180) Document SSL requirements for `reporturl` option and `http` report processor
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-7180 Document SSL requirements for `reporturl` option and `http` report processor Change By: Jorie Tappa Labels: docs_reviewed maintenance Issue Type: Bug Task 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-7259) Ensure JSON is preferred serialization format in various termini/serializers
Title: Message Title Moses Mendoza commented on PUP-7259 Re: Ensure JSON is preferred serialization format in various termini/serializers passed CI https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/master/view/puppet-agent/job/platform_puppet-agent_intn-van-sys_suite-daily-pxp-agent-master/67/ 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 (PDB-3462) (maint) Simplify synchronized-command-processing integration helper
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3462 (maint) Simplify synchronized-command-processing integration helper Issue Type: Bug Assignee: Unassigned Created: 2017/04/17 9:50 AM Priority: Normal Reporter: gepetto-bot Instead of trying to track the number of expected commands, just use the existing 'wait-for-server-processing' helper. This should eliminate some intermittent race conditions caused by the previous approach. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Jeremy Barlow commented on PUP-6359 Re: Completely remove allow/deny rules from fileserver.conf syntax Josh Cooper - thanks for the additional research on this. I hadn't been aware of the code in the fileserver which hardcodes disallowing any request methods other than find or search. Are you proposing that we'd eventually remove that code as well - so that all authorization is controlled only at the auth.conf layer - or do you think the fallback denial in fileserver still has value? If we decide to issue warnings based on auth.conf rules which allow save/delete for file_content / file_metadata, we'll presumably need to do that both at the Ruby Puppet auth.conf layer and the Puppet Server / tk-auth layer. I'd prefer not to put this kind of logic directly into the tk-auth code itself - since it doesn't have any Puppet-specific knowledge in it. We could consider having some Clojure code living in Puppet Server try to parse the auth.conf rules and issue the warning although it is nice that, in today's code, code in Puppet Server doesn't have any direct responsibility for handling the auth.conf file parsing. We'd have to think through some approaches for how to do this. 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-7261) Add/Honor charset parameter in Content-Type header
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7261 Add/Honor charset parameter in Content-Type header Change By: Josh Cooper Story Points: 2 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-3552) Use application/json Content-Type/Accepts instead of PSON
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3552 Use application/json Content-Type/Accepts instead of PSON Change By: Josh Cooper Story Points: 2 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-3552) Use application/json Content-Type/Accepts instead of PSON
Title: Message Title Geoff Nichols assigned an issue to Josh Cooper Puppet / PUP-3552 Use application/json Content-Type/Accepts instead of PSON Change By: Geoff Nichols Assignee: Josh Cooper 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-7261) Add/Honor charset parameter in Content-Type header
Title: Message Title Geoff Nichols assigned an issue to Josh Cooper Puppet / PUP-7261 Add/Honor charset parameter in Content-Type header Change By: Geoff Nichols Assignee: Josh Cooper 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-6359) Completely remove allow/deny rules from fileserver.conf syntax
Title: Message Title Geoff Nichols assigned an issue to Josh Cooper Puppet / PUP-6359 Completely remove allow/deny rules from fileserver.conf syntax Change By: Geoff Nichols Assignee: Josh Cooper 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-7258) Ensure JSON on Agents defaults to native implementation
Title: Message Title Geoff Nichols assigned an issue to Moses Mendoza Puppet / PUP-7258 Ensure JSON on Agents defaults to native implementation Change By: Geoff Nichols Assignee: Josh Cooper Moses Mendoza 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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title John Duarte updated an issue Puppet / PUP-7198 Puppet Server uses facts from the previous run (n-1) after agent switches masters Change By: John Duarte QA Risk Assessment: Needs Assessment Manual 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-7258) Ensure JSON on Agents defaults to native implementation
Title: Message Title John Duarte updated an issue Puppet / PUP-7258 Ensure JSON on Agents defaults to native implementation Change By: John Duarte QA Risk Assessment: Needs Assessment Manual 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-7256) Ensure console pretty printing maintains pre-JSON formatting
Title: Message Title John Duarte updated an issue Puppet / PUP-7256 Ensure console pretty printing maintains pre-JSON formatting Change By: John Duarte QA Risk Assessment: Needs Assessment Manual 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 (PDB-3461) Update PG clients on Jenkins test machines
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3461 Update PG clients on Jenkins test machines Issue Type: Bug Assignee: Russell Mull Created: 2017/04/17 7:17 AM Priority: Normal Reporter: Ryan Senior Our tests now use pg_dump to ensure sensitive data doesn't find it's way into the database. This test is currently failing on our Jenkins instances as they have a much older version of postgres installed than the shared postgres instance that we use for testing. Once that has been upgraded, we can uncomment this test. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1605) Network Link speed fact
Title: Message Title Pat Riehecky created an issue Facter / FACT-1605 Network Link speed fact Issue Type: New Feature Assignee: Unassigned Created: 2017/04/17 6:50 AM Priority: Trivial Reporter: Pat Riehecky With the increasing deployment of 40G and greater links speeds in server environments, it would be nice if Facter could report the link speed of any detected interfaces. For high speed networks often some additional system tunings are required. For datacenter auditing, having links speed automatically captured by puppetdb et.all would help track which systems have the enhanced links. Add Comment This message was sent by Atlassian
