Jira (PDB-804) PR (134): Fixed read-database parameters in class puppetdb - tdevelioglu
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-804 PR (134): Fixed read-database parameters in class puppetdb - tdevelioglu Issue Type: Task Assignee: Unassigned Created: 06/Aug/14 1:08 AM Labels: github module Priority: Normal Reporter: gepetto-bot Fixed read-database parameters in class puppetdb Author: Company: Github ID: tdevelioglu Pull Request 134 Discussion Pull Request 134 File Diff Pull Request Description (webhooks-id: 858c4e2abb817b91ed021869b2a5e886)
Jira (PUP-3018) Puppet doesn't like to parse 'require = [ [], [] ],'
Title: Message Title
Faye Gibbins created an issue
Puppet / PUP-3018
Puppet doesn't like to parse 'require = [ [], [] ],'
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Kylo Ginsberg
Components:
Client
Created:
06/Aug/14 1:34 AM
Priority:
Major
Reporter:
Faye Gibbins
Sometimes you might want to programmatically decide upon a resources requries, viz:
someresource {'mynam': require = $flag ? { true = another_resource['name'], false = []}
, }
This works ok until you have lists on the RHS of the require line.
This works ok:
someresource {'mynam': require = [$flag_a ? { true = resource_a['name_a'], false = []},], } But this does not: someresource {'mynam': require = [ $flag_a ? { true = resource_a['name_a'], false = []}
, $flag_b ? { true = resource_b['name_b'], false = []}
, ], }
Why? When $flag_a AND $flag_b are both false this reduces to:
someresource {'mynam': require = [ [], [] ], }
And puppet does not like this.
To recap: require = [[]], is fine but require = [[],[]], is not.
Jira (FACT-627) Boolean facts not printed with facter -p if fact value is false
Title: Message Title
Martin Westergaard Lassen commented on an issue
Re: Boolean facts not printed with facter -p if fact value is false
Any chance this will make it into 1.7? We've seen this behaviour on 1.7.4.
Add Comment
Facter / FACT-627
Boolean facts not printed with facter -p if fact value is false
Boolean facts are not printed with facter -p if the fact value is false. Example (using a custom fact): {noformat} [root@cxdrun01 ~]# facter -p | grep is_cde is_cde = true [root@cxdrun01 ~]# facter -p is_cde true # fiddle the is_cde fact to be false here [root@cxdrun01 ~]# facter -p | grep is_cde is_cde = false [root@cxdrun01 ~]# facter -p i...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1583) Non ASCII comments in puppet.conf causes exception
Title: Message Title Erik Daln updated an issue Puppet / PUP-1583 Non ASCII comments in puppet.conf causes exception Change By: Erik Daln Summary: Puppetagentdoesn'tstartonserverpoweron NonASCIIcommentsinpuppet.confcausesexception Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2878) puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2
Title: Message Title Kurt Wall updated an issue Puppet / PUP-2878 puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2 Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3018) Puppet doesn't like to parse 'require = [ [], [] ],'
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3018 Puppet doesn't like to parse 'require = [ [], [] ],' Change By: Kylo Ginsberg Component/s: Client Component/s: DSL Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3018) Puppet doesn't like to parse 'require = [ [], [] ],'
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3018 Puppet doesn't like to parse 'require = [ [], [] ],' Change By: Kylo Ginsberg Assignee: KyloGinsberg AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2946) FileUtils implementation broke compare_stream
Title: Message Title
Maksym Melnychok commented on an issue
Re: FileUtils implementation broke compare_stream
Adrien Thebo i don't have windows machine to run specs, could you share spec output please?
Add Comment
Puppet / PUP-2946
FileUtils implementation broke compare_stream
{{FileUtils.compare_stream}} implementation in ruby 1.9.3 was doing something along the lines of {code:ruby} a = b = nil while something a = as.read size b = bs.read size return false if a != b end {code} {{FileUtils.compare_stream}} in 2.0 instead does this: {code:ruby} a = b = while some...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3000) Could not get fact fqdn/ipaddress
Title: Message Title Naftuli Tzvi Kay updated an issue Puppet / PUP-3000 Could not get fact fqdn/ipaddress Change By: Naftuli Tzvi Kay
Jira (PUP-3019) PMT fails to download modules with The HTTP response we received was '200 OK'
Title: Message Title Alex Dreyer created an issue Puppet / PUP-3019 PMT fails to download modules with The HTTP response we received was '200 OK' Issue Type: Bug Assignee: Unassigned Created: 06/Aug/14 9:29 AM Priority: Normal Reporter: Alex Dreyer When download a module from forge PMT fails with Error: Request to Puppet Forge failed. The server being queried was /v3/files/puppetlabs-apache-1.1.1.tar.gz The HTTP response we received was '200 OK' Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title Josh Cooper commented on an issue Re: Windows: Unable to reference packages with UTF-8 Characters in their names Puppet scans the registry to enumerate the list of installed packages. Ultimately this results in a call to ruby's built-in registry APIs, e.g. Win32::Registry::HKEY_LOCAL_MACHINE.open(..). Unfortunately ruby 1.9.x uses the ANSI versions of these APIs, see https://github.com/ruby/ruby/blob/ruby_1_9_3/ext/dl/win32/lib/win32/registry.rb#L212-L222, and it assumes that string values read from the registry only contain US-ASCII. This is ruby bug https://bugs.ruby-lang.org/issues/8943, fixed in ruby 2.1, but not earlier. Puppet attempts to work around this limitation by forcing the encoding of strings we read from the registry based on the current code page. See https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/registry.rb#L33-L45 We had a report very similar to this involving the copyright symbol with Notepad++ ( PUP-1211 ). It fixed that immediate issue on English versions of Windows, but does not appear to work correctly on Russian versions (PUP-2154). The good news is that ruby 2.1 correctly uses the wide versions of the Win32 APIs for accessing the registry, see https://github.com/ruby/ruby/blob/ruby_2_1/ext/win32/lib/win32/registry.rb#L218-L230, which was fixed in http://svn.ruby-lang.org/cgi-bin/viewvc.cgi?revision=41838view=revision. We may need to wait until we move to ruby 2.1 or look at patching ruby with this fix. Add Comment Puppet / PUP-2937 Windows: Unable to reference packages with UTF-8 Characters in their names I'm currently trying to prevent a specific package from continuing its install run on subsequent puppet apply commands. The package in Question is the Windows
Jira (PUP-3019) PMT fails to download modules with The HTTP response we received was '200 OK'
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet / PUP-3019 PMT fails to download modules with The HTTP response we received was '200 OK' Change By: Alex Dreyer Assignee: AlexDreyer Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-631) operatingsystemmajrelease does not work on Solaris
Title: Message Title William Hopper commented on an issue Re: operatingsystemmajrelease does not work on Solaris I'm not actually able to reproduce this issue in Solaris 11 with Facter 2.1.0, even with the lower case 's' in the Solaris symbol. The operatingsystemmajrelease fact resolves as expected. However, there is a large refactor in the works to structure the operatingsystem facts (currently under review), which will change how major release is resolved, and should prevent this sort of thing from happening. Add Comment Facter / FACT-631 operatingsystemmajrelease does not work on Solaris The code for operatingsystemmajrelease tries to include Solaris, but it gets the case incorrect which causes the code to never evaluate on Solaris. https://github.com/puppetlabs/facter/blob/master/lib/facter/operatingsystemmajrelease.rb This code: Facter.add(:operatingsystemmajrelease) do confine :operatingsystem = :solaris setcode do i... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this
Jira (FACT-616) operatingsystemrelease incorrectly set on CentOS 7
Title: Message Title William Hopper commented on an issue Re: operatingsystemrelease incorrectly set on CentOS 7 From GitHub: @whopper so this came about as the result of some bad logic in the packstack project where we were trying to compare operatingsystemrelease to an int. I missed that we could use operatingsystemmajrelease in this instance thus this change is no longer required. Apologies for the noise. lyarwood Add Comment Facter / FACT-616 operatingsystemrelease incorrectly set on CentOS 7 CentOS 7 now includes major, minor and release version values in /etc/redhat-release. operatingsystemrelease currently includes all three values breaking any attempts to compare numerical values etc. For example within packstack prescript profile [1]. The following PR worksaround this by returning only the major and minor versions from CentOS 7 : ht... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-743) Report retrieval JSON::ParserError due to random database disconnection
Title: Message Title Kenneth Barber commented on an issue Re: Report retrieval JSON::ParserError due to random database disconnection At first glance this seems like PDB-707 manifesting itself in a weird way. PE for some reason restarts PostgreSQL underneath PuppetDB, and sometimes we're seeing a race where some cells in the PE Platform matrix for Puppet are failing (http://jenkins-enterprise.delivery.puppetlabs.net/view/PE%20Platform/view/Puppet/job/PE%20Puppet%20Acceptance%20Tests/). Now I have setup a smaller matrix to test a fix proposal: http://jenkins-enterprise.delivery.puppetlabs.net/view/PE%20Platform/view/Puppet/job/PE%20Puppet%20Acceptance%20Tests%20(kbarber%20test)/ I've implemented a small patch that I've been testing over the last few hours/day: https://github.com/kbarber/pe-puppet/commit/dea0efe83f82b6e82d0c21df351a4674473c2c89 ... which seems to resolve the issue for at least the minor test reports/submission.rb. We haven't done many full runs with this test, but the one we did was successful. While we still need to fix PDB-707, this workaround might remove some of the frustration from the Puppet team for now. The patch is clearly marked as blaming PDB-707 for the silly curl etc. as well so we have back/forward references to the ticket. Will speak to the Puppet Core team to see if this solution is acceptable for now. Add Comment PuppetDB / PDB-743 Report retrieval JSON::ParserError due to random database disconnection We've seen this failure a number of times. Digging into the puppetdb log, I can see that PuppetDB drops a connection for an unknown reason. A couple of recent examples: * http://jenkins-enterprise.delivery.puppetlabs.net/view/PE%20Platform/view/Puppet/job/PE%20Puppet%20Acceptance%20Tests/111/label=modgud.delivery.puppetlabs.net,layout=64mcd-64a,platfo...
Jira (FACT-638) Backport commits lost in Facter-2 / Master merge
Title: Message Title William Hopper created an issue Facter / FACT-638 Backport commits lost in Facter-2 / Master merge Issue Type: Epic Assignee: Eric Sorenson Created: 06/Aug/14 10:59 AM Priority: Normal Reporter: William Hopper With the merging of the master and facter-2 branches, we lost changes from previous commits merged into master. We'll need to inventory what changes were lost and decide which we want to bring back in. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-707) The first request to PuppetDB after DB backend restart fails
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-707 The first request to PuppetDB after DB backend restart fails Change By: Kenneth Barber Sprint: 20140827to20140910 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-121) Add Ruby 2.0 to spec test matrix for puppetdb
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-121 Add Ruby 2.0 to spec test matrix for puppetdb Change By: Kenneth Barber Sprint: 20140813to 20140827 to20140910 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-638) Backport commits lost in Facter-2 / Master merge
Title: Message Title William Hopper commented on an issue Re: Backport commits lost in Facter-2 / Master merge I've got a Gdoc spreadsheet up detailing merged commits between 1.7 and 2.1 that were lost. These were found on projects.puppetlabs.com with a filter for Facter issues. Kylo Ginsberg this document is shared with you. The next step will be to dig into the commit log and find anything that wasn't ticketed that we want. Add Comment Facter / FACT-638 Backport commits lost in Facter-2 / Master merge With the merging of the master and facter-2 branches, we lost changes from previous commits merged into master. We'll need to inventory what changes were lost and decide which we want to bring back in. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDB-121) Add Ruby 2.0 to spec test matrix for puppetdb
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-121 Add Ruby 2.0 to spec test matrix for puppetdb Change By: Kenneth Barber Sprint: 20140827to20140910 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-743) Report retrieval JSON::ParserError due to random database disconnection
Title: Message Title Kenneth Barber commented on an issue Re: Report retrieval JSON::ParserError due to random database disconnection FWIW PDB-707 affects every project that uses BoneCP to talk to PostgreSQL, not just PuppetDB. Add Comment PuppetDB / PDB-743 Report retrieval JSON::ParserError due to random database disconnection We've seen this failure a number of times. Digging into the puppetdb log, I can see that PuppetDB drops a connection for an unknown reason. A couple of recent examples: * http://jenkins-enterprise.delivery.puppetlabs.net/view/PE%20Platform/view/Puppet/job/PE%20Puppet%20Acceptance%20Tests/111/label=modgud.delivery.puppetlabs.net,layout=64mcd-64a,platfo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-638) Backport commits lost in Facter-2 / Master merge
Title: Message Title William Hopper commented on an issue Re: Backport commits lost in Facter-2 / Master merge Erp, there was already a ticket for this. Closing. Add Comment Facter / FACT-638 Backport commits lost in Facter-2 / Master merge With the merging of the master and facter-2 branches, we lost changes from previous commits merged into master. We'll need to inventory what changes were lost and decide which we want to bring back in. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-618) Cherry-pick / reimplement facts on master
Title: Message Title William Hopper commented on an issue Re: Cherry-pick / reimplement facts on master I've got a Gdoc spreadsheet up detailing merged commits between 1.7 and 2.1 that were lost. These were found on projects.puppetlabs.com with a filter for Facter issues. Kylo Ginsberg this document is shared with you. The next step will be to dig into the commit log and find anything that wasn't ticketed that we want Add Comment Facter / FACT-618 Cherry-pick / reimplement facts on master In FACT-472 we decided to overwrite facter-2 onto the master branch which left a number of commits on master effectively removed. Although this was the least bad solution to the state of facter branches, it left a number of valuable contributions orphaned. The purpose of this epic is to first inventory those orphaned contributions, and then cherry-pi... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an
Jira (PDB-707) The first request to PuppetDB after DB backend restart fails
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-707 The first request to PuppetDB after DB backend restart fails Change By: Kenneth Barber Sprint: 20140827 20140813 to 20140910 20140827 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-511) Specify Resource Expression Evaluation
Title: Message Title John Duarte assigned an issue to Kurt Wall Puppet / PUP-511 Specify Resource _expression_ Evaluation Change By: John Duarte Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3020) Add setting delete and setting list add/remove functions to puppet config.
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3020 Add setting delete and setting list add/remove functions to puppet config. Change By: Joshua Partlow Assignee: AndyParker JoshuaPartlow Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3020) Add setting delete and setting list add/remove functions to puppet config.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3020 Add setting delete and setting list add/remove functions to puppet config. Change By: Joshua Partlow Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3020) Add setting delete and setting list add/remove functions to puppet config.
Title: Message Title Joshua Partlow created an issue Puppet / PUP-3020 Add setting delete and setting list add/remove functions to puppet config. Issue Type: Bug Affects Versions: 3.6.2 Assignee: Andy Parker Components: Community, Modules Created: 06/Aug/14 11:36 AM Priority: Normal Reporter: Joshua Partlow The puppet config face has facility for creating settings, but not removing or updating lists of settings. From the PR: puppet config add [name] [value] will add to a comma separated list. `puppet config add reports store` -- (adds store to the reports list) puppet config del [name] [value] will remove from a comma separated list `puppet config del reports store` -- (deletes store from the list) puppet config del [name] will remove a setting from puppet.conf `puppet config del reporturl` -- (removes reporturl from puppet.conf)
Jira (PDB-707) The first request to PuppetDB after DB backend restart fails
Title: Message Title
Kenneth Barber commented on an issue
Re: The first request to PuppetDB after DB backend restart fails
Something important to note, we're going to put in a work around for PDB-743 to mask this issue for Puppet testing: https://github.com/kbarber/pe-puppet/commit/1ca3598e6f65e92f6ebcdc449ef20e79a23cfa60
When we fix PDB-707, we will need to remove the workaround for Puppet's tests.
Add Comment
PuppetDB / PDB-707
The first request to PuppetDB after DB backend restart fails
The first request sent to PuppetDB after its backend DB has been restarted fails. Any subsequent requests are processed normally. h6. Steps to reproduce {code} service pe-postgresql restart curl -i --cacert /opt/puppet/share/puppet-dashboard/certs/pe-internal-dashboard.ca_cert.pem --cert /opt/puppet/share/puppet-dashboard/certs/pe-internal-dashboard...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PDB-167) Query for deactivated nodes
Title: Message Title Chuck Schweizer commented on an issue Re: Query for deactivated nodes This would still be a useful feature. Add Comment PuppetDB / PDB-167 Query for deactivated nodes Hello, I didn't find a way to query facts for deactivated nodes in the new V2 API (and sorry if I overlooked something). Not through the /v2/facts endpoint and not through the /v2/nodes endpoint. If I'm not mistaken, at the moment, it's only possible through /v1/facts/node. It's nice that by deafult, the V2 queries only return active nodes, but we wo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2526) puppet agent retry failed http requests
Title: Message Title Felix Frank commented on an issue Re: puppet agent retry failed http requests Speaking for myself, I find the feature intriguing, but frankly, I wouldn't want most of my agents to behave that way. The majority of my agents are on the same, reliable network, along with the master. I propose that this is a very common setup. If requests time out, there is probably a rather severe reason for that. I wouldn't want the whole network of agents to potentially contribute to the mayhem by generating more traffic than necessary. So, if Puppet adopts this behavior, I would be most grateful for the ability to turn it off through an agent setting. Can such an option be added? Add Comment Puppet / PUP-2526 puppet agent retry failed http requests It would be nice if puppet agent had the ability had the ability to retry failed http requests to the puppet master. I have multiple puppet masters sitting behind a load balancer in AWS (ELB). Whenever we update a puppet master, the node is removed from the load balancer while the update occurs. Unfortunately the AWS ELB does not allow quiescent remova... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2526) puppet agent retry failed http requests
Title: Message Title Marc Seeger commented on an issue Re: puppet agent retry failed http requests reliable network You hit number one on the list Add Comment Puppet / PUP-2526 puppet agent retry failed http requests It would be nice if puppet agent had the ability had the ability to retry failed http requests to the puppet master. I have multiple puppet masters sitting behind a load balancer in AWS (ELB). Whenever we update a puppet master, the node is removed from the load balancer while the update occurs. Unfortunately the AWS ELB does not allow quiescent remova... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2946) FileUtils implementation broke compare_stream
Title: Message Title
Adrien Thebo commented on an issue
Re: FileUtils implementation broke compare_stream
Maksym Melnychok the issue is that the change made only affected non-Windows systems (https://github.com/puppetlabs/puppet/blob/master/lib/puppet/file_system.rb#L9-L18), so if Windows was being used with Ruby 2.0 it would still use the Ruby 1.9 file implementation and thus wouldn't pick up the patched version of #compare_stream. I'm looking into the Ruby implementation to see if there is another way we can solve this issue without having to replace #compare_stream but it does look like the change made in https://github.com/ruby/ruby/commit/2142287c makes this very hard.
Add Comment
Puppet / PUP-2946
FileUtils implementation broke compare_stream
{{FileUtils.compare_stream}} implementation in ruby 1.9.3 was doing something along the lines of {code:ruby} a = b = nil while something a = as.read size b = bs.read size return false if a != b end {code} {{FileUtils.compare_stream}} in 2.0 instead does this: {code:ruby} a = b = while some...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you
Jira (PUP-3021) User resource on AIX returns a non-working structure or 'attributes'
Title: Message Title
Kylo Ginsberg commented on an issue
Re: User resource on AIX returns a non-working structure or 'attributes'
This looks like a puppet bug so I moved the ticket to PUP. It was found in PE 3.2.3.
Add Comment
Puppet / PUP-3021
User resource on AIX returns a non-working structure or 'attributes'
The `user` resource on AIX returns back non-working Puppet code for the 'attributes' key. Example: {code:title=puppet resource user root|borderStyle=solid} # puppet resource user root | tee /tmp/root.pp user { 'root': ensure = 'present', attributes = {'account_locked' = 'false', 'admin' = 'true', 'auditclasses' = 'gene...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3021) User resource on AIX returns a non-working structure or 'attributes'
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3021 User resource on AIX returns a non-working structure or 'attributes' Change By: Kylo Ginsberg Fix Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3021) User resource on AIX returns a non-working structure or 'attributes'
Title: Message Title Kylo Ginsberg moved an issue Puppet / PUP-3021 User resource on AIX returns a non-working structure or 'attributes' Change By: Kylo Ginsberg Component/s: Modules Component/s: TypesandProviders Affects Version/s: 3.2.3 Workflow: PuppetEnterprise Platform Workflow Key: ENTERPRISE PUP - 271 3021 Project: Puppet Enterprise Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3021) User resource on AIX returns a non-working structure or 'attributes'
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3021 User resource on AIX returns a non-working structure or 'attributes' Change By: Kylo Ginsberg Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2958) Rapid-fire puppet runs cause race condition with SSL data
Title: Message Title Ben Ford commented on an issue Re: Rapid-fire puppet runs cause race condition with SSL data I've also seen this in the classroom, where 15-18 students all run the simplified agent installer at about the same time. It happens infrequently, but on a regular basis. I've not had time to nail down conditions which make it repeatable. Add Comment Puppet / PUP-2958 Rapid-fire puppet runs cause race condition with SSL data It appears that two rapid-fire puppet runs can cause a race condition of some kind when: # Puppet requests a certificate from the master. # An additional puppet run is triggered immediately, before the signed certificate is received. # New private keys are generated - but the master has already received the original CSR. # The master continuously re... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-3021) User resource on AIX returns a non-working structure or 'attributes'
Title: Message Title
Rich Acosta updated an issue
Puppet / PUP-3021
User resource on AIX returns a non-working structure or 'attributes'
Change By:
Rich Acosta
The`user`resourceonAIXreturnsbacknon-workingPuppetcodeforthe'attributes'key.Example:{code:title=puppetresourceuserroot|borderStyle=solid}#puppetresourceuserroot|tee/tmp/root.ppuser{'root':ensure='present',attributes={'account_locked'='false','admin'='true','auditclasses'='general','auth1'='SYSTEM','auth2'='NONE','core'='-1','cpu'='-1','daemon'='true','data'='-1','fsize'='-1','histexpire'='0','histsize'='0','host_last_login'='njros1ud710.prudential.com','host_last_unsuccessful_login'='njros1ud710.prudential.com','login'='true','loginretries'='0','maxexpired'='-1','maxrepeats'='8','minalpha'='0','mindiff'='0','mindigit'='0','minlen'='0','minloweralpha'='0','minother'='0','minspecialchar'='0','minupperalpha'='0','name'='root','nofiles'='2000','pwdwarntime'='0','registry'='files','rlogin'='true','rss'='-1','stack'='-1','su'='true','sugroups'='ALL','system'='compat','time_last_login'='1407248916','time_last_unsuccessful_login'='1407184651','tpath'='nosak','tty_last_login'='/dev/pts/1','tty_last_unsuccessful_login'='ssh','ttys'='ALL','umask'='22','unsuccessful_login_count'='0'},comment='root',expiry='2032-12-31',gid='0',groups=['system','bin','sys','security','cron','audit','lp'],home='/',password='WuthH/s1ny/5s',password_max_age='0',password_min_age='0',shell='/bin/ksh',uid='0',}{code}Andthenrunningthesamecodethroughpuppetapply:{code:title=puppetapplyroot.pp|borderStyle=solid}#puppetapply/tmp/root.ppNotice:Compiledcatalogfor paehowpfa142 myhost . prudential example .cominenvironmentproductionin0.28secondsError:ParameterattributesfailedonUser[root]:Attributesvaluepairsmustbeseparatedbyan=at/tmp/root.pp:14Wrappedexception:Attributesvaluepairsmustbeseparatedbyan={code}Theissueseemstostemfromtheattributesfield.`puppetresource`outputsakey/valueobjectforattributes,whilepuppetapplyseemstoexpectanarraywithkey=valuepartsinitasastring.Changingittoanarrayofkey=valuepairsresultsinastillbrokensetup.Puppetresourceoutputsseveralkey/valuepairsthatareNOTitemsthatcanbechangedviathechusercommanditrunsunderthecovers.Itshouldnotreturnthe'name'orthe'system'keys.Thiswasmyworkingroot.ppfile:{code:title=root.pp}user{'root':ensure='present',attributes=['account_locked=false','admin=true','auditclasses=general','auth1=SYSTEM','auth2=NONE','core=-1','cpu=-1','daemon=true','data="" />comment='root',expiry='2032-12-31',gid='0',groups=['system','bin','sys','security','cron','audit','lp'],home='/',password=' WuthH/s1ny/5s fakepass ',password_max_age='0',password_min_age='0',shell='/bin/ksh',uid='0',}{code}PS:
Add Comment
Jira (PUP-3022) Puppet module install deletes existing files before downloading new files. If the files cannot be downloaded the data is lost
Title: Message Title Morgan Haskel moved an issue Puppet / PUP-3022 Puppet module install deletes existing files before downloading new files. If the files cannot be downloaded the data is lost Change By: Morgan Haskel Workflow: Forge Platform Workflow Key: MODULES PUP - 599 3022 Project: ForgeModules Puppet Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3022) Puppet module install deletes existing files before downloading new files. If the files cannot be downloaded the data is lost
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-3022 Puppet module install deletes existing files before downloading new files. If the files cannot be downloaded the data is lost Change By: Alex Dreyer Component/s: PMT Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-743) Report retrieval JSON::ParserError due to random database disconnection
Title: Message Title Kenneth Barber commented on an issue Re: Report retrieval JSON::ParserError due to random database disconnection Pull request for the work around is here: https://github.com/puppetlabs/pe-puppet/pull/121 Add Comment PuppetDB / PDB-743 Report retrieval JSON::ParserError due to random database disconnection We've seen this failure a number of times. Digging into the puppetdb log, I can see that PuppetDB drops a connection for an unknown reason. A couple of recent examples: * http://jenkins-enterprise.delivery.puppetlabs.net/view/PE%20Platform/view/Puppet/job/PE%20Puppet%20Acceptance%20Tests/111/label=modgud.delivery.puppetlabs.net,layout=64mcd-64a,platfo... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3023) Puppet does not respect the path setting when set in the agent section of puppet.conf
Title: Message Title Nick Walker created an issue Puppet / PUP-3023 Puppet does not respect the path setting when set in the agent section of puppet.conf Issue Type: Bug Affects Versions: 3.6.2 Assignee: Unassigned Attachments: test.tar.gz Created: 06/Aug/14 2:04 PM Labels: support customer Priority: Normal Reporter: Nick Walker When I set the path setting in the [agent] section of puppet.conf it does not seem to be respected. If I move it to the [main] section then it is respected. I'm using the attached test module which outputs the path that the agent is using during an exec statement. I've tested on both solaris 10 and centos 6.4 with the same result. Reproduction Steps using PE3.3.0: 1. Classify the node with the test module 2. View the contents of /tmp/path_test.out 3. rm /tmp/path_test.out (to make sure you know when it's been written again) 4. Edit puppet.conf on your agent
Jira (PUP-1073) Common package name in two different providers
Title: Message Title
Richard Pijnenburg commented on an issue
Re: Common package name in two different providers
Any update on this? I'm running against this issue with my Elasticsearch module.
Add Comment
Puppet / PUP-1073
Common package name in two different providers
I have a common package name, that's in two different package managers (one with yum the other with gem) package { remove-mysql: name = mysql, provider = yum, ensure = absent, } - package { gem-mysql...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2631) Running the puppet agent against a nonexistent environment produces an overly verbose error message.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2631 Running the puppet agent against a nonexistent environment produces an overly verbose error message. Change By: Kylo Ginsberg Sprint: 2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2994) puppet parser validate shouldn't puke on exported resources
Title: Message Title Brian LaMetterey updated an issue Puppet / PUP-2994 puppet parser validate shouldn't puke on exported resources Change By: Brian LaMetterey Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2946) FileUtils implementation broke compare_stream
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2946 FileUtils implementation broke compare_stream Change By: Kylo Ginsberg Sprint: 2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2994) puppet parser validate shouldn't puke on exported resources
Title: Message Title Brian LaMetterey updated an issue Puppet / PUP-2994 puppet parser validate shouldn't puke on exported resources Change By: Brian LaMetterey Sprint: 2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3001) Reintroduce dynamic scoping for resource defaults
Title: Message Title Brian LaMetterey updated an issue Puppet / PUP-3001 Reintroduce dynamic scoping for resource defaults Change By: Brian LaMetterey Sprint: 2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3021) User resource on AIX returns a non-working structure or 'attributes'
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3021 User resource on AIX returns a non-working structure or 'attributes' Change By: Kylo Ginsberg Sprint: 2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2972) Implementation of +=/-= is potentially confusing
Title: Message Title Brian LaMetterey updated an issue Puppet / PUP-2972 Implementation of +=/-= is potentially confusing Change By: Brian LaMetterey Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2804) Remove deprecation warnings introduced into Windows code during FFI
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2804 Remove deprecation warnings introduced into Windows code during FFI Change By: Josh Cooper Sprint: 2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-603) Facter acceptance should use our github mirror
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-603 Facter acceptance should use our github mirror Change By: Kylo Ginsberg Sprint: 2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2862) Validate that default value expression for param does not define variable
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2862 Validate that default value _expression_ for param does not define variable Change By: Joshua Partlow Sprint: 2014- 08 09 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2411) Remove 1.8.7 multibyte string support in Lexer2
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2411 Remove 1.8.7 multibyte string support in Lexer2 Change By: Joshua Partlow Sprint: 2014- 08 09 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-909) Speed up type inference
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-909 Speed up type inference Change By: Joshua Partlow Sprint: 2014- 08 09 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1806) Varargs support for the new function API
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-1806 Varargs support for the new function API Change By: Joshua Partlow Sprint: 2014- 08 09 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2412) Remove 1.8.7 function API support
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2412 Remove 1.8.7 function API support Change By: Joshua Partlow Sprint: 2014- 08 09 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-494) Make future parser/evaluator have acceptable performance
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-494 Make future parser/evaluator have acceptable performance Change By: Joshua Partlow Sprint: 2014- 08 09 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2906) Reimplement Collection without 3x AST
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2906 Reimplement Collection without 3x AST Change By: Joshua Partlow Sprint: 2014- 08 09 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2904) Make string/symbol use consistent i new function API
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-2904 Make string/symbol use consistent i new function API Change By: Joshua Partlow Sprint: 2014- 08 09 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3009) PMT download treats error responses as modules
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3009 PMT download treats error responses as modules Change By: Kylo Ginsberg Sprint: 2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2349) Deprecate non-string modes on file type
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2349 Deprecate non-string modes on file type Change By: Kylo Ginsberg Sprint: 2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2950) Enable rubocop:Style/AndOr
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2950 Enable rubocop:Style/AndOr Change By: Kylo Ginsberg Sprint: 2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-614) Create structured operating system fact
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-614 Create structured operating system fact Change By: Kylo Ginsberg Sprint: 2014-07-23,2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-501) Test Evaluation of ResourceExpressions
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-501 Test Evaluation of ResourceExpressions Change By: Kylo Ginsberg Sprint: 2014-07-23,2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3006) Do not allow x64 to install on Windows Server 2003
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3006 Do not allow x64 to install on Windows Server 2003 Change By: Kylo Ginsberg Sprint: 2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2281) Publish Azure VM update that use external FQDN for MCO / simplified install
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2281 Publish Azure VM update that use external FQDN for MCO / simplified install Change By: Kylo Ginsberg Sprint: Week2014-4-23to2014-4-30,Week2014-4-16to2014-4-23,Week2014-4-30to2014-5-7,Week2014-5-7to2014-5-14,2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2379) Deprecate `recurse = inf` for file type
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2379 Deprecate `recurse = inf` for file type Change By: Kylo Ginsberg Sprint: 2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2040) Allow excluding content from Puppet module tool built packages
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2040 Allow excluding content from Puppet module tool built packages Change By: Kylo Ginsberg Sprint: 2014-07-23,2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2745) Puppet 3.6.1 issue with Forge API v3
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2745 Puppet 3.6.1 issue with Forge API v3 Change By: Kylo Ginsberg Sprint: Week2014-6-25to2014-7-9,2014-07-23,2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2701) Add acceptance tests for PMT build metadata.json support
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2701 Add acceptance tests for PMT build metadata.json support Change By: Kylo Ginsberg Sprint: 2014-07-23,2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2971) install_options are not passed to yum when listing packages
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2971 install_options are not passed to yum when listing packages Change By: Kylo Ginsberg Sprint: 2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-417) Add acceptance cells which test with passenger instead of webrick.
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-417 Add acceptance cells which test with passenger instead of webrick. Change By: Kylo Ginsberg Sprint: Week2014-3-05to2014-3-12,Week2014-3-12to2014-3-19,Week2014-6-11to2014-6-18,2014-07-23,2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-511) Specify Resource Expression Evaluation
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-511 Specify Resource _expression_ Evaluation Change By: Kylo Ginsberg Sprint: 2014-07-23,2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2860) Optimize startup of puppet apply (future parser)
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2860 Optimize startup of puppet apply (future parser) Change By: Kylo Ginsberg Sprint: Week2014-6-25to2014-7-9,2014-07-23,2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2776) Adjust master acceptance/tests/environment/{static,dynamic,directory}.rb to run in PE
Title: Message Title
Kylo Ginsberg updated an issue
Puppet / PUP-2776
Adjust master acceptance/tests/environment/{static,dynamic,directory}.rb to run in PE
Change By:
Kylo Ginsberg
Sprint:
2014-07-23,2014-08-06 ,2014-08-20
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-744) Pool HTTPS connections
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-744 Pool HTTPS connections Change By: Kylo Ginsberg Sprint: Week2014-6-25to2014-7-9,2014-07-23,2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2898) Long form Resource Type reference fools future parser this is an override
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2898 Long form Resource Type reference fools future parser this is an override Change By: Kylo Ginsberg Sprint: 2014-07-23,2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2967) Remove recurse = inf
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2967 Remove recurse = inf Change By: Kylo Ginsberg Sprint: 2014-08-06 ,2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2946) FileUtils implementation broke compare_stream
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2946 FileUtils implementation broke compare_stream Change By: Kylo Ginsberg Sprint: 2014-08-20 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3023) Puppet does not respect the path setting when set in the agent section of puppet.conf
Title: Message Title
Nick Walker updated an issue
Puppet / PUP-3023
Puppet does not respect the path setting when set in the agent section of puppet.conf
Change By:
Nick Walker
WhenIsetthepathsettinginthe[agent]sectionofpuppet.confitdoesnotseemtoberespected.IfImoveittothe[main]sectionthenitisrespected.I'musingtheattachedtestmodulewhichoutputsthepaththattheagentisusingduringanexecstatement.I'vetestedonbothsolaris10andcentos6.4withthesameresult.ReproductionStepsusingPE3.3.0:1.Classifythenodewiththetestmodule2.Viewthecontentsof{{/tmp/path_test.out}}3.{{rm/tmp/path_test.out}}(tomakesureyouknowwhenit'sbeenwrittenagain)4.Editpuppet.confonyouragent-Setpathto{{/usr/bin:/usr/sbin:/tmp}}inthe[agent]section 5.{{servicepe-puppetrestart}}tocausethechangetobetakenandcauseadaemonizedruntostart6.Viewthecontentsof{{/tmp/path_test.out}}-Thecontentsshouldbethesameasintest2becausethesettingisn'trespected. 7.{{rm/tmp/path_test.out}}again8.Editpuppet.confonyouragent-Setpathto{{/usr/bin:/usr/sbin:/tmp}}inthe[main]sectionthistime 9.{{servicepe-puppetrestart}}tocausethechangetobetakenandcauseadaemonizedruntostart10.Viewthecontentsof{{/tmp/path_test.out}}-Thecontentsshouldnowbe{{/usr/bin:/usr/sbin:/tmp:/sbin}}AnotherinterestingthingtonoteisthatIgetthiswarninguponrestartofpe-puppetwhenpathissetinthe[main]sectionbutnotwhenit'sinthe[agent]sectionwhichalsomakesmethingthepathisignoredwhenit'sinthe[agent]section.{noformat}Startingpuppet:/opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/defaults.rb:182:warning:Insecureworldwritabledir/tmpinPATH,mode041777{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google
Jira (PUP-2967) Remove recurse = inf
Title: Message Title Adrien Thebo commented on an issue Re: Remove recurse = inf Merged in 5d1e87d. Add Comment Puppet / PUP-2967 Remove recurse = inf This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3023) Puppet does not respect the path setting when set in the agent section of puppet.conf
Title: Message Title Nick Walker commented on an issue Re: Puppet does not respect the path setting when set in the agent section of puppet.conf If this is confirmed as an issue by engineering in the short term it'd be great to update the documentation on this page to say it only works in the [agent] section. https://docs.puppetlabs.com/references/latest/configuration.html#path Add Comment Puppet / PUP-3023 Puppet does not respect the path setting when set in the agent section of puppet.conf When I set the path setting in the [agent] section of puppet.conf it does not seem to be respected. If I move it to the [main] section then it is respected. I'm using the attached test module which outputs the path that the agent is using during an exec statement. I've tested on both solaris 10 and centos 6.4 with the same result. Reproduc... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
Jira (PUP-3006) Do not allow x64 to install on Windows Server 2003
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-3006 Do not allow x64 to install on Windows Server 2003 Change By: Rob Reynolds Assignee: JoshCooper RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3006) Do not allow x64 to install on Windows Server 2003
Title: Message Title Rob Reynolds assigned an issue to Josh Cooper Puppet / PUP-3006 Do not allow x64 to install on Windows Server 2003 Change By: Rob Reynolds Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3023) Puppet does not respect the path setting when set in the agent section of puppet.conf
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3023 Puppet does not respect the path setting when set in the agent section of puppet.conf Change By: Joshua Partlow Affects Version/s: 3.7.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3023) Puppet does not respect the path setting when set in the agent section of puppet.conf
Title: Message Title Joshua Partlow commented on an issue Re: Puppet does not respect the path setting when set in the agent section of puppet.conf Or rather that it only works in the main section I think. I'm seeing the same behavior in master. Looking into it a bit further to see what's going on, but I think everything path does, it does in it's :hook proc (which re-writes ruby's ENV[PATH]...which seems frightening), and perhaps this hook is not being called for :path in the agent section. Not sure yet why that would be. Add Comment Puppet / PUP-3023 Puppet does not respect the path setting when set in the agent section of puppet.conf When I set the path setting in the [agent] section of puppet.conf it does not seem to be respected. If I move it to the [main] section then it is respected. I'm using the attached test module which outputs the path that the agent is using during an exec statement. I've tested on both solaris 10 and centos 6.4 with the same result. Reproduc... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from
Jira (PUP-3006) Do not allow x64 to install on Windows Server 2003
Title: Message Title
Josh Cooper commented on an issue
Re: Do not allow x64 to install on Windows Server 2003
Merged into puppet_for_the_win in 101e07446a
Add Comment
Puppet / PUP-3006
Do not allow x64 to install on Windows Server 2003
Our compiled version of ruby 2.0 on Windows x64 depends on a version of msvcrt that contains _gmtime64_s and _localtime64_s, which are security enhanced versions of _gmtime64 and _localtime64. On 2003 (with msvcrt version 7.0.3790.3959), these functions are not available. As a result trying to execute {{ruby --version}} on 2003 will fail. This issue be...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3006) Do not allow x64 to install on Windows Server 2003
Title: Message Title
Josh Cooper commented on an issue
Re: Do not allow x64 to install on Windows Server 2003
To verify, grab a puppet x64 MSI, and try to install on 2003 (x64). It should fail like https://github.com/puppetlabs/puppet_for_the_win/pull/72#issuecomment-51404794
Add Comment
Puppet / PUP-3006
Do not allow x64 to install on Windows Server 2003
Our compiled version of ruby 2.0 on Windows x64 depends on a version of msvcrt that contains _gmtime64_s and _localtime64_s, which are security enhanced versions of _gmtime64 and _localtime64. On 2003 (with msvcrt version 7.0.3790.3959), these functions are not available. As a result trying to execute {{ruby --version}} on 2003 will fail. This issue be...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-3006) Do not allow x64 to install on Windows Server 2003
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3006 Do not allow x64 to install on Windows Server 2003 Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3006) Do not allow x64 to install on Windows Server 2003
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3006 Do not allow x64 to install on Windows Server 2003 Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3008) Already initialized constant warning when running puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3008 Already initialized constant warning when running puppet Change By: Josh Cooper Summary: Uninitialized Alreadyinitialized constantwarningwhenrunningpuppet Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3024) yumrepo: add setting deltarpm_percentage
Title: Message Title Stefan Neufeind created an issue Puppet / PUP-3024 yumrepo: add setting deltarpm_percentage Issue Type: Improvement Assignee: Unassigned Created: 06/Aug/14 5:44 PM Priority: Normal Reporter: Stefan Neufeind Allow yumrepo to also take care of the setting deltarpm_percentage. It will allow to adjust or even disable the use of deltarpms. In case a local mirror is used it's often easier/faster to just download the full rpm instead of rebuilding it from deltarpms on several machines. https://bugzilla.redhat.com/show_bug.cgi?id=1050728 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-96) Deprecate 'facter --puppet'
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-96 Deprecate 'facter --puppet' Change By: Kylo Ginsberg Fix Version/s: 2.2.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-96) Deprecate 'facter --puppet'
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-96 Deprecate 'facter --puppet' Change By: Kylo Ginsberg Fix Version/s: 2.3.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-150) Facter timeouts reap all subprocesses thus confusing Puppet
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-150 Facter timeouts reap all subprocesses thus confusing Puppet Change By: Kylo Ginsberg Fix Version/s: 2.2.0 Fix Version/s: 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-150) Facter timeouts reap all subprocesses thus confusing Puppet
Title: Message Title Kylo Ginsberg commented on an issue Re: Facter timeouts reap all subprocesses thus confusing Puppet Actually targeting at 3.0. It will be fixed by nature of the facter 3 implementation. Add Comment Facter / FACT-150 Facter timeouts reap all subprocesses thus confusing Puppet It is no longer possible to have puppet install packages via yum/rpm if the network interface is not bound to an IP address. Our use case requires using puppet in the non-daemon mode and this is possible for us because the system will have all necessary manifests and other necessary files locally. This worked just fine with 0.24.6 on Fedora 10, but bega... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-410) Add deprecation warnings for Facter 2.x
Title: Message Title Kylo Ginsberg commented on an issue Re: Add deprecation warnings for Facter 2.x Okay I'm going to close this as won't fix. For facter 3 we'll document what extension points custom facts can use. Add Comment Facter / FACT-410 Add deprecation warnings for Facter 2.x In Facter 2.0.1 a number of soft deprecations were added because existing behavior was undesired, but they were so heavily used that deprecating everything right away would spew tons of noise. In Facter 2.1 we should start adding deprecation notices to those methods. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3000) Could not get fact fqdn/ipaddress
Title: Message Title Naftuli Tzvi Kay commented on an issue Re: Could not get fact fqdn/ipaddress I believe that I've found the source of the bug via help of a friend. Evidently, PATH is not being carried over properly by the Puppet Master when it runs in - rack mode. It works in WEBrick, but not in Passenger/ -rack mode. Basically, there is a bug. As a workaround, you can currently either define `--path` in config.ru or define `path=...` in /etc/puppet/puppet.conf. Add Comment Puppet / PUP-3000 Could not get fact fqdn/ipaddress I have a weird issue where the Puppet Master is generating a certificate called .mydomain.com (ie: .$domain). Looking into the logs, I see the following: Aug 1 00:01:14 kungfumaster puppet-master[447]: Could not retrieve fact fqdn Aug 1 00:01:14 kungfumaster puppet-master[447]: Could not retrieve fact ipaddress In the codebase it's locate... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) --
