Jira (PUP-2156) file provider silent behaviour change for mode
Title: Message Title Per Cederqvist commented on an issue Re: file provider silent behaviour change for mode I can't seem to let go about this issue. Sorry if I keep nagging, but I got a new idea over the weekend. There should be a deprecation warning if a non-string mode variable is used. This should be added well in advance of Puppet 4. Here is a list of test cases and whether I think the should produce a deprecation warning when using the default parser: format deprecated? 777 yes 0777 probably '777' or 777 probably '0777' or 0777 no 4711 yes 04711 probably
Jira (PUP-1960) realizing an empty array of resources fails in future evaluator
Title: Message Title
Andy Parker commented on an issue
Re: realizing an empty array of resources fails in future evaluator
I'm not sure that I like the single value array behavior. It means that you don't get consistent return types out of the _expression_ given consistent input types. I also agree that continuing that behavior is just another aspect of PUP-1299.
If we had a function called find_resource(r, b), which is just an alias for the notation in the language, where r :: ResourceType then what we need are two variants of the function for different types of b.
find_resource(r, b) :: ResourceType - String - Maybe Resource
find_resource(r, b) :: ResourceType - [String] - [Resource] I think the chosen semantics mostly match these signatures, if we take Maybe Resource to mean that the return value is undef or a value in the puppet language. I think this makes a lot of sense. I also agree with Erik that the empty array case shouldn't be a warning. The only disconnect is the flattening of the arrays.
Since nested arrays are pretty much a tree structure, one way of expressing this would be to say find_resource(r, b) :: ResourceType - Tree String - [Resource]. I have to admit, that seems very strange to me, but if it is commonly used, then so be it.
Add Comment
Puppet / PUP-1960
realizing an empty array of resources fails in future evaluator
The following code runs fine without deprecation warning in old evaluator but fails in 3.5-rc1: {code} realize(File[[]]) {code} {noformat} Error: Evaluation Error: File[] accepts 1
Jira (PUP-1960) realizing an empty array of resources fails in future evaluator
Title: Message Title
Erik Daln commented on an issue
Re: realizing an empty array of resources fails in future evaluator
I don't think the nested array stuff is commonly used. Perhaps someone has noticed they can use it and do so, but it should be really easy for them to just use the flatten() function from stdlib.
Add Comment
Puppet / PUP-1960
realizing an empty array of resources fails in future evaluator
The following code runs fine without deprecation warning in old evaluator but fails in 3.5-rc1: {code} realize(File[[]]) {code} {noformat} Error: Evaluation Error: File[] accepts 1 argument. Got 0 on node test.dalen.cloud.spotify.net Error: Evaluation Error: File[] accepts 1 argument. Got 0 on node test.dalen.cloud.spotify.net {noformat}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
Jira (PUP-2158) Directory Environments breaks many classic Config File Environments
Title: Message Title Andy Parker updated an issue Puppet / PUP-2158 Directory Environments breaks many classic Config File Environments Change By: Andy Parker Fix Version/s: 3.5.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2158) Directory Environments breaks many classic Config File Environments
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2158 Directory Environments breaks many classic Config File Environments Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2158) Directory Environments breaks many classic Config File Environments
Title: Message Title
Andy Parker commented on an issue
Re: Directory Environments breaks many classic Config File Environments
Discussion of options for resolving the conflict on the puppet-dev list at https://groups.google.com/forum/?utm_medium=emailutm_source=footer#!msg/puppet-dev/OeGCFTVxFwA/qVz8sIbFd5cJ
Add Comment
Puppet / PUP-2158
Directory Environments breaks many classic Config File Environments
If you use the script in the classic blog post http://puppetlabs.com/blog/git-workflow-and-puppet-environments you have Config File Environments located at /etc/puppet/environments. Unfortunately, Puppet 3.5.0 will treat them as Directory Environments. If you have a modulepath such as this: {noformat} modulepath=/etc/puppet/environments/$environme...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-1444) Allow for different permissions for main directory in recursive file object
Title: Message Title Martin Hcker commented on an issue Re: Allow for different permissions for main directory in recursive file object Actually it would very much like to specify that in a recursive directory that is created via a file resource, the files are readable, while the directories are executable too - but not the files. This bug http://projects.puppetlabs.com/issues/20001 suggests that this can be achieved with a syntax like 'mode = 'u=rw,g=rs,o=r',' but that is not anymore the case and anyway an ugly and very not self documenting hack if it is achieved like this. Add Comment Puppet / PUP-1444 Allow for different permissions for main directory in recursive file object I tried to set 0750 for a directory and 0770 for all files in that directory with puppet. It seemed not possible without an ugly find command via an exec in the module. It would be nice if one could set a different mode for the parent directory (as specified in the path variable) than for the files inside that directory. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to
Jira (PUP-1030) FreeBSD: Puppet triggers loading of ZFS module
Title: Message Title Remko Catersels updated an issue Puppet / PUP-1030 FreeBSD: Puppet triggers loading of ZFS module Change By: Remko Catersels Affects Version/s: 3.4.3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1030) FreeBSD: Puppet triggers loading of ZFS module
Title: Message Title Remko Catersels commented on an issue Re: FreeBSD: Puppet triggers loading of ZFS module Issue still exists with Puppet 3.4.3. Add Comment Puppet / PUP-1030 FreeBSD: Puppet triggers loading of ZFS module When puppet starts the puppet ZFS provider issues the zfs command. On FreeBSD this automatically loads the ZFS kernel module. Even when ZFS is not used on that host. The provider should first check if ZFS is enabled or not. If it's not enabled it shouldn't execute any zpool or zfs commands as those will trigger the automatic load of the kernel module. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title
Markus Schuster created an issue
Puppet / PUP-2169
Not possible to manage SELinux file contexts via puppet in a sane way
Issue Type:
Bug
Affects Versions:
3.4.3
Assignee:
Unassigned
Created:
07/Apr/14 6:40 AM
Environment:
CentOS 6.5 x86_64 Puppet 3.4.3 from Puppetlabs repository
Priority:
Normal
Reporter:
Markus Schuster
There's currently no sane way to manage SELinux file contexts using puppet. The only way is to call 'semanage' via a 'exec' resource. But then the next issue comes up: Puppet seems to keep some file context rule cache, built once at startup. I wasn't able to find a way to invalidate this cache without restarting the whole puppet agent. Even when calling 'restorecon' from puppet, the next puppet run will reset file contexts for 'file' resources found in the catalog because of the cached file context rules.
How to reproduce:
setest.pp
file { '/srv/setest-before':
ensure = directory,
}
- exec { 'semanage':
command = '/usr/sbin/semanage fcontext -a -t home_root_t /srv/setest[^/]*',
creates = '/srv/setest-after',
}
- file { '/srv/setest-after':
ensure
Jira (PDB-560) PR (904): Fixed 'same file' error when running rake install - Ginja
Title: Message Title gepetto-bot commented on an issue Re: PR (904): Fixed 'same file' error when running rake install - Ginja kbarber commented: @Ginja so as far as the main issue you have pointed out, I cannot replicate it: https://gist.github.com/kbarber/10020594 But yes, it seems rake package:bootstrap should be a mandatory step, and if you can change that in the docs that would be much appreciated. I think you're getting the weird effect in master due to your 'version' file perhaps? That file shouldn't be necessary if you have rake package:version -s. The formats of the version slightly differ, so I imagine thats causing you hassles. Add Comment PuppetDB / PDB-560 PR (904): Fixed 'same file' error when running rake install - Ginja h2. Fixed 'same file' error when running rake install * Author: Riley Shott * Company: * Github ID: [Ginja|https://github.com/Ginja] * [Pull Request 904 Discussion|https://github.com/puppetlabs/puppetdb/pull/904] * [Pull Request 904 File Diff|https://github.com/puppetlabs/puppetdb/pull/904/files] h2. Pull Request Description Setup: Cen... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2170) Puppet always recreates Nagios_hosts
Title: Message Title Jonathan Gazeley created an issue Puppet / PUP-2170 Puppet always recreates Nagios_hosts Issue Type: Bug Affects Versions: 3.4.3 Assignee: Kylo Ginsberg Components: Types and Providers Created: 07/Apr/14 7:16 AM Environment: [jg4461@monitor ~]$ puppet -V 3.4.3 [jg4461@monitor ~]$ ruby -v ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] [jg4461@monitor ~]$ cat /etc/redhat-release CentOS release 6.5 (Final) Priority: Normal Reporter: Jonathan Gazeley I've been using puppet with nagios for ages without any problems. Recently I looked into the puppet logs on my nagios server and it seems on every puppet run, puppet throws an error and recreates all the nagios_host objects (see below), even if none of them have been changed. I haven't changed my config so is there a new bug? Thanks, Jonathan [jg4461@monitor ~]$ sudo puppet agent -t Notice: Ignoring --listen on onetime run Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb Info: Loading facts in
Jira (PDB-563) puppet nodes status -- SSL problems
Title: Message Title
Kenneth Barber commented on an issue
Re: puppet nodes status -- SSL problems
Andreas Rtten did you see my previous message on this ^^.
Add Comment
PuppetDB / PDB-563
puppet nodes status -- SSL problems
We are getting a SSL error while calling {code} # puppet node status puppetdb-test02.domain.net Error: Could not retrieve status for puppetdb-test02.domain.net: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished A {code} In the puppetdb log we see this: {code} 2014-03-28 15:46:06,694 DEBUG [qtp1303770546-46] [nio.ssl] SCEP@7705bc1...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2171) wrong quoting used in concatfragments.sh
Title: Message Title Theo Cabrerizo Diem created an issue Puppet / PUP-2171 wrong quoting used in concatfragments.sh Issue Type: Bug Assignee: Eric Sorenson Components: Community Created: 07/Apr/14 7:31 AM Environment: Debian wheezy GNU bash, version 4.2.37(1)-release (x86_64-pc-linux-gnu) Mac OS X GNU bash, version 3.2.51(1)-release (x86_64-apple-darwin13) Labels: puppetlabs-concat Priority: Critical Reporter: Theo Cabrerizo Diem At line 101 in https://github.com/puppetlabs/puppetlabs-concat/blame/master/files/concatfragments.sh : There's just too much quoting, resulting in a filename which contains double-quote characters. The error message from puppet is ls: cannot access /var/lib/puppet/concat/_etc_newrelic_newrelic_plugin_agent.cfg_mongodb/fragments: No such file or directory Please note that the filename shown contains the double-quote characters.
Jira (PUP-1964) Using undefined variable as class parameter default fails in future evaluator
Title: Message Title
Henrik Lindberg commented on an issue
Re: Using undefined variable as class parameter default fails in future evaluator
Merged to master e9c2174
Add Comment
Puppet / PUP-1964
Using undefined variable as class parameter default fails in future evaluator
The following manifest fails in the future evaluator: {code} class a ($b=$x) {notify{$b:}} include a {code} I get the following output (also not the lack of line numbers): {noformat} Error: Evaluation Error: Error while evaluating a Function Call, Received incomplete information - no value provided for parameter b on node test.dalen.cloud.spo...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1964) Using undefined variable as class parameter default fails in future evaluator
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1964 Using undefined variable as class parameter default fails in future evaluator Change By: Henrik Lindberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1964) Using undefined variable as class parameter default fails in future evaluator
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1964 Using undefined variable as class parameter default fails in future evaluator Change By: Henrik Lindberg Sprint: Week2014-4-02to2014-4-09 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1960) realizing an empty array of resources fails in future evaluator
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-1960 realizing an empty array of resources fails in future evaluator Change By: Henrik Lindberg Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-563) puppet nodes status -- SSL problems
Title: Message Title
Andreas Rtten commented on an issue
Re: puppet nodes status -- SSL problems
Kenneth Barber yes I saw it. Sorry for not responding.
I have not tested it but I assume it would work.
In our current setup it should be working if we set a default certname in main and only one in master or agent if it's differ from that.
So from my point of view the next step should be either to create a [node] section or to close this ticket and leave it as it is.
Add Comment
PuppetDB / PDB-563
puppet nodes status -- SSL problems
We are getting a SSL error while calling {code} # puppet node status puppetdb-test02.domain.net Error: Could not retrieve status for puppetdb-test02.domain.net: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished A {code} In the puppetdb log we see this: {code} 2014-03-28 15:46:06,694 DEBUG [qtp1303770546-46] [nio.ssl] SCEP@7705bc1...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs
Jira (PUP-1960) realizing an empty array of resources fails in future evaluator
Title: Message Title
Henrik Lindberg commented on an issue
Re: realizing an empty array of resources fails in future evaluator
Treating this as a failed review. I will rework the API for Resource and Class type parameterizations as per what we agreed on above.
See no harm in keeping the flattening semantics. This was something I discussed with a couple of users in Ghent. It is being used when they get resource names from multiple places e.g. File[$a, $b, $c], where each of the variables is an array.
Add Comment
Puppet / PUP-1960
realizing an empty array of resources fails in future evaluator
The following code runs fine without deprecation warning in old evaluator but fails in 3.5-rc1: {code} realize(File[[]]) {code} {noformat} Error: Evaluation Error: File[] accepts 1 argument. Got 0 on node test.dalen.cloud.spotify.net Error: Evaluation Error: File[] accepts 1 argument. Got 0 on node test.dalen.cloud.spotify.net {noformat}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this
Jira (PUP-2170) Puppet always recreates Nagios_hosts
Title: Message Title Jonathan Gazeley updated an issue Puppet / PUP-2170 Puppet always recreates Nagios_hosts Change By: Jonathan Gazeley I'vebeenusingpuppetwithnagiosforageswithoutanyproblems.RecentlyIlookedintothepuppetlogsonmynagiosserveranditseemsoneverypuppetrun,puppetthrowsanerrorandrecreatesallthenagios_hostobjects(seebelow),evenifnoneofthemhavebeenchanged.Ihaven'tchangedmyconfigsoisthereanewbug?Thanks,Jonathan ``` [jg4461@monitor~]$sudopuppetagent-tNotice:Ignoring--listenononetimerunInfo:RetrievingpluginfactsInfo:RetrievingpluginInfo:Loadingfactsin/var/lib/puppet/lib/facter/concat_basedir.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/python_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/srvadminpkgcount.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/gitolite_basedir.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/lib_path.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/virtualenv_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/ads_domain.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/rubyversion_major.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/cron_dayofmonth.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/partitions.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/winbind_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/vmparent.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/facter_dot_d.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/root_home.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/puppet_vardir.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/mountpoints.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/manufacturer.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/cron_dayofweek.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/oracle_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/cron_hour.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/os_maj_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/gateway.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/iptables_persistent_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/warranty.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/cron_minute.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/pip_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/iptables_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/ip6tables_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/isopenmanagesupported.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/pe_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/environment.rbInfo:Cachingcatalogformonitor.resnet.bris.ac.ukError:/Stage[main]/Nagios::Server/Resources[nagios_host]:Failedtogenerateadditionalresourcesusing'generate':undefinedmethod`file='for#Puppet::Error:0x7f0910359ab0Info:Applyingconfigurationversion'1396867605'Error:Couldnotprefetchnagios_hostprovider'naginator':undefinedmethod`file='for#Puppet::Error:0x7f0912f92ff0Notice:/Stage[main]/Nagios::Server/Nagios_host[radius01.nomadic-core.bris.ac.uk]/ensure:created... ```
Jira (PUP-2170) Puppet always recreates Nagios_hosts
Title: Message Title Jonathan Gazeley updated an issue Puppet / PUP-2170 Puppet always recreates Nagios_hosts Change By: Jonathan Gazeley I'vebeenusingpuppetwithnagiosforageswithoutanyproblems.RecentlyIlookedintothepuppetlogsonmynagiosserveranditseemsoneverypuppetrun,puppetthrowsanerrorandrecreatesallthenagios_hostobjects(seebelow),evenifnoneofthemhavebeenchanged.Ihaven'tchangedmyconfigsoisthereanewbug?Thanks,Jonathan ``` [jg4461@monitor~]$sudopuppetagent-tNotice:Ignoring--listenononetimerunInfo:RetrievingpluginfactsInfo:RetrievingpluginInfo:Loadingfactsin/var/lib/puppet/lib/facter/concat_basedir.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/python_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/srvadminpkgcount.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/gitolite_basedir.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/lib_path.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/virtualenv_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/ads_domain.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/rubyversion_major.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/cron_dayofmonth.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/partitions.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/winbind_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/vmparent.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/facter_dot_d.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/root_home.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/puppet_vardir.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/mountpoints.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/manufacturer.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/cron_dayofweek.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/oracle_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/cron_hour.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/os_maj_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/gateway.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/iptables_persistent_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/warranty.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/cron_minute.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/pip_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/iptables_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/ip6tables_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/isopenmanagesupported.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/pe_version.rbInfo:Loadingfactsin/var/lib/puppet/lib/facter/environment.rbInfo:Cachingcatalogformonitor.resnet.bris.ac.ukError:/Stage[main]/Nagios::Server/Resources[nagios_host]:Failedtogenerateadditionalresourcesusing'generate':undefinedmethod`file='for#Puppet::Error:0x7f0910359ab0Info:Applyingconfigurationversion'1396867605'Error:Couldnotprefetchnagios_hostprovider'naginator':undefinedmethod`file='for#Puppet::Error:0x7f0912f92ff0Notice:/Stage[main]/Nagios::Server/Nagios_host[radius01.nomadic-core.bris.ac.uk]/ensure:created... ```
Jira (PDB-563) puppet nodes status -- SSL problems
Title: Message Title
Kenneth Barber commented on an issue
Re: puppet nodes status -- SSL problems
Andreas Rtten test out either solution and let us know how it goes.
Add Comment
PuppetDB / PDB-563
puppet nodes status -- SSL problems
We are getting a SSL error while calling {code} # puppet node status puppetdb-test02.domain.net Error: Could not retrieve status for puppetdb-test02.domain.net: SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read finished A {code} In the puppetdb log we see this: {code} 2014-03-28 15:46:06,694 DEBUG [qtp1303770546-46] [nio.ssl] SCEP@7705bc1...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2021) $name var should be resource name systematicaly
Title: Message Title
Ken Dreyer updated an issue
Puppet / PUP-2021
$name var should be resource name systematicaly
Change By:
Ken Dreyer
Thiscarriesforwardhttps://projects.puppetlabs.com/issues/15718spurredbyanattempttoinvokethefollowing: {noformat} user{'dboldt':ensure=present,comment='DavidBoldt',uid=26869,gid='natweb',groups='wheel',shell='/bin/ksh',home=${home}/${name},password='NP'} {noformat} whereIdiscoveredthat$nameissettotheclassnameratherthantheresourcename.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2158) Directory Environments breaks many classic Config File Environments
Title: Message Title Andy Parker updated an issue Puppet / PUP-2158 Directory Environments breaks many classic Config File Environments Change By: Andy Parker Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2158) Directory Environments breaks many classic Config File Environments
Title: Message Title Andy Parker updated an issue Puppet / PUP-2158 Directory Environments breaks many classic Config File Environments Change By: Andy Parker Sprint: Week2014-4-02to2014-4-09 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2164) require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2164 require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized Change By: Charlie Sharpsteen Environment: PuppetLabsrepos Centos6.5 PuppetLabsrepos Ruby1.8.7 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2156) file provider silent behaviour change for mode
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2156 file provider silent behaviour change for mode Change By: Charlie Sharpsteen Labels: future-parser Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2158) Directory Environments breaks many classic Config File Environments
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-2158 Directory Environments breaks many classic Config File Environments Change By: Joshua Partlow Assignee: JoshuaPartlow Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2154) Puppet Resource Package not work with Windows OS (russian localization)
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2154 Puppet Resource Package not work with Windows OS (russian localization) Change By: Joshua Cooper Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-509) Document plan and design for environments
Title: Message Title Kenneth Barber commented on an issue Re: Document plan and design for environments Status: so right now the design (https://confluence.puppetlabs.com/display/ProMan/PDB+Environment+Awareness+Design) was slightly changed after discussions in this thread: https://groups.google.com/forum/#!searchin/puppet-users/puppetdb%7Csort:date/puppet-users/g0xzNc7p4mE/tVR3TVnjJEcJ It seems we're still dithering on how to constraint an environment during collection before this can move on. Add Comment PuppetDB / PDB-509 Document plan and design for environments How environment support works. Design and plan. Review with UI team. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2163) yumrepo resource completely broken with 3.5 release
Title: Message Title Ashley Penney commented on an issue Re: yumrepo resource completely broken with 3.5 release So far I've dealt with 1 and 3, I'm looking at 2 and 4 now to make sure we retain whatever behavior 3.4 offered. I think we're in a better situation already. We've overhauled the unit tests, I've been writing acceptance tests, and it's looking like we'll be in better shape for 3.5.1. Add Comment Puppet / PUP-2163 yumrepo resource completely broken with 3.5 release 1. Any attribute that can take 'absent' as a value, either complains about it being invalid or puts the actual text value 'absent' in to the produced repo file. http://docs.puppetlabs.com/references/latest/type.html#yumrepo for example: exclude = absent ends up looking like exclude=absent in the .repo file. 2. yumrepo resource title sho... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-1362) Rubyize yumhelper.py to remove dependency on python
Title: Message Title Dominic Cleal commented on an issue Re: Rubyize yumhelper.py to remove dependency on python I agree with Joshua's statements, there is a lack of useful data here. The only way I can see that it could be breaking is if /usr/local/bin/python (or similar, further up in the PATH) existed. Currently the yum provider runs python with yumhelper itself, so it uses the normal command searching technique to find python in the PATH, rather than using a shebang line in yumhelper. The shebang lines for yum itself on both RHEL 5.10 and 6.5 appear to be /usr/bin/python, so if this was replaced, I don't see that yum would work either (and it didn't, from my test of replacing /usr/bin/python with python26 on RHEL 5.10). I'd suggest having the yum provider default to /usr/bin/python unless it isn't available, in which case use the PATH search mechanism, or simply only use /usr/bin/python. Alternatively as I suggested above, use a shebang line in the yumhelper and replace it based on the platform from the spec file, but I can't see any evidence on my RHEL 5 and 6 boxes that it ever differs and points to a more specific Python version (e.g. 2.4 on EL5). Add Comment Puppet / PUP-1362 Rubyize yumhelper.py to remove dependency on python There are several bugs (bug 11380 being one that triggered this patch) that highlight the fact that the version of python used as the default on a system running puppet can break yumhelper.py. This refactor removes yumhelper.py and moves the functionality into the Yum provider in puppet.
Jira (PUP-2164) require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Title: Message Title Charlie Sharpsteen commented on an issue Re: require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized Also, interesting to note that if JSON is not installed, puppet --version throws an error: # puppet --version /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require': cannot load such file -- json (LoadError) from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /puppetlabs/puppet/lib/puppet/module.rb:3:in `top (required)' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /puppetlabs/puppet/lib/puppet/parser/files.rb:1:in `top (required)' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /puppetlabs/puppet/lib/puppet/parser/templatewrapper.rb:1:in `top (required)' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /puppetlabs/puppet/lib/puppet/parser/scope.rb:6:in `top (required)' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /puppetlabs/puppet/lib/puppet/parser/methods.rb:2:in `top (required)' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /puppetlabs/puppet/lib/puppet/parser/ast/method_call.rb:2:in `top (required)' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /puppetlabs/puppet/lib/puppet/parser/ast.rb:115:in `top (required)' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /puppetlabs/puppet/lib/puppet/parser/parser.rb:11:in `top (required)' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /puppetlabs/puppet/lib/puppet/parser.rb:4:in `top (required)' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /puppetlabs/puppet/lib/puppet.rb:240:in `top (required)' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /puppetlabs/puppet/lib/puppet/util/command_line.rb:12:in `top (required)' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' from /puppetlabs/puppet/bin/puppet:3:in `main' Requiring a JSON parser, let alone the whole module subsystem, to print out the Puppet version seems to indicate some code that could be better factored.
Jira (PUP-2163) yumrepo resource completely broken with 3.5 release
Title: Message Title
Aaron Whiteside commented on an issue
Re: yumrepo resource completely broken with 3.5 release
Guys first off I want to thank you for the quick turn around on this issue, it's really good to know everyone is on top of this stuff!
Ashley Penney For #2 the following resource definition will produce the error I mentioned..
yumrepo{ 'base':
ensure = present,
name = 'my base repo',
baseurl = 'http://someurl',
}
here the title is the repo id I.e. [base] in the repo file, but when the name attribute is specified now the name becomes the repo id, so [my base repo] in the .repo file, and yum complains that there is no actual name=my base repo in .repo file.
so the title should be used for the repo id, and the name attribute in the resource should not override this, it should only be used for the name= value in the .repo file. You may want to introduce another resource attribute to override the title, maybe repo_id = 'something'?
Add Comment
Puppet / PUP-2163
yumrepo resource completely broken with 3.5 release
1. Any attribute that can take 'absent' as a value, either complains about it being invalid or puts the actual text value 'absent' in to the produced repo file. http://docs.puppetlabs.com/references/latest/type.html#yumrepo for example: exclude = absent ends up looking like exclude=absent in the .repo file. 2. yumrepo resource title sho...
Jira (PUP-2172) Add exceptions to http_proxy_{port,host}
Title: Message Title
Kylo Ginsberg created an issue
Puppet / PUP-2172
Add exceptions to http_proxy_{port,host}
Issue Type:
Bug
Affects Versions:
3.5.0
Assignee:
Andy Parker
Components:
Networking Services
Created:
07/Apr/14 10:58 AM
Priority:
Normal
Reporter:
Kylo Ginsberg
We had a PE site which had set the http_proxy_ {port,host}
settings for PMT usage, which had the unintended consequence that all puppet master http connections went through the proxy, including those to the dashboard for node lookups. When something (not yet identified) changed in the network/proxy configuration, these lookups failed causing all agent runs to fail.
This raises the question about whether it ever makes sense for the master to use a proxy for connections to localhost.
We've considered two approaches here: 1) add a new setting for http proxy exclusions. This could be set to, e.g. localhost;*.internal.lan, etc. 2) never using the proxy settings when talking to localhost
There may be some other approaches that would work as well.
Jira (PUP-1991) Usernames 13 characters may not resolve properly from their SID on Windows
Title: Message Title Joshua Cooper commented on an issue Re: Usernames 13 characters may not resolve properly from their SID on Windows This is a problem because we recently added the ability to add domain accounts to local groups, something that users have been asking for a long time. This change is actually in the puppet-win32-ruby repo. Add Comment Puppet / PUP-1991 Usernames 13 characters may not resolve properly from their SID on Windows Due to a bug in an old version of the win32-security gem that we use (0.1.4), an issue cropped up on a customer site when managing groups. For that particular issue, some domain users were being added to a group managed by Puppet, and because the names were greater than 13 characters, an exception was being thrown because the buffer allocated for LookupA... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group
Jira (PUP-2173) puppet config set certname accepts upper-case names
Title: Message Title Kurt Wall created an issue Puppet / PUP-2173 puppet config set certname accepts upper-case names Issue Type: Bug Affects Versions: 3.5.1 Assignee: Unassigned Created: 07/Apr/14 11:06 AM Priority: Normal Reporter: Kurt Wall On CentOS 6 with Puppet 3.5.0, the certname subcommand accepts upper case letters for the certname. If you then try to change the name to lower-case, puppet complains and refuses to do so: # puppet config set certname Jenny.I.Got.Your.Number # puppet config print certname centos6-master.localdomain Error: Could not initialize global default settings: Certificate names must be lower case; see #1168 # cat /etc/puppet/puppet.conf [main] # The Puppet log directory. # The default value is '$vardir/log'. logdir = /var/log/puppet # Where Puppet PID files are kept. # The default value is '$vardir/run'. rundir = /var/run/puppet # Where SSL certificates are kept. # The default value is '$confdir/ssl'. ssldir = $vardir/ssl server = centos6-master.localdomain certname = Jenny.I.Got.Your.Number [agent] # The file in which puppetd stores a list of the classes # associated with the retrieved configuratiion. Can be loaded in # the separate ``puppet`` executable using the ``--loadclasses`` # option. # The default value is '$confdir/classes.txt'. classfile = $vardir/classes.txt # Where puppetd caches the local configuration. An # extension indicating the cache format is added automatically. # The default value is '$confdir/localconfig'. localconfig = $vardir/localconfig # puppet config set
Jira (PUP-1991) Usernames 13 characters may not resolve properly from their SID on Windows
Title: Message Title
Joshua Cooper commented on an issue
Re: Usernames 13 characters may not resolve properly from their SID on Windows
To verify, grab an MSI built by http://jenkins-legacy.delivery.puppetlabs.net/job/Windows%20Polling%20Build%20(stable)/. Make sure the puppet-win32-ruby repo includes the commit referenced in the PR above. Install the MSI, make sure you can add the Guest account to the local Administrators group.
user { 'Guest':
groups = ['Administrators']
}
The Guest SID is not long enough to completely verify this issue, but it will exercise this code path and ensure nothing is broken.
Add Comment
Puppet / PUP-1991
Usernames 13 characters may not resolve properly from their SID on Windows
Due to a bug in an old version of the win32-security gem that we use (0.1.4), an issue cropped up on a customer site when managing groups. For that particular issue, some domain users were being added to a group managed by Puppet, and because the names were greater than 13 characters, an exception was being thrown because the buffer allocated for LookupA...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-509) Document plan and design for environments
Title: Message Title Kenneth Barber commented on an issue Re: Document plan and design for environments I think I'll just resolve this actually, and continue the design around constraints in PDB-455. Add Comment PuppetDB / PDB-509 Document plan and design for environments How environment support works. Design and plan. Review with UI team. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2172) Add exceptions to http_proxy_{port,host}
Title: Message Title
Joshua Cooper commented on an issue
Re: Add exceptions to http_proxy_{port,host}
One fun fact is that the PMT uses two different code paths when making network connections. One path uses open-uri, which relies on environment specific proxy settings. The other path uses puppet's networking code. I think the former is used when searching, the latter when downloading, though I may have those backwards. So we need to make sure that this PR accounts for both scenarios.
This is based off of my recollection from the open source PMT circa 3.3 in the puppet repo. Things may have changed in pe-puppet or in PMT itself that this is no longer an issue.
Add Comment
Puppet / PUP-2172
Add exceptions to http_proxy_{port,host}
We had a PE site which had set the http_proxy_{port,host} settings for PMT usage, which had the unintended consequence that all puppet master http connections went through the proxy, including those to the dashboard for node lookups. When something (not yet identified) changed in the network/proxy configuration, these lookups failed causing all agent runs...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-572) PR (911): new community packages of puppet install in vendorlibdir - aboe76
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-572 PR (911): new community packages of puppet install in vendorlibdir - aboe76 Issue Type: Task Assignee: Unassigned Created: 07/Apr/14 11:28 AM Labels: github Priority: Normal Reporter: gepetto-bot new community packages of puppet install in vendorlibdir Author: Niels Abspoel Company: Github ID: aboe76 Pull Request 911 Discussion Pull Request 911 File Diff Pull Request Description Archlinux future puppet package will be a community repo packages which installs puppet from tarball into vendorlibdir. (webhooks-id: 890f1f6943889b9692247d6b9329bf14)
Jira (PUP-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title
Joshua Cooper commented on an issue
Re: Windows Group and User fail during deletion even though it is successful
I cannot reproduce this issue either:
C:\Windows\system32puppet apply -e user{'FakeTestUser1': ensure = present, password = 'nobodyknowssupersecret123#', }
Notice: Compiled catalog for winagent.cloudapp.net in environment production in 0.17 seconds
Notice: /Stage[main]/Main/User[FakeTestUser1]/ensure: created
Notice: Finished catalog run in 0.64 seconds
C:\Windows\system32puppet apply -e user{'FakeTestUser1': ensure = absent }
Notice: Compiled catalog for winagent.cloudapp.net in environment production in 0.17 seconds
Notice: /Stage[main]/Main/User[FakeTestUser1]/ensure: removed
Notice: Finished catalog run in 0.59 seconds
C:\Windows\system32puppet --version
3.4.3 (Puppet Enterprise 3.2.1)
That said I think the provider should explicitly clear the @user variable in the delete method, so it doesn't assume that nothing else lazily initializes it.
Add Comment
Puppet / PUP-1279
Windows Group and User fail during deletion even though it is successful
This is due to commit being called in the flush method when it should not be. Steps to reproduce: 1. Create a user `puppet apply -e user{'FakeTestUser': ensure = present, password = 'nobodyknowssupersecret', } 2. Delete a user - `puppet apply -e user{'FakeTestUser': ensure = absent, } pre Notice: /User[FakeTestUser]/ensure: removed ...
Jira (PDB-572) PR (911): new community packages of puppet install in vendorlibdir - aboe76
Title: Message Title gepetto-bot commented on an issue Re: PR (911): new community packages of puppet install in vendorlibdir - aboe76 pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-572 PR (911): new community packages of puppet install in vendorlibdir - aboe76 h2. new community packages of puppet install in vendorlibdir * Author: Niels Abspoel * Company: * Github ID: [aboe76|https://github.com/aboe76] * [Pull Request 911 Discussion|https://github.com/puppetlabs/puppetdb/pull/911] * [Pull Request 911 File Diff|https://github.com/puppetlabs/puppetdb/pull/911/files] h2. Pull Request Description Ar... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-572) PR (911): new community packages of puppet install in vendorlibdir - aboe76
Title: Message Title gepetto-bot commented on an issue Re: PR (911): new community packages of puppet install in vendorlibdir - aboe76 pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-572 PR (911): new community packages of puppet install in vendorlibdir - aboe76 h2. new community packages of puppet install in vendorlibdir * Author: Niels Abspoel * Company: * Github ID: [aboe76|https://github.com/aboe76] * [Pull Request 911 Discussion|https://github.com/puppetlabs/puppetdb/pull/911] * [Pull Request 911 File Diff|https://github.com/puppetlabs/puppetdb/pull/911/files] h2. Pull Request Description Ar... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1279) Windows Group and User fail during deletion even though it is successful
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1279 Windows Group and User fail during deletion even though it is successful Change By: Joshua Cooper Assignee: MarkMyers RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-572) PR (911): new community packages of puppet install in vendorlibdir - aboe76
Title: Message Title gepetto-bot commented on an issue Re: PR (911): new community packages of puppet install in vendorlibdir - aboe76 kbarber commented: @pljenkinsro test this please Add Comment PuppetDB / PDB-572 PR (911): new community packages of puppet install in vendorlibdir - aboe76 h2. new community packages of puppet install in vendorlibdir * Author: Niels Abspoel * Company: * Github ID: [aboe76|https://github.com/aboe76] * [Pull Request 911 Discussion|https://github.com/puppetlabs/puppetdb/pull/911] * [Pull Request 911 File Diff|https://github.com/puppetlabs/puppetdb/pull/911/files] h2. Pull Request Description Ar... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-572) PR (911): new community packages of puppet install in vendorlibdir - aboe76
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-572 PR (911): new community packages of puppet install in vendorlibdir - aboe76 Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-572) PR (911): new community packages of puppet install in vendorlibdir - aboe76
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-572 PR (911): new community packages of puppet install in vendorlibdir - aboe76 Change By: Kenneth Barber Sprint: 20140326to20140409 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-207) Puppet Windows Exec providers don't support runas
Title: Message Title Joshua Cooper commented on an issue Re: Puppet Windows Exec providers don't support runas Marking as duplicate of PUP-532, because the latter has the redmine link Add Comment Puppet / PUP-207 Puppet Windows Exec providers don't support runas It appears we don't support configuring a runas user for Windows, it is possible via powershell commands, but being able to have native support inside the provider should be useful and allow feature parity with our linux exec providers. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Change By: Joshua Cooper Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Joshua Cooper commented on an issue Re: Remove win32console gem in ruby 2.0 on windows The easy fix is to just rip out the win32console gem from puppet-win32-ruby and the specific code in Puppet::Util::Colors, once we move to ruby 2. Then run the puppet module tool with --debug, and verify that the unicode box characters are displayed correctly and the colors are correct. Also make sure to try running from powershell and cmd.exe as they have different default background colors. We also need to check facter and hiera to see if they use win32console. The harder fix is to try to support ruby 1.9 and 2.0 simultaneously. Add Comment Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Ruby 2.0 on windows supports ANSI escape sequences, so the win32console gem is unnecessary. Also, ruby 2.0 likely support unicode character output correctly (such as the unicode box characters used in module tool output), so the windows-specific code in `lib/puppet/util/colors.rb` to force wide character output can be removed. See https://github.com/l... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1285) Allow windows to manage hidden applications
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1285 Allow windows to manage hidden applications Change By: Joshua Cooper Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1499) Puppet open source Windows packages should include mcollective
Title: Message Title Matthaus Owens commented on an issue Re: Puppet open source Windows packages should include mcollective The mcollective client is packaged as a gem: https://rubygems.org/gems/mcollective-client Add Comment Puppet / PUP-1499 Puppet open source Windows packages should include mcollective I have a large client that's 50/50 Windows/Linux that's desperately trying to embrace Puppet, but Puppet on Windows always appears to be the proverbial red-headed stepchild. :) Puppet kick is both deprecated and not supported on Windows, and the recommended solution is to use mcollective. Unfortunately, mcollective is not part of the open source MSI, a... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2164) require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Joe Julian: You were seeing something related to JSON loading last Friday, did you come across anything that should be added to this ticket?
Add Comment
Puppet / PUP-2164
require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
We now ship {{rubygems-json}} for EL 6.x as a dependency of Puppet 3.5.0. However, Ruby 1.8.7 does not initialize the Gem search paths by default which leads to the following error: {noformat} # yum install -y puppet-3.5.0-1.el6 # ... much yum output ... # ruby -e ' require puppet ' /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3:in `require':...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-2160) Undocumented hash lookup change in Puppet 3.5.0
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Undocumented hash lookup change in Puppet 3.5.0
Thanks for reporting! I'm looking into this.
Add Comment
Puppet / PUP-2160
Undocumented hash lookup change in Puppet 3.5.0
Consider this code: {noformat} $h = { k1 = value } $v = $h[k2] {noformat} Puppet 3.5.0 sets $v to undef. Earlier versions set $v to the empty string, I believe. (Possibly that isn't true. Possibly it is instead some comparison changes that bites me.) What happens when you look up a non-existing key in a hash should be documented on htt...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2160) Undocumented hash lookup change in Puppet 3.5.0
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Undocumented hash lookup change in Puppet 3.5.0
Used an inline_template to extract the variable value:
$h = { k1 = value }
$v = $h[k2]
notice(inline_template('The value retrieved for $v is: %= scope.lookupvar(v).inspect %'))
Looks like there is no change between 3.4.3 and 3.5.0 when using the standard evaluator, but there is a change when using the future evaluator:
# puppet --version
3.4.3
# puppet apply hash_values.pp
Notice: Scope(Class[main]): The value retrieved for $v is: :undef
Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.04 seconds
Notice: Finished catalog run in 0.15 seconds
# puppet apply hash_values.pp --parser=future
Notice: Scope(Class[main]): The value retrieved for $v is: :undef
Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.80 seconds
Notice: Finished catalog run in 0.15 seconds
# puppet --version
3.5.0
# puppet apply hash_values.pp
Notice: Scope(Class[main]): The value retrieved for $v is: :undef
Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.06 seconds
Notice: Finished catalog run in 0.11 seconds
# puppet apply hash_values.pp --parser=future
Notice: Scope(Class[main]): The value retrieved for $v is: nil
Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.86 seconds
Notice: Finished catalog run in 0.10 seconds
# puppet apply hash_values.pp --parser=future --evaluator=current
Notice: Scope(Class[main]): The value retrieved for $v is: :undef
Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.77 seconds
Notice: Finished catalog run in 0.09 seconds
Per Cederqvist: Were you using the future parser and evaluator?
Add Comment
Jira (PUP-2160) Undocumented hash lookup change in Puppet 3.5.0
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2160 Undocumented hash lookup change in Puppet 3.5.0 Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2160) Undocumented hash lookup change in Puppet 3.5.0
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2160 Undocumented hash lookup change in Puppet 3.5.0 Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen PerCederqvist Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-572) PR (911): new community packages of puppet install in vendorlibdir - aboe76
Title: Message Title gepetto-bot commented on an issue Re: PR (911): new community packages of puppet install in vendorlibdir - aboe76 pljenkinsro commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/344/ Add Comment PuppetDB / PDB-572 PR (911): new community packages of puppet install in vendorlibdir - aboe76 h2. new community packages of puppet install in vendorlibdir * Author: Niels Abspoel * Company: * Github ID: [aboe76|https://github.com/aboe76] * [Pull Request 911 Discussion|https://github.com/puppetlabs/puppetdb/pull/911] * [Pull Request 911 File Diff|https://github.com/puppetlabs/puppetdb/pull/911/files] h2. Pull Request Description Ar... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this
Jira (PDB-572) PR (911): new community packages of puppet install in vendorlibdir - aboe76
Title: Message Title gepetto-bot commented on an issue Re: PR (911): new community packages of puppet install in vendorlibdir - aboe76 aboe76 commented: @kbarber, can you please add this in the next tarball release of puppetdb, would love to create archlinux specific packages, instead of relying on fedora's rpms. Add Comment PuppetDB / PDB-572 PR (911): new community packages of puppet install in vendorlibdir - aboe76 h2. new community packages of puppet install in vendorlibdir * Author: Niels Abspoel * Company: * Github ID: [aboe76|https://github.com/aboe76] * [Pull Request 911 Discussion|https://github.com/puppetlabs/puppetdb/pull/911] * [Pull Request 911 File Diff|https://github.com/puppetlabs/puppetdb/pull/911/files] h2. Pull Request Description Ar... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit
Jira (PUP-2129) Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:
Title: Message Title Daniele Sluijters assigned an issue to Henrik Lindberg I think you or Andy Parker are likely to know what's going on here. Puppet / PUP-2129 Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: Change By: Daniele Sluijters Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2164) require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Title: Message Title Joe Julian commented on an issue Re: require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized Just that it was, indeed, happening from the cli (the following is with 3.5.0rc3 since 3.5.0 was pulled from the repo). # puppet /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3:in `require': no such file to load -- json (LoadError) from /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/files.rb:1:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/files.rb:1 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/templatewrapper.rb:1:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/templatewrapper.rb:1 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/scope.rb:6:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/scope.rb:6 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/methods.rb:2:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/methods.rb:2 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/method_call.rb:2:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/method_call.rb:2 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast.rb:115:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast.rb:115 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/parser.rb:11:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/parser.rb:11 from /usr/lib/ruby/site_ruby/1.8/puppet/parser.rb:4:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser.rb:4 from /usr/lib/ruby/site_ruby/1.8/puppet.rb:240:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet.rb:240 from /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:12:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:12 from /usr/bin/puppet:3:in `require' from /usr/bin/puppet:3 Add Comment Puppet / PUP-2164 require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Jira (PUP-2172) Add exceptions to http_proxy_{port,host}
Title: Message Title
Joshua Partlow updated an issue
Puppet / PUP-2172
Add exceptions to http_proxy_{port,host}
Change By:
Joshua Partlow
WehadaPEsitewhichhadsetthehttp_proxy_ \ {port,host \ }settingsforPMTusage,whichhadtheunintendedconsequencethatallpuppetmasterhttpconnectionswentthroughtheproxy,includingthosetothedashboardfornodelookups.Whensomething(notyetidentified)changedinthenetwork/proxyconfiguration,theselookupsfailedcausingallagentrunstofail.Thisraisesthequestionaboutwhetherit*ever*makessenseforthemastertouseaproxyforconnectionstolocalhost.We'veconsideredtwoapproacheshere:1)addanewsettingforhttpproxyexclusions.Thiscouldbesetto,e.g.{{localhost;*.internal.lan}},etc.2)neverusingtheproxysettingswhentalkingtolocalhostTheremaybesomeotherapproachesthatwouldworkaswell.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2160) Undocumented hash lookup change in Puppet 3.5.0
Title: Message Title
Per Cederqvist commented on an issue
Re: Undocumented hash lookup change in Puppet 3.5.0
Yes, I was using the future parser. (And that implies the future evaluator, in 3.5.0, does it not?)
The change is arguably a good one. I just wish the documentation would be improved so that it states what happens (and that, if you are using the default parser, the semanitcs will change in Puppet 4.)
Add Comment
Puppet / PUP-2160
Undocumented hash lookup change in Puppet 3.5.0
Consider this code: {noformat} $h = { k1 = value } $v = $h[k2] {noformat} Puppet 3.5.0 sets $v to undef. Earlier versions set $v to the empty string, I believe. (Possibly that isn't true. Possibly it is instead some comparison changes that bites me.) What happens when you look up a non-existing key in a hash should be documented on htt...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post
Jira (PUP-2129) Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:
Title: Message Title Sean Edge commented on an issue Re: Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: I'm seeing a message similar to the one described in this bug report: puppet-master[22270]: undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:0x7f2afb395800 on node fw Only found this reference to slurpfunc in all of the files that come with the EL6 RPM from PuppetLabs: [root@fw modules]# rpm -ql puppet | xargs grep slurpfunc /usr/lib/ruby/site_ruby/1.8/puppet/pops/parser/interpolation_support.rb: value,terminator = self.send(slurpfunc) [root@fw modules]# Only happens when using parser=future. Add Comment Puppet / PUP-2129 Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:0x00031a3cb0 at /etc/puppet/external/modules/python/manifests/config.pp:20:31 on node The module where this is happening can be f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2160) Undocumented hash lookup change in Puppet 3.5.0
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Undocumented hash lookup change in Puppet 3.5.0
Yes. Starting with 3.5.x, enabling the future parser also enables the future evaluator by default. Documentation of future parser changes is a bit tricky as many parts are still changing. Also, for this case it is not yet clear whether the change was intentional.
Henrik Lindberg: I see some comments around equating undef to nil in PUP-480, was any of that work included in the future evaluator?
Add Comment
Puppet / PUP-2160
Undocumented hash lookup change in Puppet 3.5.0
Consider this code: {noformat} $h = { k1 = value } $v = $h[k2] {noformat} Puppet 3.5.0 sets $v to undef. Earlier versions set $v to the empty string, I believe. (Possibly that isn't true. Possibly it is instead some comparison changes that bites me.) What happens when you look up a non-existing key in a hash should be documented on htt...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and
Jira (PUP-2160) Undocumented hash lookup change in Puppet 3.5.0
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2160 Undocumented hash lookup change in Puppet 3.5.0 Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2160) Undocumented hash lookup change in Puppet 3.5.0
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2160 Undocumented hash lookup change in Puppet 3.5.0 Change By: Charlie Sharpsteen Assignee: PerCederqvist CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2164) require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-2164
require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Change By:
Charlie Sharpsteen
Wenowship{{rubygems-json}}forEL6.xasadependencyofPuppet3.5.0.However,Ruby1.8.7doesnotinitializetheGemsearchpathsbydefaultwhichleadstothefollowingerror:{noformat}#yuminstall-ypuppet-3.5.0-1.el6#...muchyumoutput...#ruby-e'requirepuppet'/usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3:in`require':nosuchfiletoload--json(LoadError) from/usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3 from/usr/lib/ruby/site_ruby/1.8/puppet/parser/files.rb:1:in`require' from/usr/lib/ruby/site_ruby/1.8/puppet/parser/files.rb:1 from/usr/lib/ruby/site_ruby/1.8/puppet/parser/templatewrapper.rb:1:in`require' from/usr/lib/ruby/site_ruby/1.8/puppet/parser/templatewrapper.rb:1 from/usr/lib/ruby/site_ruby/1.8/puppet/parser/scope.rb:6:in`require' from/usr/lib/ruby/site_ruby/1.8/puppet/parser/scope.rb:6 from/usr/lib/ruby/site_ruby/1.8/puppet/parser/methods.rb:2:in`require' from/usr/lib/ruby/site_ruby/1.8/puppet/parser/methods.rb:2 from/usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/method_call.rb:2:in`require' from/usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/method_call.rb:2 from/usr/lib/ruby/site_ruby/1.8/puppet/parser/ast.rb:115:in`require' from/usr/lib/ruby/site_ruby/1.8/puppet/parser/ast.rb:115 from/usr/lib/ruby/site_ruby/1.8/puppet/parser/parser.rb:11:in`require' from/usr/lib/ruby/site_ruby/1.8/puppet/parser/parser.rb:11 from/usr/lib/ruby/site_ruby/1.8/puppet/parser.rb:4:in`require' from/usr/lib/ruby/site_ruby/1.8/puppet/parser.rb:4 from/usr/lib/ruby/site_ruby/1.8/puppet.rb:240:in`require' from/usr/lib/ruby/site_ruby/1.8/puppet.rb:240 from-e:1:in`require' from-e:1{noformat}The{{puppet}}commanditsselfdoesn'tshowtheerrorasithasadifferententrypoint[thatinitializesrubygems|https://github.com/puppetlabs/puppet/blob/3.5.0/lib/puppet/util/command_line.rb# L15 L7 ]:{noformat}#ruby-e'requirepuppet/util/command_line'{noformat}RequiringthePuppetlibraryworksunder3.4.3:{noformat}#yumremove-yrubygems#yuminstall-ypuppet-3.4.3-1.el6#ruby-e'requirepuppet'{noformat}
Add Comment
Jira (PUP-2129) Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:
Title: Message Title
Henrik Lindberg commented on an issue
Re: Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:
Unsure how that bug could have gone unnoticed. The slurpfunc is indeed undefined - the method was once parameterized, but i now explicit.
value,terminator = self.send(slurpfunc)
Should be a call to an explicit method:
value,terminator = slurp_dqstring()
in this case.
The problem can occur when there is a false variable interpolation start - i.e. when a $ is followed by neither '{' nor a valid variable name - e.g. $$, $., $- etc. This should naturally be fixed. As a work around, it is possible to escape the $.
Add Comment
Puppet / PUP-2129
Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:0x00031a3cb0 at /etc/puppet/external/modules/python/manifests/config.pp:20:31 on node The module where this is happening can be f...
Jira (PUP-2129) Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2129 Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: Change By: Henrik Lindberg Fix Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2160) Undocumented hash lookup change in Puppet 3.5.0
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2160 Undocumented hash lookup change in Puppet 3.5.0 Change By: Charlie Sharpsteen Component/s: DSL Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2160) Undocumented hash lookup change in Puppet 3.5.0
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2160 Undocumented hash lookup change in Puppet 3.5.0 Change By: Charlie Sharpsteen Labels: future-parser Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2165) The fragments directory is empty, cowardly refusing to make empty config files
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-2165
The fragments directory is empty, cowardly refusing to make empty config files
Change By:
Charlie Sharpsteen
concatmodulebreaksformeforfollowingcode {code} nodedefault{concat{'/etc/test.txt':owner='root',group='root',mode='0644'}concat::fragment{'etc_header':target='/etc/test.txt',content=Heyitstest,}concat::fragment{'etc_body':target='/etc/test.txt',content=Heyitstestghdhjhjdh,}} {code} Result: {noformat} Notice:/Stage[main]//Node[default]/Concat[/etc/test.txt]/Exec[concat_/etc/test.txt]/returns:Thefragmentsdirectoryisempty,cowardlyrefusingtomakeemptyconfigfilesError:/var/lib/puppet/concat/bin/concatfragments.sh-o/var/lib/puppet/concat/_etc_test.txt/fragments.concat.out-d/var/lib/puppet/concat/_etc_test.txtreturned1insteadofoneof[0]Error:/Stage[main]//Node[default]/Concat[/etc/test.txt]/Exec[concat_/etc/test.txt]/returns:changefromnotrunto0failed:/var/lib/puppet/concat/bin/concatfragments.sh-o/var/lib/puppet/concat/_etc_test.txt/fragments.concat.out-d/var/lib/puppet/concat/_etc_test.txtreturned1insteadofoneof[0] {noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-2164) require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Title: Message Title
Joe Julian commented on an issue
Re: require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
And this is one of the reasons I hate gems (or multiple package managers of any kind). puppetlabs-ruby installed the rubygems-update gem which was causing that error.
Add Comment
Puppet / PUP-2164
require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
We now ship {{rubygems-json}} for EL 6.x as a dependency of Puppet 3.5.0. However, Ruby 1.8.7 does not initialize the Gem search paths by default which leads to the following error: {noformat} # yum install -y puppet-3.5.0-1.el6 # ... much yum output ... # ruby -e ' require puppet ' /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3:in `require':...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-2164) require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Joe Julian: Do you happen to have RVM installed on that box? If so, does the error persist after rvm use system?
Add Comment
Puppet / PUP-2164
require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
We now ship {{rubygems-json}} for EL 6.x as a dependency of Puppet 3.5.0. However, Ruby 1.8.7 does not initialize the Gem search paths by default which leads to the following error: {noformat} # yum install -y puppet-3.5.0-1.el6 # ... much yum output ... # ruby -e ' require puppet ' /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3:in `require':...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more
Jira (PUP-2164) require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Title: Message Title
Joe Julian commented on an issue
Re: require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
I do not have RVM installed.
Add Comment
Puppet / PUP-2164
require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
We now ship {{rubygems-json}} for EL 6.x as a dependency of Puppet 3.5.0. However, Ruby 1.8.7 does not initialize the Gem search paths by default which leads to the following error: {noformat} # yum install -y puppet-3.5.0-1.el6 # ... much yum output ... # ruby -e ' require puppet ' /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3:in `require':...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-375) Acceptance test Facter from packages
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Facter / FACT-375 Acceptance test Facter from packages Change By: Kylo Ginsberg Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2164) require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Title: Message Title Charlie Sharpsteen commented on an issue Re: require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized puppetlabs-ruby installed the rubygems-update gem which was causing that error. Awesome. Confirmed that this also causes the problem: # puppet --version 3.5.0 # gem install rubygems-update --no-rdoc --no-ri Successfully installed rubygems-update-2.2.2 # update_rubygems RubyGems 2.2.2 installed Installing ri documentation for rubygems-2.2.2 ... much noise trimmed ... # puppet --version /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `gem_original_require': no such file to load -- json (LoadError) from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3 from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/files.rb:1 from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/templatewrapper.rb:1 from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/scope.rb:6 from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/methods.rb:2 from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/method_call.rb:2 from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast.rb:115 from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/parser.rb:11 from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser.rb:4 from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet.rb:240 from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:12 from /usr/bin/puppet:3:in `require' from /usr/bin/puppet:3 Thanks for the additional details!
Jira (PUP-2160) Undocumented hash lookup change in Puppet 3.5.0
Title: Message Title Henrik Lindberg commented on an issue Re: Undocumented hash lookup change in Puppet 3.5.0 The idea is that undefinedness in 4.x should be uniform and not mysterious - i.e. equate nil with undef and have very clear rules. The idea is also to remove the horrible empty string is the same as undef that is used in 3x. (The 3x has multiple ways of handling nil, undef, empty string - semantics are very unclear). In 4x a hash lookup of missing key will produce a nil value. The stat of future parser/evaluator in 3.5.0 is still translating to 3x for all catalog operations, and calls to functions. This means there is some translation going on back and forth between the two, and we have not yet focused explicitly on the undef/nil/empty string issues. We will need to. At the moment we are encountering and fixing this at the points where there handoffs between 3x/4x (both directions) and we may have issues in this area. One such problem surfaced in PUP-1264 . The reported issue puzzles me a bit, there is transformation to 3x when calling a function, and IIRC it is required that undefined values are transformed to empty strings in the function API (but I could be confused because there are so many places where there are exceptions). I will do a bit more exploration to see if there is a difference between the different ways calls are made - i.e. notice $x notice($x) and some other things that come to mind. Add Comment Puppet / PUP-2160 Undocumented hash lookup change in Puppet 3.5.0
Jira (PUP-2160) Undocumented hash lookup change in Puppet 3.5.0
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Undocumented hash lookup change in Puppet 3.5.0
The reported issue puzzles me a bit, there is transformation to 3x when calling a function, and IIRC it is required that undefined values are transformed to empty strings in the function API
During my testing, the change seemed to be that the current evaluator stores the value of $v as :undef in the Scope @symtable}, while the future evaluator stores a nil. I'm not sure if this behavior is a result of the function API.
Add Comment
Puppet / PUP-2160
Undocumented hash lookup change in Puppet 3.5.0
Consider this code: {noformat} $h = { k1 = value } $v = $h[k2] {noformat} Puppet 3.5.0 sets $v to undef. Earlier versions set $v to the empty string, I believe. (Possibly that isn't true. Possibly it is instead some comparison changes that bites me.) What happens when you look up a non-existing key in a hash should be documented on htt...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You
Jira (PUP-2129) Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:
Title: Message Title Henrik Lindberg commented on an issue Re: Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: Ouch, this was a nasty problem, when the function call was fixed, the interpolation of false interpolation starts were not handled correctly. Actually a good thing it completely fails, or it would have produced severely broken string with repeated sections and sections missing. Marking this for 3.5.1, and PR coming shortly. Add Comment Puppet / PUP-2129 Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:0x00031a3cb0 at /etc/puppet/external/modules/python/manifests/config.pp:20:31 on node The module where this is happening can be f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You
Jira (PUP-2164) require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2164 require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2129) Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2129 Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: Change By: Henrik Lindberg Fix Version/s: 3.6.0 Fix Version/s: 3.5.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2160) Undocumented hash lookup change in Puppet 3.5.0
Title: Message Title
Henrik Lindberg commented on an issue
Re: Undocumented hash lookup change in Puppet 3.5.0
the new should store it as nil, we still want a local assignment of nil / undef to shadow an outer scope variable bound to some other value. What puzzles me is that the function notice is called, and it should transform arguments when calling (IIRC). Have to look.
Add Comment
Puppet / PUP-2160
Undocumented hash lookup change in Puppet 3.5.0
Consider this code: {noformat} $h = { k1 = value } $v = $h[k2] {noformat} Puppet 3.5.0 sets $v to undef. Earlier versions set $v to the empty string, I believe. (Possibly that isn't true. Possibly it is instead some comparison changes that bites me.) What happens when you look up a non-existing key in a hash should be documented on htt...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-2129) Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:
Title: Message Title Sean Edge commented on an issue Re: Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: Thanks for your help! Add Comment Puppet / PUP-2129 Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:0x00031a3cb0 at /etc/puppet/external/modules/python/manifests/config.pp:20:31 on node The module where this is happening can be f... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more
Jira (PUP-2174) Returned data from PMT actions should be better specified
Title: Message Title Pieter van de Bruggen created an issue Puppet / PUP-2174 Returned data from PMT actions should be better specified Issue Type: Bug Assignee: Pieter van de Bruggen Created: 07/Apr/14 4:45 PM Priority: Normal Reporter: Pieter van de Bruggen As we build more tooling around the PMT, codifying the structure and form of the returned data structures becomes more important. We should use this ticket as a platform for adding to and restructuring (and ultimately documenting) the existing return values. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2129) Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2129 Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: Change By: Henrik Lindberg Component/s: DSL Story Points: 1 Labels: future-parser Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2129) Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2129 Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: Change By: Henrik Lindberg Sprint: Week2014-4-02to2014-4-09 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1960) realizing an empty array of resources fails in future evaluator
Title: Message Title
Henrik Lindberg commented on an issue
Re: realizing an empty array of resources fails in future evaluator
Merged to master 7c5c209
Add Comment
Puppet / PUP-1960
realizing an empty array of resources fails in future evaluator
The following code runs fine without deprecation warning in old evaluator but fails in 3.5-rc1: {code} realize(File[[]]) {code} {noformat} Error: Evaluation Error: File[] accepts 1 argument. Got 0 on node test.dalen.cloud.spotify.net Error: Evaluation Error: File[] accepts 1 argument. Got 0 on node test.dalen.cloud.spotify.net {noformat}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2150) Specifying proxy = 'absent' or baseurl = 'absent' on any yumrepo resource breaks Puppet 3.5.0.
Title: Message Title
Joshua Hoblitt commented on an issue
Re: Specifying proxy = 'absent' or baseurl = 'absent' on any yumrepo resource breaks Puppet 3.5.0.
I haven't seen it explicitly mentioned but setting absent on mirrorlist is also hosed:
Error: Parameter mirrorlist failed on Yumrepo[epel]: Must be a valid URL at /root/yumtest.pp:9 Wrapped exception: Must be a valid URL
Add Comment
Puppet / PUP-2150
Specifying proxy = 'absent' or baseurl = 'absent' on any yumrepo resource breaks Puppet 3.5.0.
I am on CentOS 6.5 using open-source Puppet 3.5.0. We were previously using Puppet 3.4.3. We are using the epel module from the forge, which specifies a value of 'absent' for all of the yumrepos it manages by default. This does not work in Puppet 3.5.0, causing this error: {noformat} Error: Parameter proxy failed on Yumrepo[epel-testing]: Must be a...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (FACT-376) Status of merged code in facter-2 vs. master
Title: Message Title Adrien Thebo commented on an issue Re: Status of merged code in facter-2 vs. master Jasper Lievisse Adriaanse As part of shipping Facter 2 earlier rather than later we decided to cut the Facter 2.0.1 release from the stable branch rather than master. The idea is that we could just make core API changes for the 2.0.1 release to get it out sooner, and then incrementally pull changes from master into the 2.x release so that we didn't have a massive wall of changes land all at once. https://groups.google.com/forum/#!msg/puppet-dev/Q24GLe6s1_4/tKC_Az3r0EIJ gives a bit more backstory about that. That being said we do need to start pulling changes back from master into the facter-2 branch, and we can definitely start with these. If you want we can repurpose this ticket to track the work of backporting your changes into facter-2 and release them in 2.1.0. How does that sound? Add Comment Facter / FACT-376 Status of merged code in facter-2 vs. master Not a bug per se, but I was wondering about some code I've written last year for Facter that never got included into a release because they were features, not bugfixes. However, looking at the rc1 of facter 2.0.1 I noticed the code was most still not there: https://github.com/puppetlabs/facter/commits?author=jasperla https://github.com/puppetlabs/fa... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
