Jira (FACT-1280) Empty 'aio_agent_version' fact on AIO agent
Title: Message Title Josh Cooper assigned an issue to Antoine Cotten Facter / FACT-1280 Empty 'aio_agent_version' fact on AIO agent Change By: Josh Cooper Assignee: Antoine Cotten Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (FACT-1281) Remove host specific logic from facter acceptance setup steps
Title: Message Title Josh Cooper updated an issue Facter / FACT-1281 Remove host specific logic from facter acceptance setup steps Change By: Josh Cooper Sprint: Client Platform Additions Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (HI-486) Remove host specific logic from hiera acceptance setup steps
Title: Message Title Josh Cooper updated an issue Hiera / HI-486 Remove host specific logic from hiera acceptance setup steps Change By: Josh Cooper Sprint: Client Platform Additions Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5283) Puppet assumes if file changes, the content must be different, and prints misleading diff
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5283 Puppet assumes if file changes, the content must be different, and prints misleading diff Change By: Josh Cooper Labels: puppethack Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5595) Generated resource state is retrieved prematurely
Title: Message Title
Reid Vandewiele created an issue
Puppet / PUP-5595
Generated resource state is retrieved prematurely
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
backtrace.txt, generated_resource.png, manual_resource.png
Created:
2015/12/10 11:41 AM
Priority:
Normal
Reporter:
Reid Vandewiele
Issue discovered while working with the lwf/remote_file type/provider.
Remote_file generates a file resource to enforce owner, group and mode parameters. The following is an example use of the resource.
remote_file { 'download':
source => 'https://github.com/dimetron/vagrant_docker_dbora12c/archive/master.zip',
path=>
Jira (PUP-5063) Puppet 4 --profile is not complete compared to 3
Title: Message Title Henrik Lindberg commented on PUP-5063 Re: Puppet 4 --profile is not complete compared to 3 R.I.Pienaar Would be great if you could confirm that the PR now available gives you what was expected. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5063) Puppet 4 --profile is not complete compared to 3
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5063 Puppet 4 --profile is not complete compared to 3 Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PDB-2251) Document PE PuppetDB in the FOSS repo
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2251 Document PE PuppetDB in the FOSS repo Issue Type: Bug Affects Versions: PDB 3.2.x Assignee: Unassigned Created: 2015/12/10 11:15 AM Priority: Normal Reporter: Andrew Roetker We need to pull in the PE version of the reports-endpoint documentation, and we should document some warnings to PE customers about how much more data will be in their PostgreSQL instance, maybe in some kind of generalized 2015.3.0 (Ankeny) documentation section. Add Comment
Jira (PDB-2251) Document PE PuppetDB in the FOSS repo
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2251 Document PE PuppetDB in the FOSS repo Change By: Andrew Roetker Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PDB-2251) Document PE PuppetDB in the FOSS repo
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2251 Document PE PuppetDB in the FOSS repo Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5594) Yum provider raises exception if check-update returns unexpected exit code
Title: Message Title Reid Vandewiele created an issue Puppet / PUP-5594 Yum provider raises exception if check-update returns unexpected exit code Issue Type: Bug Assignee: Unassigned Created: 2015/12/10 8:53 AM Priority: Normal Reporter: Reid Vandewiele Installing PE 2015.2.3 on an AWS instance without internet access fails to install the console successfully. The yum package provider calls `yum check-update`, and the command returns a non-zero exit code. The package provider tries to emit a warning, but calls a private method in doing so. This causes an exception to be raised and the resource to fail. [2015-11-19 16:52:16.287 UTC] INFO Error: Could not get latest version: private method `warn' called for Puppet::Type::Package::ProviderYum:Class [2015-11-19 16:52:16.287 UTC] INFO Error: /Stage[main]/Pe_nginx/Package[pe-nginx]/ensure: change from 1.8.0-9.pe.el7 to latest failed: Could not get latest version: private method `warn' called for Puppet::Type::Package::ProviderYum:Class
Jira (PUP-5593) Update Cumulus Node config to use VM from VMpooler
Title: Message Title Josh Cooper moved an issue Puppet / PUP-5593 Update Cumulus Node config to use VM from VMpooler Change By: Josh Cooper Workflow: Release Engineering Scrum Team Workflow Key: PA PUP - 79 5593 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5123) Update HTTP links to HTTPS within code
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5123 Update HTTP links to HTTPS within code Change By: Josh Cooper Sprint: Client 2015-12-30 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (FACT-1050) can't find facts specified on CLI when defined in ini file containing spaces around =
Title: Message Title Josh Cooper commented on FACT-1050 Re: can't find facts specified on CLI when defined in ini file containing spaces around = This would be a change in https://github.com/puppetlabs/facter/blob/3.1.3/lib/src/facts/external/text_resolver.cc#L24-L33 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title William Hopper updated an issue Puppet / PUP-5549 package version behavior for epoch versioned rpm's in centos is broken. Change By: William Hopper Release Notes Summary: The change made for PUP-5025 for installing packages versions with epochs using the DNF provider caused a regression when trying to do the same using the Yum provider. This change reverts the culprit commit. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (FACT-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Sylvain Costard commented on FACT-1244 Re: xenu vs. xen0 difference not recognized by Puppet After compiling facter 3.1.4 it appears that the problem is solved in this version Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (FACT-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Sylvain Costard updated an issue Facter / FACT-1244 xenu vs. xen0 difference not recognized by Puppet Change By: Sylvain Costard Fix Version/s: FACT 3.x Fix Version/s: FACT 3.1.4 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1974) Mechanism for securing sensitive catalog data
Title: Message Title Henrik Lindberg commented on PUP-1974 Re: Mechanism for securing sensitive catalog data If this is only about preventing logging from taking place, then adding a sensitive meta parameter that when set to true prevents logging and removes resource from catalog before storing in puppet db, then that is doable without new catalog format and features related to that. "Securing Sensitive Data" is a complete epic. Should this ticket be used for "prevent logging of sensitive data"? In order to scope this we need to explore how/where logging takes place. At the moment this feels like a 5 point job (or more as it touches many parts of the system), Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5437) Explain lookup of lookup_options
Title: Message Title Thomas Hallgren commented on PUP-5437 Re: Explain lookup of lookup_options John Duarte, the lookup_options part of the example where you don't find it in hiera looks odd: lookup_options: data_module::hash_name: merge: deep data_module::hash_name: module_hash_key: hiera_value Here, the data_module::hash_name key is specified twice with different values. YAML will not merge these values. Instead, it will select the latter which means that the above is equivalent to: lookup_options: data_module::hash_name: module_hash_key: hiera_value
Jira (PUP-5595) Generated resource state is retrieved prematurely
Title: Message Title Branan Riley updated an issue Puppet / PUP-5595 Generated resource state is retrieved prematurely Change By: Branan Riley Sprint: Client 2015-12-16 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5595) Generated resource state is retrieved prematurely
Title: Message Title Branan Riley updated an issue Puppet / PUP-5595 Generated resource state is retrieved prematurely Change By: Branan Riley Scope Change Reason: Ping from CS, and easy to fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5595) Generated resource state is retrieved prematurely
Title: Message Title Branan Riley updated an issue Puppet / PUP-5595 Generated resource state is retrieved prematurely Change By: Branan Riley Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5595) Generated resource state is retrieved prematurely
Title: Message Title Branan Riley updated an issue Puppet / PUP-5595 Generated resource state is retrieved prematurely Change By: Branan Riley Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5595) Generated resource state is retrieved prematurely
Title: Message Title Branan Riley updated an issue Puppet / PUP-5595 Generated resource state is retrieved prematurely Change By: Branan Riley Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5592) hiera lookup regression in resource like class definitions with undef parameter
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5592 hiera lookup regression in resource like class definitions with undef parameter Ping Thomas Hallgren I think this could be caused by the refactored calling/parameter checks or by the changes made to data in modules. Change By: Henrik Lindberg Story Points: 1 Sprint: Language 2015-12-16 Scrum Team: Language Fix Version/s: PUP 4.3.2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5063) Puppet 4 --profile is not complete compared to 3
Title: Message Title
R.I.Pienaar commented on PUP-5063
Re: Puppet 4 --profile is not complete compared to 3
Appears that this will do what I expect yes - though I didnt run the code
For QA purposes this is what I see and how to reproduce and test that PR:
With a working 3 this does:
puppet apply -e 'notice("x")' --profile --debug
Debug: functions -> notice: 0.000207 ms (1 calls)
With a broken 4 the notice function will not be profiled, with this patch it should.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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
Jira (PUP-4125) Add migration check for upper case bare word evaluation
Title: Message Title Brian Morris commented on PUP-4125 Re: Add migration check for upper case bare word evaluation This bug bit me in the butt big time when attempting to upgrade from PE 3.8.3 to 2015.3. Geppetto never highlights any issues, and the server never gripes during compile time, but statements like this: if ( $::osfamily == Debian ) ... never resolve because the bare word is now treated as a literal instead of a string, when it has been treated as a string for many years. This causes many facters to not populate, which in turn makes many manifests fail their logic that relies on those facters. There should be some mechanism that helps us more painlessly migrate from years old Ruby-esque variables to the more strict C++ variables that come in with 2015.x. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PDB-2252) PuppetDB should not be slurping all request bodies to a string
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-2252 PuppetDB should not be slurping all request bodies to a string Issue Type: Bug Affects Versions: PDB 3.2.2 Assignee: Unassigned Created: 2015/12/10 2:43 PM Fix Versions: PDB 3.2.x Priority: Normal Reporter: Ryan Senior Currently we are always slurping the full InputStream in the body of the request into a String (see here for the code). This is being done on ALL incoming requests. This is bad for several reasons. One is with the new code that rejects payloads that are too large. If we always slurp it in, we could get a payload too large for the String of it to fit in memory. If we need to parse the JSON, it's much better to just pass in the stream. If we can avoid converting to a string entirely (i.e. transfer the data to AMQ in raw bytes) that's even better. After this is fixed, we should be able to accept arbitrarily large POST bodies and reject them properly. This should also be faster and more memory efficient.
Jira (PDB-156) Handle large catalog sizes gracefully
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-156 Handle large catalog sizes gracefully Change By: Kenneth Barber Fix Version/s: PDB 4.0.0 Fix Version/s: PDB 3.2.x Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5591) undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-5591 undefined local variable or method `data' for Puppet::Provider::Package::Windows::Package:Class Change By: Owen Rodabaugh CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PDB-2254) docs changes (on stable at least) provoke an acceptance test run
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2254 docs changes (on stable at least) provoke an acceptance test run Issue Type: Bug Assignee: Unassigned Created: 2015/12/10 4:21 PM Priority: Normal Reporter: Wyatt Alt See https://github.com/puppetlabs/puppetdb/pull/1782 Not sure when this regressed. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2254) docs changes (on stable at least) provoke an acceptance test run
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2254 docs changes (on stable at least) provoke an acceptance test run Change By: Wyatt Alt Sprint: PuppetDB 2015-12-30 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5547) Environment is evicted many times during compile
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5547 Environment is evicted many times during compile Change By: Sean Griffin QA Risk Assessment: Low QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5596) Puppet agent freezes
Title: Message Title Christopher Price commented on PUP-5596 Re: Puppet agent freezes Josh Cooper Kylo Ginsberg this came up in IRC today and sounded like it was causing a lot of pain, but I don't have any ideas. Do either of you, or do you know who might be a good SME? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5547) Environment is evicted many times during compile
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-5547 Environment is evicted many times during compile Change By: Sean Griffin Assignee: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PDB-2248) (maint) Upgrade to ActiveMQ 5.13.0
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2248 (maint) Upgrade to ActiveMQ 5.13.0 Change By: Kenneth Barber Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PDB-2212) (maint) Update docs for releasing PE
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2212 (maint) Update docs for releasing PE Change By: Kenneth Barber Scope Change Category: Found Scope Change Reason: Docs for releasing PE needed updating from last release Sprint: PuppetDB 2015-12-16 Fix Version/s: PDB 4.0.0 Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
Jira (PDB-2253) Revert "Revert "(maint) default statement cache size to 0""
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2253 Revert "Revert "(maint) default statement cache size to 0"" Issue Type: Bug Assignee: Unassigned Created: 2015/12/10 3:02 PM Priority: Normal Reporter: gepetto-bot This reverts commit 8a70a5d3416a89c45cf70c1b1c9e58f7e82ce19b. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2252) PuppetDB should not be slurping all request bodies to a string
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2252 PuppetDB should not be slurping all request bodies to a string Change By: Ryan Senior Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PDB-2253) Revert "Revert "(maint) default statement cache size to 0""
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2253 Revert "Revert "(maint) default statement cache size to 0"" Change By: Andrew Roetker Scope Change Category: Adopted Scope Change Reason: Support found a bug that we fixed but got reverted for some reason, this reverts PDB back to the fixed state Sprint: PuppetDB 2015-12-16 Fix Version/s: PDB 3.2.x This reverts commit 8a70a5d3416a89c45cf70c1b1c9e58f7e82ce19b. Revert a revert that never got properly reverted ;) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (FACT-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Kylo Ginsberg commented on FACT-1244 Re: xenu vs. xen0 difference not recognized by Puppet Hmm, that makes me a bit suspicious. Nothing has changed in facter#stable since 3.1.3 (in fact we haven't released 3.1.4, we just bump the version file in advance). Sylvain Costard can you double-check that 3.1.3 fixes the issue? (E.g. that it wasn't tested on a system that had the virt-what patch you mentioned earlier.) Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5596) Puppet agent freezes
Title: Message Title Matt Stith created an issue Puppet / PUP-5596 Puppet agent freezes Issue Type: Bug Affects Versions: PUP 3.8.4 Assignee: Kylo Ginsberg Components: Client Created: 2015/12/10 4:59 PM Environment: Ubuntu 12.04, puppetlabs ppa package Priority: Normal Reporter: Matt Stith Sometimes when I add a relationship between resources, I can no longer run puppet on agents. it freezes at "Applying configuration version...", and an strace shows it just doing "brk" constantly, slowly eating up memory. It'll sit like that forever until the system runs out of memory and OOM's the process, or I kill -9 it. This hit me today when I made this change (strace of puppet agent --test --environment=blah also attached): https://gist.github.com/stith/8dc9f788a55aaf5c1d0c I added the file resource and the "require" on line 19. Removing the "require" on line 19 lets puppet run successfully, but with the resources being applied out
Jira (PUP-5592) hiera lookup regression in resource like class definitions with undef parameter
Title: Message Title
Reinhard Vicinus updated an issue
Puppet / PUP-5592
hiera lookup regression in resource like class definitions with undef parameter
Change By:
Reinhard Vicinus
Another regression with hiera lookups if classes are defined resource like and a parameter is configured undef. With prior versions a hiera lookup happened for this parameter. With 4.3.x no lookup occurs. Short reproducer:* hiera.yaml:{code:java}---:backends: - yaml:hierarchy: - global:yaml: :datadir: "/etc/puppetlabs/code/hiera"{code}* /etc/puppetlabs/code/hiera/global.yaml:{code:java}test::p: 'hiera value'{code}* test module: /etc/puppetlabs/code/modules/test/manifests/init.pp:{code:java}class test ( $p = 'default module value',) { notice($p)}{code}with puppet 4.3.1:{code:java}puppet apply --hiera_config [..]/hiera.yaml --modulepath=/etc/puppetlabs/code/modules -e 'class { "test": p => undef }'Notice: Scope(Class[Test]): default module valueNotice: Compiled catalog for puppet4.3.1 in environment production in 0.10 seconds{code}with puppet 4.2.3:{code:java}puppet apply --hiera_config [..]/hiera.yaml --modulepath=/etc/puppetlabs/code/modules -e 'class { "test": p => undef }'Notice: Scope(Class[Test]): hiera valueNotice: Compiled catalog for puppet4.2.3 in environment production in 0.65 seconds{code}And an example were this happens in the wild is the module jfryman-nginx with the parameter migration from parameters like server_tokens from init.pp to config.pp (an example parameter is server_tokens among others) .
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5592) hiera lookup regression in resource like class definitions with undef parameter
Title: Message Title Reinhard Vicinus created an issue Puppet / PUP-5592 hiera lookup regression in resource like class definitions with undef parameter Issue Type: Bug Affects Versions: PUP 4.3.1, PUP 4.3.0 Assignee: Unassigned Created: 2015/12/10 2:45 AM Priority: Normal Reporter: Reinhard Vicinus Another regression with hiera lookups if classes are defined resource like and a parameter is configured undef. With prior versions a hiera lookup happened for this parameter. With 4.3.x no lookup occurs. Short reproducer: hiera.yaml: --- :backends:
Jira (PUP-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-3149 Removing packages on Suse should use zypper not rpm Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5594) Yum provider raises exception if check-update returns unexpected exit code
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5594 Yum provider raises exception if check-update returns unexpected exit code Change By: Josh Cooper Fix Version/s: PUP 4.2.3 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5594) Yum provider raises exception if check-update returns unexpected exit code
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5594 Yum provider raises exception if check-update returns unexpected exit code Change By: Josh Cooper Story Points: 1 Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (FACT-1050) can't find facts specified on CLI when defined in ini file containing spaces around =
Title: Message Title Josh Cooper updated an issue Facter / FACT-1050 can't find facts specified on CLI when defined in ini file containing spaces around = Change By: Josh Cooper Labels: puppethack Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title William Hopper commented on PUP-3149 Re: Removing packages on Suse should use zypper not rpm Note for functional review: this change is expected to fix puppet's package removal behavior on systems with zypper versions 1.0 and above. Earlier versions of zypper don't have automatic dependency management capabilities. So, when removing packages on our test platforms of SLES 11, 12 and OpenSUSE 11, we should expect zypper to run and automatically resolve dependencies. On SLES 10, which has zypper 0.6, we expect to fall back to the RPM provider (as before), which may or may not succeed based on the package (but should not "succeed" but silently fail to remove the package). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (FACT-1274) virtual/is_virtual does not detect docker anymore
Title: Message Title Josh Cooper commented on FACT-1274 Re: virtual/is_virtual does not detect docker anymore Maxence Dunnewind does this issue affect both ruby and native facter, or only ruby facter? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5594) Yum provider raises exception if check-update returns unexpected exit code
Title: Message Title Josh Cooper commented on PUP-5594 Re: Yum provider raises exception if check-update returns unexpected exit code The yum provider should call self.warning not self.warn. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-4744) Yumrepo doesn't recognize whitespace delimited reposdir settings in /etc/yum.conf
Title: Message Title Josh Cooper commented on PUP-4744 Re: Yumrepo doesn't recognize whitespace delimited reposdir settings in /etc/yum.conf Probably just need to change: https://github.com/puppetlabs/puppet/blob/4.3.1/lib/puppet/provider/yumrepo/inifile.rb#L77 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-4744) Yumrepo doesn't recognize whitespace delimited reposdir settings in /etc/yum.conf
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4744 Yumrepo doesn't recognize whitespace delimited reposdir settings in /etc/yum.conf Change By: Josh Cooper Labels: customer puppethack support Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-4445) Add support to TLS 1.2 connections to Puppet Forge when SSLv3 is blocked in a corporate network
Title: Message Title Josh Cooper commented on PUP-4445 Re: Add support to TLS 1.2 connections to Puppet Forge when SSLv3 is blocked in a corporate network We moved to openssl 1.0.2d in puppet-agent 1.2.4 (*nix) and puppet-agent 1.2.7 (windows). Can you confirm this issue is resolved and close if so? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5283) Puppet assumes if file changes, the content must be different, and prints misleading diff
Title: Message Title Josh Cooper commented on PUP-5283 Re: Puppet assumes if file changes, the content must be different, and prints misleading diff See https://github.com/puppetlabs/puppet/blob/4.3.1/lib/puppet/type/file/content.rb#L102-L106 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title William Hopper updated an issue Puppet / PUP-3149 Removing packages on Suse should use zypper not rpm Change By: William Hopper Release Notes Summary: Previously, when uninstalling packages on platforms which include the Zypper package manager, Puppet would always fall back to using RPM to try and do the uninstallation. As RPM is incapable of dependency management, uninstallation would fail if the package had any dependencies. This change adds an `uninstall` method to the Zypper provider for versions of Zypper 1.0 and above to properly manage dependencies and remove packages using Zypper itself. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5061) Always restore full trusted information from store
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-5061 Always restore full trusted information from store Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5437) Explain lookup of lookup_options
Title: Message Title
John Duarte commented on PUP-5437
Re: Explain lookup of lookup_options
Thank you Thomas Hallgren.
With the corrected hieradata definition, the expected merge strategy is reported.
[root@pfnwuo8brxeiu3p lookup.honTno]# puppet lookup data_module::hash_name --explain
Using merge options from "lookup_options" hash
Merge strategy deep
Data Binding "hiera"
Found key: "data_module::hash_name" value: {
"hiera_hash_key" => "hiera_class_c"
}
Data Provider "FunctionEnvDataProvider"
Found key: "data_module::hash_name" value: {
"env_hash_key" => "env_class_a"
Jira (FACT-1280) Empty 'aio_agent_version' fact on AIO agent
Title: Message Title Josh Cooper commented on FACT-1280 Re: Empty 'aio_agent_version' fact on AIO agent The aio_agent_version fact is specific to PE installations, and will be empty unless you've done a pluginsync from a PE master. In general, you'll always want to use puppetversion for both FOSS and PE: [root@tj0w4i1oqf4xss8 ~]# puppet apply -e 'notice $puppetversion' Notice: Scope(Class[main]): 4.3.1 There was a regression with puppetversion in Puppet 4.0.x, but that's been fixed in Puppet 4.1.0, see PUP-4359 . Also prior to Puppet 4.0/PE 2015.x, puppetversion would include the "Puppet Enterprise" in the version string, which is why the module you linked to is trying to regex for that. I don't think there's anything to do here. I'm reassigning it back to you as needs more information. Please close unless there's something I'm missing. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received
Jira (PUP-5593) Update Cumulus Node config to use VM from VMpooler
Title: Message Title Josh Cooper commented on PUP-5593 Re: Update Cumulus Node config to use VM from VMpooler Stan Duffy It doesn't look like beaker-hostgenerator knows about cumulus. Could you file a QENG ticket to add that, and have it block this ticket? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5595) Generated resource state is retrieved prematurely
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5595 Generated resource state is retrieved prematurely Change By: Kylo Ginsberg Fix Version/s: PUP 4.3.2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5596) Puppet agent freezes
Title: Message Title Matt Stith commented on PUP-5596 Re: Puppet agent freezes It occurs for me in 3.8.4-1puppetlabs1, which I believe is the most recent version of 3.8, and I also tried and reproduced it in 3.8.1-1puppetlabs1. Are there any other versions I should try? I'm still on 3.x everywhere. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5596) Puppet agent freezes
Title: Message Title Kylo Ginsberg commented on PUP-5596 Re: Puppet agent freezes Matt Stith are you able to see if this problem reproduces with the current puppet-agent packages? Or is there a release where you know it did not have this problem? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5596) Puppet agent freezes
Title: Message Title Kylo Ginsberg assigned an issue to Matt Stith Puppet / PUP-5596 Puppet agent freezes Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Matt Stith Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5595) Generated resource state is retrieved prematurely
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5595 Generated resource state is retrieved prematurely Change By: Kylo Ginsberg Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5595) Generated resource state is retrieved prematurely
Title: Message Title Kylo Ginsberg commented on PUP-5595 Re: Generated resource state is retrieved prematurely Branan Riley can you drop a note in for the Release Notes Summary? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (PDB-997) Add Ubuntu 14.04/trusty to acceptance testing
Title: Message Title Kenneth Barber commented on PDB-997 Re: Add Ubuntu 14.04/trusty to acceptance testing This is unblocked now, but waiting on this PR here: https://github.com/puppetlabs/puppetdb/pull/1768 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5594) Yum provider raises exception if check-update returns unexpected exit code
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5594 Yum provider raises exception if check-update returns unexpected exit code Change By: Josh Cooper Labels: puppethack Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5208) owner uid --> integer 4294967294 too big to convert to `int'
Title: Message Title
mattison ward commented on PUP-5208
Re: owner uid --> integer 4294967294 too big to convert to `int'
I have a similar issue with puppet 3.8.3 with a uid and gid > 2 million.
Error: integer 33 too big to convert to `int' Error: content: change from {md5}8ac0a40d78fb871f32a4d1bccd3a159a to{md5}
b6ee926e576bbc098e7b07963f89f0aa failed: integer 33 too big to convert to `int' Notice: Finished catalog run in 14.75 seconds $ ls -al /opt/odbc/odbc.ini
rw-r
r
-. 1 sas sas 8949 Dec 9 15:41 /opt/odbc/odbc.ini $ sudo -u sas id uid=33(sas) gid=33(sas) groups=33(sas)
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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.
