Jira (PUP-1931) mount provider improvement when options property is not specified
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-1931 mount provider improvement when options property is not specified Change By: Kenn Hussey Sprint: RE2015-04-08,RE2015-04-22 ,RE2015-05-06 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilati
Title: Message Title Gary Larizza commented on PDB-949 Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilation. Adding another comment echoing what Ben Ford said about seeing this in class when there's a time skew between the master and agent. It's an issue because the fix (syncing clocks) doesn't match the seemingly cryptic error message that's raised, and it's confusing. Don't know if that's a separate ticket or not. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4447) error message when using $name/$title variables could be more expressive
Title: Message Title Thomas Hallgren commented on PUP-4447 Re: error message when using $name/$title variables could be more expressive Merged to master at 9e3c493 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4447) error message when using $name/$title variables could be more expressive
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-4447 error message when using $name/$title variables could be more expressive Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2080) Support functions written in pp
Title: Message Title Thomas Hallgren commented on PUP-2080 Re: Support functions written in pp Merged to master at 4a37ee2 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3686) exec type ignores schedule on refresh
Title: Message Title Ian commented on PUP-3686 Re: exec type ignores schedule on refresh Any thoughts on a workaround for this until such time as the issue is resolved? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1419) PR (176): Enable the module to manage entries in $confdir/config.ini - buzzdeee
Title: Message Title gepetto-bot commented on PDB-1419 Re: PR (176): Enable the module to manage entries in $confdir/config.ini - buzzdeee Pull request Enable the module to manage entries in $confdir/config.ini has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4447) error message when using $name/$title variables could be more expressive
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4447 error message when using $name/$title variables could be more expressive Too complex to fix on 3.x because errors come from multiple places, and spec tests are completely restructured for compiler/parser. Changing this to only target 4.1.0 Change By: Henrik Lindberg Fix Version/s: PUP3.8.1 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4450 Cannot load 'provider/network_route/routes.rb' Change By: Henrik Lindberg Summary: EvaluationError:ErrorwhileevaluatingaVirtualQuery Cannotload'provider/network_route/routes.rb' Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title Henrik Lindberg commented on PUP-4450 Re: Cannot load 'provider/network_route/routes.rb' The significant part is this: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Virtual Query, Could not autoload puppet/type/network_route: Could not autoload puppet/provider/network_route/routes: no such file to load -- puppetx/filemapper at /var/puppet/environments/production/modules/dec/manifests/profiles/soe_network.pp:25:43 on node host.domain.com i.e soe_network.pp causes /var/puppet/environments/production/modules/network/lib/puppet/provider/network_route/routes.rb:2:in `(root)' to attempt to load the puppetx/filemapper, and this fails. Christopher Price Does this seem familiar? Any hints? My first suspicion is the use of puppetx as opposed to puppet_x. Alex Jurkiewicz, can you check the name/path of the filemapper.rb file that it expects to load? Is it under puppetx, or puppet_x, and is it called filemapper.rb or file_mapper.rb ? Add Comment
Jira (PUP-4449) When running a puppet manifest, if disk is full, give an error message indicating the disk is full.
Title: Message Title Henrik Lindberg commented on PUP-4449 Re: When running a puppet manifest, if disk is full, give an error message indicating the disk is full. This is similar to PUP-4442, as it is also about issues with checking errors of an Dir.mkdir. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4449) When running a puppet manifest, if disk is full, give an error message indicating the disk is full.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4449 When running a puppet manifest, if disk is full, give an error message indicating the disk is full. Change By: Henrik Lindberg Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4445) Add support to TLS 1.2 connections to Puppet Forge when SSLv3 is blocked in a corporate network
Title: Message Title Louis Mayorga commented on PUP-4445 Re: Add support to TLS 1.2 connections to Puppet Forge when SSLv3 is blocked in a corporate network The certificate is installed already and it works when I am not connected to my corporate network but it fails when i am connected to it. So basically SSLv3 is blocked at the network level. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4436) With a gem install of puppet, when run as root, 'puppet {agent|apply}' fail
Title: Message Title
Jason Knudsen commented on PUP-4436
Re: With a gem install of puppet, when run as root, 'puppet {agent|apply}' fail
Another use-case that may be blocked. In a lot of our situations, we'll run puppet as a non-privileged user on the system, under /opt or /data. We build our own ruby and gem install puppet and then point confdir there.
My initial attempt at getting the latest gem to work broke while trying to create those directories in /etc (which is not possible as a non-privileged user)
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4451) Allow automatic conversion of string to numeric for certain comparisons
Title: Message Title Henrik Lindberg commented on PUP-4451 Re: Allow automatic conversion of string to numeric for certain comparisons As you say, the way forward is to use facter with --stringified_facts turned off on the agent (afaik, you do not need cfacter for this). This gives you correct data types instead of a vague mush of data in string form. Meanwhile( and instead of using scanf) you can also write: if 0 + $::operatingsysemmajrelease = 7 to force conversion to a number. We are not going to open the can of worms that automatic string to number conversion would mean. (Sorry). Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title Christopher Price commented on PUP-4450 Re: Cannot load 'provider/network_route/routes.rb' We've had a couple of issues where we get 'no such file to load' because of the fact that we're really strict in Puppet Server about the ruby load path. You might want to validate the absolute path of the puppetx/filemapper code, and then check whether or not that path is included in the `ruby-load-path` setting, in the `jruby-puppet` section of `puppetserver.conf`. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2862) Validate that default value expression for param does not define variable
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-2862 Validate that default value _expression_ for param does not define variable Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3814) Duplicated error output
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-3814 Duplicated error output Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4447) error message when using $name/$title variables could be more expressive
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-4447 error message when using $name/$title variables could be more expressive Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2080) Support functions written in pp
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-2080 Support functions written in pp Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4444) Puppet 4 AIO can't find its own cfacter
Title: Message Title Michael Smith commented on PUP- Re: Puppet 4 AIO can't find its own cfacter We could write a clojure API for Facter. Not sure how to register custom facts without MRI though. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4444) Puppet 4 AIO can't find its own cfacter
Title: Message Title Peter Huene commented on PUP- Re: Puppet 4 AIO can't find its own cfacter My guess is that master's interaction with Facter would likely be limited to OS / fqdn facts. I'll look into what it would take to remove the in-process dependency, if possible to do so. Does puppet server support apply though? I ask because that's at least one scenario where it would be constructing a Node and gathering facts on the master. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2862) Validate that default value expression for param does not define variable
Title: Message Title Thomas Hallgren commented on PUP-2862 Re: Validate that default value _expression_ for param does not define variable Merged to master at 76c7979 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3814) Duplicated error output
Title: Message Title Thomas Hallgren commented on PUP-3814 Re: Duplicated error output Merged to master at 03f89e5 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4453) too many warnings/errors when master can't start due to no puppet user/group
Title: Message Title Eric Thompson created an issue Puppet / PUP-4453 too many warnings/errors when master can't start due to no puppet user/group Issue Type: Bug Assignee: Unassigned Created: 2015/04/22 8:00 AM Priority: Minor Reporter: Eric Thompson [root@l86deazwbquziik ~]# puppet master --no-daemonize Warning: could not change to group puppet: Invalid group: puppet could not change to group puppet Could not change to user puppet: Invalid user: puppet
Jira (PUP-4044) AIO acceptance tests copies multiple versions of repo configs to the SUT
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4044 AIO acceptance tests copies multiple versions of repo configs to the SUT Change By: Eric Thompson Assignee: QA EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3480) Puppet does not have Python 3 package provider (pip3)
Title: Message Title Melissa Stone updated an issue Puppet / PUP-3480 Puppet does not have Python 3 package provider (pip3) Change By: Melissa Stone Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4454) setup for data in environments and modules is overly complex
Title: Message Title
Eric Thompson created an issue
Puppet / PUP-4454
setup for data in environments and modules is overly complex
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2015/04/22 10:22 AM
Priority:
Normal
Reporter:
Eric Thompson
Environments
In environments one can use the default environment_data_provider of 'function' to provide data and it looks to the environment's function data() to provide the data. environment_data_provider can be set in an environment.conf. perhaps one could also specify the name of the function(s) in the environment.conf
Modules
setup data binding for a module:
# moduleroot/lib/puppet/bindings/mymodule/default.rb
#
Puppet::Bindings.newbindings('mymodule::default') do
Jira (PUP-4111) The environment_scenario-* acceptance tests aren't asserting their success/failure and are therefore always 'passing'
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-4111 The environment_scenario-* acceptance tests aren't asserting their success/failure and are therefore always 'passing' Change By: Eric Thompson Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2862) Validate that default value expression for param does not define variable
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-2862 Validate that default value _expression_ for param does not define variable Change By: Eric Thompson Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3988) remove logic for single feature hostname in 4.0 validator
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-3988 remove logic for single feature hostname in 4.0 validator Change By: Eric Thompson Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2080) Support functions written in pp
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-2080 Support functions written in pp Change By: Eric Thompson Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4178) defined() function returns true for undef and empty string, and false for main
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-4178 defined() function returns true for undef and empty string, and false for main Change By: Eric Thompson Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4444) Puppet 4 AIO can't find its own cfacter
Title: Message Title Christopher Price commented on PUP- Re: Puppet 4 AIO can't find its own cfacter `apply` would never be run in the server process; it could definitely be run on the same machine that Puppet Server was installed on, but it'd be running entirely through the client code path, so we shouldn't have any issues there. I don't think it'd be too hard to write a JNI wrapper around cfacter, but how that'd interact with MRI for custom facts is definitely something we should talk/think about. If you guys are calling into MRI from C, that might actually work fine via JNI. Peter Huene I do think the ideal path to the future will be to just get rid of most of the calls to facter from the server; I think you're right about fqdn (and any other ones that are used as default values for settings, like certname) being the main ones we need to think about. I'd like to believe that most of the rest of the interaction between the master and facter is incidental and unnecessary, but it would be great to get a sense of how much work it'd be to remove those calls. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4447) error message when using $name/$title variables could be more expressive
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-4447 error message when using $name/$title variables could be more expressive Change By: Eric Thompson Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3814) Duplicated error output
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-3814 Duplicated error output Change By: Eric Thompson Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4443) splat-assign multiple variables from a hash
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-4443 splat-assign multiple variables from a hash Change By: Eric Thompson Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4444) Puppet 4 AIO can't find its own cfacter
Title: Message Title Peter Huene commented on PUP- Re: Puppet 4 AIO can't find its own cfacter Even if we were able to use JNI to load libfacter and it, in turn, loaded libruby (this is normally done in reverse when running under libruby), there'd now be two Ruby VMs in the process: JRuby's and MRI's. The Facter API would only be defined in the MRI VM so any code expecting the Facter API to be present under the JRuby VM would still fail. Basically libfacter has an optional dependency on MRI by dynamically binding to libruby; it either loads it itself (e.g. run facter from the command line) or it uses an already loaded one (e.g. require 'facter' under a MRI process). To make libfacter work for JRuby would require JRuby to export the same symbols as MRI does in libruby. My guess that is not the case, nor likely to ever be the case, so I don't think JNI is a possible solution. At best a JRuby master could spawn facter as a separate process for (hopefully very limited) information. Once we determine the extent of a master's reliance on Facter (elephant in room: how many modules out there provide server-side extensions such as custom functions or report processors that rely on Facter?) we can answer the question of whether or not it's possible to remove the Facter dependency entirely. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4044) AIO acceptance tests copies multiple versions of repo configs to the SUT
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-4044 AIO acceptance tests copies multiple versions of repo configs to the SUT Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3944) Make sure puppetdb.conf is under $confdir
Title: Message Title Eric Thompson commented on PUP-3944 Re: Make sure puppetdb.conf is under $confdir anyone know why this was closed as fixed? no PR and comments imply won't fix. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3944) Make sure puppetdb.conf is under $confdir
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3944 Make sure puppetdb.conf is under $confdir Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4444) Puppet 4 AIO can't find its own cfacter
Title: Message Title Christopher Price commented on PUP- Re: Puppet 4 AIO can't find its own cfacter Even if we were able to use JNI to load libfacter and it, in turn, loaded libruby (this is normally done in reverse when running under MRI), there'd now be two Ruby VMs in the process: JRuby's and MRI's. The Facter API would only be defined in the MRI VM so any code expecting the Facter API to be present under the JRuby VM would still fail. Agreed; what I was suggesting was that we could provide an alternate implementation of the facter API that called through the JNI layer, similar to what we've done with the HTTP client. Then any JRuby code calling into the facter API would go through the JNI layer. It's not awesome but I think it could be done. At best a JRuby master could spawn facter as a separate process for (hopefully very limited) information. This is definitely another option. (elephant in room: how many modules out there provide server-side extensions such as custom functions or report processors that rely on Facter?) I'd hope this would be rare and fairly easy to workaround, but it is defintely an important question. If it's more common than I imagine, then it seems like a single call to facter at startup would be sufficient to populate the facts data we'd need for this use case, and worst case we just implement that call by shelling out, correct? So I'm still thinking the main hurdle is avoiding the implicit calls to facter during server startup / execution. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are
Jira (PUP-4444) Puppet 4 AIO can't find its own cfacter
Title: Message Title Peter Huene commented on PUP- Re: Puppet 4 AIO can't find its own cfacter Agreed; what I was suggesting was that we could provide an alternate implementation of the facter API that called through the JNI layer, similar to what we've done with the HTTP client. Then any JRuby code calling into the facter API would go through the JNI layer. It's not awesome but I think it could be done. Ah, that would definitely make more sense than what I was on about. That sounds possible, but a lot of work to make happen. So I'm still thinking the main hurdle is avoiding the implicit calls to facter during server startup / execution. Agreed, I think that's where the immediate effort should lay. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4111) The environment_scenario-* acceptance tests aren't asserting their success/failure and are therefore always 'passing'
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4111 The environment_scenario-* acceptance tests aren't asserting their success/failure and are therefore always 'passing' Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4235) Create rake task for puppet-passenger AIO acceptance tests
Title: Message Title Josh Cooper commented on PUP-4235 Re: Create rake task for puppet-passenger AIO acceptance tests The passenger package installs server related data files in a different place than puppetserver, e.g. reports, filebucket, etc. I think it would be useful to run a more extensive set of agent/master tests, e.g. ssl, pluginsync, enc, directory environments, etc to make sure things are working as expected. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4445) Add support to TLS 1.2 connections to Puppet Forge when SSLv3 is blocked in a corporate network
Title: Message Title Melissa Stone commented on PUP-4445 Re: Add support to TLS 1.2 connections to Puppet Forge when SSLv3 is blocked in a corporate network Hmm, this would come into play when we're compiling openssl, but I can't seem to track down exactly where that happens in rubyinstaller. I'll keep looking around, but in the meantime, Matthaus Owens or Rob Braden might have more insight Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4445) Add support to TLS 1.2 connections to Puppet Forge when SSLv3 is blocked in a corporate network
Title: Message Title Josh Cooper commented on PUP-4445 Re: Add support to TLS 1.2 connections to Puppet Forge when SSLv3 is blocked in a corporate network Louis Mayorga Puppet supports TLSv1.1 and 1.0, but not SSLv2 or SSLv3. If your corporate network was blocking TLSv1.0 or 1.1, then I would expect the initial ClientHello message sent by the client to the server to fail. However, the SSL handshake is proceeding far enough that the agent receives the server's Certificate message, and is unable to verify it. I do agree that the windows agent should support TLSv1.2, but I'm not sure that that is the reason for the failure. Can you run wireshark on the windows agent and capture a network trace (restricting traffic to port 8140)? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4454) setup for data in environments and modules is overly complex
Title: Message Title Henrik Lindberg commented on PUP-4454 Re: setup for data in environments and modules is overly complex The binding is a string modulename = string name of mechanism. We currently have 'none', and 'function', and the idea was to add 'hiera'. I can imagine we could have a compound name instead, say bind to function::mymodule::data in a module, and function:.environment::data in an environment. (This would allow using different names for the functions, which I think is of questionable value). Finally, the intent is to be able to specify the to 'funcion' part in module meta data and skip the binding configuration all together. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3855) auth.conf no longer restricting based on environment
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3855 auth.conf no longer restricting based on environment Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1444) PR (1358): (maint) Move late-project? from queries to columns - ajroetker
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1444 PR (1358): (maint) Move late-project? from queries to columns - ajroetker Change By: AJ Roetker Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-400) Manage hidden windows packages
Title: Message Title Ethan Brown assigned an issue to QA Puppet / PUP-400 Manage hidden windows packages Change By: Ethan Brown Status: Readyfor CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-400) Manage hidden windows packages
Title: Message Title Ethan Brown commented on PUP-400 Re: Manage hidden windows packages This has cleared CI at https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Master/view/Puppet/job/platform_aio-puppet_pkg-promote_master/19/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4447) error message when using $name/$title variables could be more expressive
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-4447 error message when using $name/$title variables could be more expressive Change By: Eric Thompson Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-962) operatingsystemmajrelease returns string data type
Title: Message Title Alex Jurkiewicz created an issue Facter / FACT-962 operatingsystemmajrelease returns string data type Issue Type: Bug Affects Versions: FACT 2.4.3 Assignee: Unassigned Created: 2015/04/22 5:20 PM Priority: Normal Reporter: Alex Jurkiewicz facter's `operatingsystemmajrelease` fact returns a string, when it could return a Number (in all cases I'm aware of, at least). This would be useful to allow version comparison in Puppet, see PUP-4451 . Add Comment
Jira (PUP-4451) Allow automatic conversion of string to numeric for certain comparisons
Title: Message Title Alex Jurkiewicz commented on PUP-4451 Re: Allow automatic conversion of string to numeric for certain comparisons Just to clarify, stringified_facts is gone in Puppet 4 – it's always on. I'll open another ticket to change the data type this fact returns. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4451) Allow automatic conversion of string to numeric for certain comparisons
Title: Message Title Henrik Lindberg commented on PUP-4451 Re: Allow automatic conversion of string to numeric for certain comparisons Changing the data type is a breaking change. A solution is to add a new fact, maybe even a structure where the data types are of a more useful data type. Note though that there is nothing saying that all operating systems universally will have a numeric value for this fact, so there may be the need to supply it both in string form, and as a number if possible, and it is the user's choice to use one or the other. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4447) error message when using $name/$title variables could be more expressive
Title: Message Title
Eric Thompson commented on PUP-4447
Re: error message when using $name/$title variables could be more expressive
validated on rhel7 at SHA: e5bce51
[root@lwfnn6bjeklzkfk puppet]# puppet apply -e '$title = lol $name = wut'
Error: Evaluation Error: Cannot reassign built in (or already assigned) variable '$title' at line 1:8 on node lwfnn6bjeklzkfk.delivery.puppetlabs.net
[root@lwfnn6bjeklzkfk puppet]# puppet apply -e '$name = wut'
Error: Evaluation Error: Cannot reassign built in (or already assigned) variable '$name' at line 1:7 on node lwfnn6bjeklzkfk.delivery.puppetlabs.net
[root@lwfnn6bjeklzkfk puppet]# puppet apply -e 'define mydefinite ($title){}'
Error: Could not parse for environment production: The parameter $title redefines a built in parameter in the 'define' _expression_ at line 1:20 on node lwfnn6bjeklzkfk.delivery.puppetlabs.net
[root@lwfnn6bjeklzkfk puppet]# puppet apply -e '[$title, $name] = [lol,wut]'
Error: Evaluation Error: Cannot reassign built in (or already assigned) variable '$title' at line 1:17 on node lwfnn6bjeklzkfk.delivery.puppetlabs.net
Jira (FACT-962) operatingsystemmajrelease returns string data type
Title: Message Title Alex Jurkiewicz updated an issue Facter / FACT-962 operatingsystemmajrelease returns string data type Change By: Alex Jurkiewicz facter's`operatingsystemmajrelease`factreturnsastring,whenitcouldreturna Number number (inallcasesI'mawareof,atleast).ThiswouldbeusefultoallowversioncomparisoninPuppet,seePUP-4451. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title Alex Jurkiewicz commented on PUP-4450 Re: Cannot load 'provider/network_route/routes.rb' Here, the path is modules/filemapper/lib/puppetx/filemapper.rb which starts with the following code: require 'puppet/util/filetype' # Forward declaration module PuppetX; end module PuppetX::FileMapper Add Comment This message was sent by Atlassian JIRA
Jira (PUP-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title Henrik Lindberg commented on PUP-4450 Re: Cannot load 'provider/network_route/routes.rb' I think that should be in modules/filemapper/lib/puppet_x/filemapper.rb - it should really also be under the name of the author of the module or it has the potential to clash with another author's use of a PuppetX::FileMapper namespaced thing. You can try hacking it by just adding the directory 'puppet_x' if you do not have it, and copy the file over. If that helps report the issue against the filemapper module. (Ping Adrien Thebo) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2080) Support functions written in pp
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-2080 Support functions written in pp Change By: Eric Thompson Assignee: QA EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4444) Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Kylo Ginsberg commented on PUP- Re: Puppetserver implictly relies on facter but has no mechanism to run native facter Also: I tried to reword the summary to match the issue as being discussed here. Wordsmithing is hard though, so if someone has something more pithy, go for it Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1444) PR (1358): (maint) Move late-project? from queries to columns - ajroetker
Title: Message Title gepetto-bot commented on PDB-1444 Re: PR (1358): (maint) Move late-project? from queries to columns - ajroetker wkalt commented: I'm +1 on this – makes things a bit more explicit. Ultimately we'll need to handle the underlying issue of late-project (which is relevant to group-by) by pushing all projections to the database and getting rid of the must-have flag. I've created https://tickets.puppetlabs.com/browse/PDB-1447 to cover this work. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3774) puppet fails to manipulate user's group membership if group name has space in it
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3774 puppet fails to manipulate user's group membership if group name has space in it Change By: Kylo Ginsberg Fix Version/s: PUP4.1.0 Fix Version/s: PUP4.2.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4385 Can't write WOMANS HAT emoji with \u unicode escapes Change By: Josh Cooper Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1444) PR (1358): (maint) Move late-project? from queries to columns - ajroetker
Title: Message Title gepetto-bot commented on PDB-1444 Re: PR (1358): (maint) Move late-project? from queries to columns - ajroetker mullr commented: Generally lgtm, just some small comments. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1043) Specifying file content by checksum should not use 'content' property
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1043 Specifying file content by checksum should not use 'content' property Change By: Josh Cooper Fix Version/s: PUP4.1.0 Fix Version/s: PUP4.x Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4374 Splatting attributes into an amended attribute block isn't supported Change By: Henrik Lindberg Fix Version/s: PUP3.8.1 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2862) Validate that default value expression for param does not define variable
Title: Message Title Eric Thompson commented on PUP-2862 Re: Validate that default value _expression_ for param does not define variable validated on redhat7 at SHA: e5bce51 [root@lwfnn6bjeklzkfk ~]# puppet apply -e 'define foo ($a = ($b = 10))' Error: Could not parse for environment production: Syntax error at end of file on node lwfnn6bjeklzkfk.delivery.puppetlabs.net Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4198) Add install_options feature to pip provider
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4198 Add install_options feature to pip provider Change By: Josh Cooper Sprint: Client2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4457) Puppet::Node::Facts add_local_facts -- review for deprecation
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4457 Puppet::Node::Facts add_local_facts -- review for deprecation Change By: Kylo Ginsberg Issue Type: Improvement Task Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4457) Puppet::Node::Facts add_local_facts review for deprecation
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4457 Puppet::Node::Facts add_local_facts review for deprecation Issue Type: Improvement Assignee: Unassigned Created: 2015/04/22 2:49 PM Priority: Normal Reporter: Kylo Ginsberg There are three facts in add_local_facts: clientversion (duplicate of puppetversion) clientnoop clientcert These should be reviewed for possible deprecation. Depending on the outcome of that, there might be more cleanup possible, e.g. these might be moved to where puppet 4 now sets puppetversion and/or the network_device usage of add_local_facts might be obviated. Add Comment
Jira (PUP-4351) Default service type and package provider not set on Cumulus Linux
Title: Message Title Josh Cooper assigned an issue to QA Puppet / PUP-4351 Default service type and package provider not set on Cumulus Linux Change By: Josh Cooper Status: Readyfor CI Test Assignee: MelissaStone QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4351) Default service type and package provider not set on Cumulus Linux
Title: Message Title Josh Cooper commented on PUP-4351 Re: Default service type and package provider not set on Cumulus Linux Eric Thompson, Melissa Stone since this passed CI and we don't have cumulus linux to test against, I'm going to mark as resolved. Please reopen if you want to take a closer look. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2630
Server-set global variables like $::environment get overwritten by client facts
Change By:
Henrik Lindberg
REPORTEDPROBLEM---Asperthedocs(http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master)thepuppetmastersetstheglobal$::environmentvariabletocontainthenameofthenode'senvironment.However,ifanodeprovidesafactwiththename'environment'thatfact'svalueoverridestheserver-setenvironment.Thesamehappenswithotherserver-setglobalvariables,like$::servernameand$::serverip.Asaresult,modulescan'treliablyusethesevariablesforwhatevertheirintendedpurposeis.Ifthisistheintendedbehavior,thenthedocsshouldclarifythisanddiscourageuseoftheserver-setvariables,becauseamisbehavingnodecanoverridethem.SOLUTION---Addafunctionthatreturnstheserverfacts(e.g.{{server_facts()}}sincethatmakesitpossibleformoduleauthorstodependonpuppet4.1.0andgetexpectedvalueswithoutanyopt-in.Thisispreferredoversettingyetanotherglobalvariablename.* Separatethelogicinnode(seecommentfromAndyParkerbelowwiththedetails)tomakeitpossibletoretrievetheserversidefactslater* Addafunction{{server_facts()}}thatreturnsahashoftheserversidefacts (thatweresetasideinthenode) *Iftherearenoserversidefacts(puppetapplycase),anemptyhashisreturned*Issueawarningwhenafactoverwritesaserversidefact(butperformtheoverwritesincenotdoingsobreaksAPI)*Decideonrealresolutionofthisissue:(Ping[~eric.sorenson] )**Possibly i.e.possibly deprecatesettingserverfactsasvariablesintopscope? So (Adddeprecationticket , addremovalticket for 4 PUP5 . 1. 0 -maketheseparationinthenodelogictoenablethefunctiontogetcorrectdata,butkeepthevariableoverwrites . Alsoaddawarningwhenthereisanoverwriteofaserverfactbyafact. 0) QA---risk:highprobability:mediumseverity:high(hardtodebug,somewhatofasecurityissue,canspoofenvironment)testlayer:acceptance
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4445) Add support to TLS 1.2 connections to Puppet Forge when SSLv3 is blocked in a corporate network
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4445 Add support to TLS 1.2 connections to Puppet Forge when SSLv3 is blocked in a corporate network Change By: Josh Cooper Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2080) Support functions written in pp
Title: Message Title Eric Thompson commented on PUP-2080 Re: Support functions written in pp thanks Henrik. Will sub-task and look into those options. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2080) Support functions written in pp
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2080 Support functions written in pp Change By: Eric Thompson Addtheabilitytowritefunctionsinthepuppetlanguage.Functionsshouldbestoredunder./functionsrelativetotherootofamodule.Functionnamesshouldsupportfullyqualifiednames.risk:highprobability:high(usersdon'tlikewritingfunctionsinruby)severity:medium(workarounds:rubyfunctions)testlayer:acceptance(weshouldhaveatleastasimple acceptance testtoensurethisworks) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4443) splat-assign multiple variables from a hash
Title: Message Title
Eric Thompson commented on PUP-4443
Re: splat-assign multiple variables from a hash
validated on rhel7 at SHA: e5bce51
[root@lwfnn6bjeklzkfk puppet]# puppet apply -e '[[$a, $b], $c] = {[a,b] = {a = 10, b = 20 }, c = 30 } notice $a $b $c'
Notice: Scope(Class[main]): 10 20 30
Notice: Compiled catalog for lwfnn6bjeklzkfk.delivery.puppetlabs.net in environment production in 0.39 seconds
Notice: Applied catalog in 0.02 seconds
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you
Jira (PUP-4444) Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP- Puppetserver implictly relies on facter but has no mechanism to run native facter Change By: Kylo Ginsberg Summary: Puppet4AIOcan'tfinditsowncfacter Puppetserverimplictlyreliesonfacterbuthasnomechanismtorunnativefacter Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4235) Create rake task for puppet-passenger AIO acceptance tests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4235 Create rake task for puppet-passenger AIO acceptance tests Change By: Josh Cooper Fix Version/s: PUP4.1.0 Fix Version/s: PUP4.x Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4385) Can't write WOMANS HAT emoji with \uXXXX unicode escapes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4385 Can't write WOMANS HAT emoji with \u unicode escapes Not important enough to also do for PUP 3.8.1, but can be cherry picked if something thinks this should be done. Change By: Henrik Lindberg Sprint: Language2015-04-29 Story Points: 1 Scope Change Reason: Foundbydocs Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4417) Either affirm or revert changes to allowed environment names
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4417 Either affirm or revert changes to allowed environment names Change By: Josh Cooper Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4184) Puppet resource package behaves inconsistently for packages with same name from different providers
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4184 Puppet resource package behaves inconsistently for packages with same name from different providers Change By: Josh Cooper Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4435) Deprecate Puppet WEBrick and Rack servers
Title: Message Title William Hopper updated an issue Puppet / PUP-4435 Deprecate Puppet WEBrick and Rack servers Change By: William Hopper ThePuppetWEBrick andRack master server servesr shouldbedeprecated,asweplantoeventuallyremove it theminfavorofPuppetServer .From[~kylo]:I'dliketoaddadeprecationnoticeatthesametime,sincetheplantodeprecate,andlaterdrop,webrickisinpartwhathasmotivatedthechangesthatleadtothisissue.ThisreferstoPUP-4394,whereinthepuppet-agentpackagedoesn'tcreatethepuppetuserbydefaultsoWEBrickfailstostartunlesstheuserismanuallycreated.RiskAssessment:lowProbability:lowImpact:lowTestLayer:unit Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2630
Server-set global variables like $::environment get overwritten by client facts
Change By:
Henrik Lindberg
REPORTEDPROBLEM---Asperthedocs(http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master)thepuppetmastersetstheglobal$::environmentvariabletocontainthenameofthenode'senvironment.However,ifanodeprovidesafactwiththename'environment'thatfact'svalueoverridestheserver-setenvironment.Thesamehappenswithotherserver-setglobalvariables,like$::servernameand$::serverip.Asaresult,modulescan'treliablyusethesevariablesforwhatevertheirintendedpurposeis.Ifthisistheintendedbehavior,thenthedocsshouldclarifythisanddiscourageuseoftheserver-setvariables,becauseamisbehavingnodecanoverridethem.SOLUTION---Addafunctionthatreturnstheserverfacts(e.g.{{server_facts()}}sincethatmakesitpossibleformoduleauthorstodependonpuppet4.1.0andgetexpectedvalueswithoutanyopt-in.Thisispreferredoversettingyetanotherglobalvariablename.*Separatethelogicinnode(seecommentfromAndyParkerbelowwiththedetails)tomakeitpossibletoretrievetheserversidefactslater*Addafunction{{server_facts()}}thatreturnsahashoftheserversidefacts(thatweresetasideinthenode)*Iftherearenoserversidefacts(puppetapplycase),anemptyhashisreturned*Issueawarningwhenafactoverwritesaserversidefact(butperformtheoverwritesincenotdoingsobreaksAPI)*Decideonrealresolutionofthisissue:(Ping[~eric.sorenson]i.e.possiblydeprecatesettingserverfactsasvariablesintopscope?(Adddeprecationticket,addremovalticketforPUP5.0.0) *ForDOCS,shouldmentionthat{{server_facts()}}shouldbeusedinsteadofusingtopscopevariablesastheycannotbereliedupon. QA---risk:highprobability:mediumseverity:high(hardtodebug,somewhatofasecurityissue,canspoofenvironment)testlayer:acceptance
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title Henrik Lindberg assigned an issue to Hailee Kenney Puppet / PUP-2630 Server-set global variables like $::environment get overwritten by client facts Change By: Henrik Lindberg Assignee: HaileeKenney Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2630 Server-set global variables like $::environment get overwritten by client facts Change By: Henrik Lindberg Component/s: Server Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4435) Deprecate Puppet WEBrick and Rack servers
Title: Message Title William Hopper updated an issue Puppet / PUP-4435 Deprecate Puppet WEBrick and Rack servers Change By: William Hopper Summary: DeprecatePuppetWEBrick server andRackservers Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-956) Update puppet-agent#master to build facter#master, remove cfacter
Title: Message Title Josh Cooper commented on FACT-956 Re: Update puppet-agent#master to build facter#master, remove cfacter PUP- means that we can't test the latest puppet-agent#master (containing only native facter#master) with puppetserver in CI, added as a blocking ticket. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2080) Support functions written in pp
Title: Message Title Henrik Lindberg commented on PUP-2080 Re: Support functions written in pp Eric Thompson As you can see if you dive into the comments there are a couple of aspects that relate to function in puppet language, and there are unit/integration tests that cover those cases. From an acceptance/user perspective: it should be able to define functions in modules, and call those from the environment, and other modules that either have no dependencies at all, or have a dependency on the module where the function is defined. it is possible to write functions that are not autoloaded (just defined in a manifest that is loaded via other means) the caller of a function does not need to know if it is a 3.x, 4.x ruby, or 4.x pp function (obvious in the puppet language, but should also be true in ruby for 4.x functions (calling 4.x pp functions). it should be possible to have functions in the environment in the namespace 'environment::' Not sure how much of that we need to have acceptance tests for - some of the features are implemented in the loader system, some in the 4.x function framework, and a small part in the 'functions in puppet language'. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-3566) Remove support for versions in faces
Title: Message Title Josh Cooper commented on PUP-3566 Re: Remove support for versions in faces Andy Parker retargeting fix version for now, pull requests are welcome Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2638) Missing dependent directory from Puppet Agent install causes issues with resource graphing
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2638 Missing dependent directory from Puppet Agent install causes issues with resource graphing Change By: Josh Cooper Fix Version/s: PUP4.1.0 Fix Version/s: PUP4.2.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4362) Portage package provider does not list all installed packages
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4362 Portage package provider does not list all installed packages Change By: Josh Cooper Sprint: Client2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3908) Tidy type is too verbose when working of directories containing lot of files
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3908 Tidy type is too verbose when working of directories containing lot of files Change By: Josh Cooper Sprint: Client2015-05-13 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4457) Puppet::Node::Facts add_local_facts -- review for deprecation
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4457 Puppet::Node::Facts add_local_facts -- review for deprecation Change By: Kylo Ginsberg Fix Version/s: PUP4.x Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4457) Puppet::Node::Facts add_local_facts -- review for deprecation
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4457 Puppet::Node::Facts add_local_facts -- review for deprecation Change By: Kylo Ginsberg Summary: Puppet::Node::Factsadd_local_facts -- reviewfordeprecation Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4435) Deprecate Puppet WEBrick server
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4435 Deprecate Puppet WEBrick server Change By: Josh Cooper Fix Version/s: PUP4.1.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4184) Puppet resource package behaves inconsistently for packages with same name from different providers
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4184 Puppet resource package behaves inconsistently for packages with same name from different providers Change By: Josh Cooper Fix Version/s: PUP4.x Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4374 Splatting attributes into an amended attribute block isn't supported Change By: Henrik Lindberg Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
