Jira (PDB-2275) (maint) Remove outdated docs
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2275 (maint) Remove outdated docs Change By: gepetto-bot 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5212) Pip package provider fails to honor HTTP proxy settings
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5212 Pip package provider fails to honor HTTP proxy settings Change By: Kylo Ginsberg Release Notes: New Feature 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5538) Puppet fails to convert Windows Unicode group or user names to sids
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5538 Puppet fails to convert Windows Unicode group or user names to sids Change By: Ethan Brown Sprint: Client Windows 2016-01-13 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5628) Functions written in Puppet language errors don't mention the file
Title: Message Title Thomas Hallgren commented on PUP-5628 Re: Functions written in Puppet language errors don't mention the file Sample output from syntax error in test function environment::min(): Error: Syntax error at 'b' at /some/environment/functions/min.pp:5:5 on node test.example.com Sample output from call to fail() Error: Evaluation Error: Error while evaluating a Function Call, oops at /some/environment/functions/min.pp:5:5 on node test.example.com 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-4744) Yumrepo doesn't recognize whitespace delimited reposdir settings in /etc/yum.conf
Title: Message Title
Kylo Ginsberg updated an issue
Puppet / PUP-4744
Yumrepo doesn't recognize whitespace delimited reposdir settings in /etc/yum.conf
Change By:
Kylo Ginsberg
The {{inifile}} provider for the Yumrepo type searches various directories when deciding where to create repository definitions. One source of directories is the {{reposdir}} setting of {{/etc/yum.conf}}. Yum allows this setting to contain a list of directories [delimited by either commas or whitespace|http://yum.baseurl.org/gitweb?p=yum.git;a=blob;f=yum/config.py;h=97e5e3d3b063294a96227a67cce43a9655cd3aa6;hb=30c993c19b8b85f44e7cec436484862ab55a6961#l171], however Puppet [only uses commas|https://github.com/puppetlabs/puppet/blob/3.8.1/lib/puppet/provider/yumrepo/inifile.rb#L77] when parsing the setting.If the {{reposdir}} setting contains a whitespace delimited list of directories, then Puppet will almost silently (a DEBUG level message is logged) fall back to creating definitions directly in {{/etc/yum.conf}}.h2. Reproduction Case* Install Puppet on a Red Hat system.* Add a {{reposdir}} setting to {{/etc/yum.conf}} which contains a whitespace-delimited list:{code:bash} echo 'reposdir=/etc/yum.conf.d /tmp' >> /etc/yum.conf{code}* Attempt to create a new repo definition.h3. OutcomeThe definition is added to {{/etc/yum.conf}} instead of a new file under {{/etc/yum. conf repos .d/}}:{noformat}# /opt/puppet/bin/puppet resource yumrepo foo ensure=present descr='foo repo'Notice: /Yumrepo[foo]/ensure: createdyumrepo { 'foo': ensure => 'present', descr => 'foo repo',}# ls /etc/yum.repos.d/foo.repols: cannot access /etc/yum.repos.d/foo.repo: No such file or directory{noformat}h3. Expected OutcomeThe definition is created under {{/etc/yum. conf repos .d/}}{noformat}# /opt/puppet/bin/puppet resource yumrepo foo ensure=present descr='foo repo'Notice: /Yumrepo[foo]/ensure: createdyumrepo { 'foo': ensure => 'present', descr => 'foo repo',}# ls /etc/yum.repos.d/foo.repo /etc/yum.repos.d/foo.repo{noformat}
Add Comment
Jira (PUP-5628) Functions written in Puppet language errors don't mention the file
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5628 Functions written in Puppet language errors don't mention the file Change By: Thomas Hallgren Assignee: Thomas Hallgren Scope Change Category: Found Scope Change Reason: Quick fix Sprint: Language Triage 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 https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (HI-487) Strict %{hiera()} interpolation
Title: Message Title
Henrik Lindberg commented on HI-487
Re: Strict %{hiera()} interpolation
Lets table the discussion about more advanced features for now...
Regarding strict and default value. Can we support specifying a default value in the (interpolation) call to hiera/lookup? Also, can we support other options supported by the lookup function (not sure exactly which ones that make sense)?
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3309) puppet master --compile should be able to source facts from master inventory service
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-3309 puppet master --compile should be able to source facts from master inventory service Change By: Henrik Lindberg Assignee: Andrew Parker 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5635) accessing facts via another scope
Title: Message Title Reinhard Vicinus commented on PUP-5635 Re: accessing facts via another scope tested with puppet version 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5635) accessing facts via another scope
Title: Message Title Henrik Lindberg commented on PUP-5635 Re: accessing facts via another scope Which version of puppet are you using? 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5628) Functions written in Puppet language errors don't mention the file
Title: Message Title Thomas Hallgren commented on PUP-5628 Re: Functions written in Puppet language errors don't mention the file PR-4529 ensures that the file name is propagated correctly from the loader to the lexer/parser. This make the output from syntax errors and calls to fail() far more readable. The function name is still not included in the output though. I hesitated adding it since it's not trivial and I'm not sure it would be that helpful. The location is precise enough and the name of the function should be the same as the name of the file. 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5635) accessing facts via another scope
Title: Message Title Henrik Lindberg assigned an issue to Reinhard Vicinus Puppet / PUP-5635 accessing facts via another scope Change By: Henrik Lindberg Assignee: Reinhard Vicinus 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5638) acceptance: lookup() and data-in-modules' should work in site clauses
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-5638 acceptance: lookup() and data-in-modules' should work in site clauses Change By: Eric Thompson Assignee: Eric Sorenson 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5638) acceptance: lookup() and data-in-modules' should work in site clauses
Title: Message Title Eric Thompson created an issue Puppet / PUP-5638 acceptance: lookup() and data-in-modules' should work in site clauses Issue Type: Task Assignee: Eric Sorenson Components: QA Created: 2015/12/28 9:26 AM Priority: Normal Reporter: Eric Thompson see related ticket and test case Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5611) Research supporting SQL 2008 on Windows 2008r2
Title: Message Title Craig Gomes commented on PUP-5611 Re: Research supporting SQL 2008 on Windows 2008r2 Requirements matrix: https://msdn.microsoft.com/en-us/library/ms143506(v=sql.105).aspx 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2275) (maint) Remove outdated docs
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2275 (maint) Remove outdated docs Change By: Russell Mull Scope Change Category: Found Scope Change Reason: Discovered by user 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2275) (maint) Remove outdated docs
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2275 (maint) Remove outdated docs Issue Type: Bug Assignee: Unassigned Created: 2015/12/28 1:37 PM Priority: Normal Reporter: gepetto-bot 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5212) Pip package provider fails to honor HTTP proxy settings
Title: Message Title
Kylo Ginsberg updated an issue
Puppet / PUP-5212
Pip package provider fails to honor HTTP proxy settings
Change By:
Kylo Ginsberg
Release Notes Summary:
The pip provider formerly did not support the {{http_proxy_host}} and {{http_proxy_port}} settings. This change adds that 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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5640) Memory access is out of bounds
Title: Message Title Craig Gomes moved an issue Puppet / PUP-5640 Memory access is out of bounds Change By: Craig Gomes Affects Version/s: puppet-agent 1.3.1 Affects Version/s: PUP 4.3.1 Workflow: Release Engineering Scrum Team Workflow Key: PA PUP - 128 5640 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
Jira (PUP-4744) Yumrepo doesn't recognize whitespace delimited reposdir settings in /etc/yum.conf
Title: Message Title Kylo Ginsberg commented on PUP-4744 Re: Yumrepo doesn't recognize whitespace delimited reposdir settings in /etc/yum.conf I just went to verify this and the outcome with this fix is different than described above. I think it's correct, but I'd like a sanity check, /cc Peter Souter or Charlie Sharpsteen. Specifically, it chooses the last, not the first, directory in the reposdir setting. I.e. given the arrangement in the description, it will create /tmp/foo.repo, not /etc/yumrepos.d/foo.repo. I think this is the appropriate thing to do, e.g. see the reasoning in the comment at https://github.com/puppetlabs/puppet/blob/4.2.2/lib/puppet/provider/yumrepo/inifile.rb#L169-L171. If it is the appropriate thing to do, we might want to flesh out the docstring at https://github.com/puppetlabs/puppet/blob/4.2.2/lib/puppet/provider/yumrepo/inifile.rb#L17-L21 to call out this case. If not, then we should discuss what the desired behavior is. 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5640) Memory access is out of bounds
Title: Message Title Ethan Brown commented on PUP-5640 Re: Memory access is out of bounds A couple of ideas for implementation approaches to fix this: Be more defensive when reading registry values so that we're not as affected by corruption - i.e. in read at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/registry.rb#L198-L229, guard the reading of values with a begin / rescue approach, and emit a warning for corrupted registry data. Take a look at the package provider code and eliminate any unnecessary registry enumeration / reading code, so that we only read the values we're interested and nothing more - see https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/windows/package.rb#L16-L49 for the current code 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5640) Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5640 Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt Change By: Ethan Brown Summary: Windows package provider can crash with " Memory access is out of bounds " when registry values are corrupt 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5639) "free" parameter $name not useable for resource collection
Title: Message Title
Reinhard Vicinus created an issue
Puppet / PUP-5639
"free" parameter $name not useable for resource collection
Issue Type:
Bug
Affects Versions:
PUP 4.2.3
Assignee:
Unassigned
Created:
2015/12/28 11:58 AM
Priority:
Normal
Reporter:
Reinhard Vicinus
The "free" parameter $name that every resource along with $title gets and that defaults to $title if nothing is set can't be used for resource collection (if the default value is used). Here an example:
when using "name" during resource collection, the parameter p doesn't get updated:
puppet apply -e 'define test ($p) { notice("$name $p") } test { "a": p => "a" } Test <| name == "a" |> { p => "aa" }'
Notice: Scope(Test[a]): a a
Jira (PUP-5628) Functions written in Puppet language errors don't mention the file
Title: Message Title Jo Rhett commented on PUP-5628 Re: Functions written in Puppet language errors don't mention the file Can you provide an example of the new output? 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5635) accessing facts via another scope
Title: Message Title Reinhard Vicinus updated an issue Puppet / PUP-5635 accessing facts via another scope Change By: Reinhard Vicinus Affects 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5640) Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt
Title: Message Title Glenn Sarti commented on PUP-5640 Re: Windows package provider can crash with "Memory access is out of bounds" when registry values are corrupt An invalid DWORD can be created manually using the steps provided in https://github.com/PoshSec/PoshSec/issues/25 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1291) Ruby 2.3.0 compatibility problem
Title: Message Title Anatol Pomozov created an issue Facter / FACT-1291 Ruby 2.3.0 compatibility problem Issue Type: Bug Assignee: Unassigned Attachments: facter-2.3.0.patch Created: 2015/12/28 4:24 PM Priority: Normal Reporter: Anatol Pomozov Ruby 2.3.0 has been released and Linux Arch tries to port the packages to it. We've found that facter/leatherman do not work with 2.3.0 because upstream ruby got removed symbol rb_data_object_alloc from *.so file and replaced it with rb_data_object_wrap. Here is a patch that resolves the facter issue and allows puppet to be built. But you probably want to make it compatible both with ruby 2.2 and 2.3. Add Comment
Jira (PDB-2276) Remove usage of robert.hooke for tk-config
Title: Message Title Russell Mull created an issue PuppetDB / PDB-2276 Remove usage of robert.hooke for tk-config Issue Type: Task Assignee: Unassigned Created: 2015/12/28 4:20 PM Priority: Normal Reporter: Russell Mull This is preventing the use of -Dclojure.compiler.direct-linking=true Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2277) (maint) Improve memory usage in benchmark tool
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2277 (maint) Improve memory usage in benchmark tool Change By: gepetto-bot 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2277) (maint) Improve memory usage in benchmark tool
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2277 (maint) Improve memory usage in benchmark tool Issue Type: Bug Assignee: Unassigned Created: 2015/12/28 5:03 PM Priority: Normal Reporter: gepetto-bot Use ActiveMQ for on-disk intermediate storage when doing a simulation-style (--runinterval) benchmark. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
