Jira (PUP-1875) warning for Could not look up qualified variable 'foo::bar' should report the fully-qualified class name being examined
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1875
warning for Could not look up qualified variable 'foo::bar' should report the fully-qualified class name being examined
Issue Type:
New Feature
Assignee:
Unassigned
Created:
06/Mar/14 1:13 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
Consider the following manifest, assuming the classes and such were separated into the correct file structure
prestage { 'init': }
-Stage['main']
class config ($server_id = 1) { ... } class mysql ($server_id = config::$server_id) { ... }
class mysql::config inherits mysql { ... }
Class {'config': }
-Class {'mysql': }
-Class['mysql::config': }/pre
During apply, puppet will report a warning similar to: warning: Scope(Class[Mysql]): Could not look up qualified variable 'config::server_id'; class *config* has not been evaluated at /etc/puppet/modules/mysql/manifests/init.pp:17
What actually is happening is config::$server_id is resolving to ::mysql::config::$server_id rather than the intended ::config::$server_id, and the warning is generated since mysql::config has not yet been evaluated. Furthermore, this only happens if there is a class named mysql::config – if it were named, say, 'mysql::files' instead, the code works as intended.
That's not readily obvious from the warning message,
Jira (PUP-1876) 3.4.3 broke the ability to add provider-specific parameters to built-in types
Title: Message Title Anthony Ryan created an issue Puppet / PUP-1876 3.4.3 broke the ability to add provider-specific parameters to built-in types Issue Type: Bug Affects Versions: 3.4.3 Assignee: Unassigned Created: 06/Mar/14 1:34 AM Priority: Normal Reporter: Anthony Ryan Until 3.4.3 it has been possible to extend built-in types as desired in PUP-1183 by including a lib/puppet/type/package.rb file that expands upon the one included in puppet itself. This allowed provider specific options without using install_options. An example of how this worked previously, it was possible to copy lib/puppet/type/package.rb from puppet into a module as described in http://docs.puppetlabs.com/guides/plugins_in_modules.html and then modifying that file adding parameters as necessary. Add Comment
Jira (PUP-1045) No way to set default tags for exported ressources
Title: Message Title
Kenny Rasschaert updated an issue
Puppet / PUP-1045
No way to set default tags for exported ressources
Change By:
Kenny Rasschaert
Hi,Inourmanifest,wearetryingtosetadefaulttagforallourNagios_host,toachievethisweareaddingthefollowingcodeinthesite.pp: pre {code} Nagios_host{tag='local',} /pre {code} Andthesomewhereelseinourcode,weareexportingtheresourcesandthetryingtocollectthemusingthetag: pre {code} @@nagios_host{'foo':params}Nagios_host|tag=='local'| /pre {code} Theproblemhereisthat,nothingisrealizedbecausethetagisnotexportedproperly,queryingpuppetdbdirectlyshowsthefollowing: pre {code} #curllocalhost:8080/v3/resources/Nagios_host[{parameters:{statusmap_image:os/Ubuntu.png,action_url:/pnp4nagios/graph?host=$HOSTNAME$,notifications_enabled:1,target:/etc/icinga/objects/hosts/host-mon2.example.com.cfg,check_command:check-host-alive,address:192.168.3.129,icon_image:os/Ubuntu.png,notification_period:24x7,max_check_attempts:4,tag:local,hostgroups:default,ensure:present,icon_image_alt:Ubuntu},line:78,file:/etc/puppet/environments/prod/modules/icinga/manifests/collect.pp,exported:true,tags:[example,default,node,mon2.example.com,icingaclient,example::icingaclient,collect,nagios_host,icinga::collect,class,icinga],title:mon2.example.com,type:Nagios_host,resource:806ed13544851d4ede203cbe3a9eceed6964c5ab,certname:mon2.example.com}] /pre {code} Asyoucansee,thelocaltagisonlypresentintheparameterspartandnotittagsIfI'mexplicitlyaddingthetagtotheresourcethatwillbeexported,thetagispresentinbothtagandtagsandtheresourcesareproperlyrealized.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to
Jira (PUP-1045) No way to set default tags for exported ressources
Title: Message Title
Kenny Rasschaert commented on an issue
Re: No way to set default tags for exported ressources
We ended up going with opion A, which was a major pain. If setting resource defaults works for local resources, it should also work for exported resources.
Note that in the curl output above that tag : local, is actually in there, it's just not in the right place!
Add Comment
Puppet / PUP-1045
No way to set default tags for exported ressources
Hi, In our manifest, we are trying to set a default tag for all our Nagios_host, to achieve this we are adding the following code in the site.pp: {code} Nagios_host { tag = 'local', } {code} And the somewhere else in our code, we are exporting the resources and the trying to collect them using the tag: {code} @@nagios_host{'foo': par...
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-1417) puppet parser not order independent
Title: Message Title
Kenny Rasschaert updated an issue
Puppet / PUP-1417
puppet parser not order independent
Change By:
Kenny Rasschaert
Thepuppetparserhasnumberofissuesregardingorder-ofevaluation:*Itdoesnotalwaysensurethatincludedclassesareevaluatedbeforequalifiedvariablesreferringtothemareevaluated.([[LanguageTutorial#qualified-variables]])*Itmayevaluateclassesbeforethescopeinwhichtheyaredefinedisevaluated.*thedefined()functionisunfortunatelydependentontheparseorderoftheconfigurationwhentestingwhetheraresourceisdefined.([[FunctionReference#defined]])AsfarasIunderstandit,theintentisthatpuppetisadeclarativelanguage,inwhichorderofevaluationshouldnotmatter,anditwouldbenicetohavetheseissuesclearedup.Conversely,ifpuppetcontinuestobesomewhatorderdependant,strongermechanismstoprovidecontroloverorder-of-executionoratleastmakeorder-of-executionmorepredictablearenecessary.Ibelievetheformerispreferable.Thefollowingexampledemonstratesthefirsttwooftheseproblems(testedonboth0.24.5andHEAD): pre {code} ###definesomeclassesclassapache{apache_setup{config:}}defineapache_setup($chroot=true,$ssl=false){#sanitychecking,platform-specificdefaults$_chroot=$chroot$_ssl=$sslclassapache_config{$ssl=$_ssl$chroot=$_chroot#morevariableshere}includeapache_config#actuallapachesetupgoeshere}classtrac{case$apache_config::chroot{true:{notice(chroot=true)#dosomething}default:{#dosomethingelsenotice(chroot=${apache_config::chroot})}}}###Nowusewhatwe'vesetupclassapache_sslinheritsapache{#overridethedefaultsApache_setup[config]{ssl=true,chroot=false}}includeapache_ssl#includeapache_configincludetrac /pre {code} Ifthisexampleisexecutedas-is,werecievetheerror,ithasclearlybeenincludedinapache_setup.(issue1above) pre {code} Classapache_confighasnotbeenevaluatedsoitsvariablescannotbereferencedat/tmp/foo:26onnode000AE43B1909 /pre {code} Ifweuncommentthe'includeapache_config'directiveatthebottomoftheexampletoensurethatpuppetseestheclassasbeingincluded,puppetevaluatesapache_config_before_theapacheclassandapache_setupdefine;thescopeinwhichapache_configisdefinedisnotevaluated,andthevariablesitdependsonareevaluatedasemptystrings.(issue2above) pre {code} notice:Scope(Class[trac]):chroot= /pre {code}
Add Comment
Jira (PUP-1877) Cron resource returns succesfully if the user is not cron allowed
Title: Message Title
Pim Polderman created an issue
Puppet / PUP-1877
Cron resource returns succesfully if the user is not cron allowed
Issue Type:
Bug
Affects Versions:
3.4.3
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
06/Mar/14 4:11 AM
Environment:
Red Hat Enterprise Linux Server release 6.5 (Santiago) Puppet 3.4.3
Priority:
Normal
Reporter:
Pim Polderman
The following Puppet code:
cron { somejob : ensure = present, command = $ {data[directory]}
/epic_backup.sh /var/log/epic_backup.log 21, user = pim, hour = [6], minute = [0], weekday = 0-7 }
The /etc/cron.allow file: root
The /etc/cron.deny file is empty
Problem: puppet reports that it has succesfully created the cronjob, but can't be found on the system (crontab -u pim -l). This happens every puppet run, until the cronjob user has changed which is allowed to have cronjobs.
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Klavs Klavsen created an issue PuppetDB / PDB-501 kahadb has 1.1GB log files Issue Type: Bug Assignee: Unassigned Created: 06/Mar/14 7:42 AM Priority: Normal Reporter: Klavs Klavsen rw-r r -. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 rw-r r -. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 rw-r r - 1 puppetdb 29K May 19 2013 db.redo-1369122060204 rw-r r - 1 puppetdb 32K May 21 2013 db.data-1369122060204 rw-r r - 1 puppetdb 32M Mar 6 04:12 db-11955.log rw-r r
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Klavs Klavsen commented on an issue Re: kahadb has 1.1GB log files seems to be caused by https://tickets.puppetlabs.com/browse/PUP-1524 - I've upgraded to puppet 3.4.3 - now I just need to figure out how to clear the queue Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11... 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/groups/opt_out.
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Kenneth Barber commented on an issue Re: kahadb has 1.1GB log files Can you show us a screenshot of your dashboard on http://localhost:8080/? You also haven't provided what version of PuppetDB this is occurring on. If there has been any corruption at some point, KahaDB may have lost its reference to these files. This corruption may go back some time, or it might be recent. You can probably search your logs for anything specific to KahaDB: # grep -i kahadb /var/log/puppetdb/puppetdb.log At the end of the day, if KahaDB doesn't acknowledge the data and there is nothing in the queue it is safe to delete these files: http://docs.puppetlabs.com/puppetdb/1.6/trouble_kahadb_corruption.html Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Kenneth Barber commented on an issue Re: kahadb has 1.1GB log files Klavs Klavsen sorry typed a response without seeing yours. Are you sure that's what is causing it? You can clear the queue just be deleting the files: http://docs.puppetlabs.com/puppetdb/1.6/trouble_kahadb_corruption.html#how-do-i-recover Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Klavs Klavsen commented on an issue Re: kahadb has 1.1GB log files I spoke too soon. the issue cleared itself up, after upgrading to 3.4.3 on the puppetmaster and restarting it. Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11... 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/groups/opt_out.
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Klavs Klavsen commented on an issue Re: kahadb has 1.1GB log files the puppetdb.log was full of: 2014-03-06 16:48:14,273 ERROR [command-proc-65] [puppetdb.command] [bb57eeb6-6026-4ad4-ae13-01878327a47f] [store report] Retrying after attempt 7, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint constraint_resource_events_unique org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint constraint_resource_events_unique at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:363) at com.jolbox.bonecp.PreparedStatementHandle.executeUpdate(PreparedStatementHandle.java:203) at clojure.java.jdbc.internal$do_prepared_return_keys_STAR_$fn__2133.invoke(internal.clj:337) at clojure.java.jdbc.internal$transaction_STAR_.invoke(internal.clj:223) at clojure.java.jdbc.internal$do_prepared_return_keys_STAR_.invoke(internal.clj:337) at clojure.lang.AFn.applyToHelper(AFn.java:163) Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11...
Jira (PUP-1524) Duplicate events since 3.4.0
Title: Message Title Kenneth Barber commented on an issue Re: Duplicate events since 3.4.0 Klavs Klavsen find my answer in the other ticket. (its also not normal form to comment on dead tickets for help . Add Comment Puppet / PUP-1524 Duplicate events since 3.4.0 I'm noticing a series of duplicate events from failed resources being raised by PuppetDB users (see PDB-349) this seems to have been caused by a patch as shown from the bisect here: https://gist.github.com/kbarber/8653842 The net effect is that properties are getting logged twice in the event log for PuppetDB, in the store and even on the console. T... 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/groups/opt_out.
Jira (PUP-1878) PR (2414): Pup 1769 yum provider install options - petems
Title: Message Title gepetto-bot created an issue Puppet / PUP-1878 PR (2414): Pup 1769 yum provider install options - petems Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 06/Mar/14 7:53 AM Labels: github Priority: Normal Reporter: gepetto-bot Pup 1769 yum provider install options Author: Peter Souter Company: Github ID: petems Pull Request 2414 Discussion Pull Request 2414 File Diff Pull Request Description (webhooks-id:
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Kenneth Barber commented on an issue Re: kahadb has 1.1GB log files Klavs Klavsen so the queue was indeed full perhaps? That would make sense. Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11... 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/groups/opt_out.
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Klavs Klavsen commented on an issue Re: kahadb has 1.1GB log files hmm. can't close it as invalid.. which would seem to be the correct status Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11... 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/groups/opt_out.
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Klavs Klavsen commented on an issue Re: kahadb has 1.1GB log files yup. caused by the other issue and luckily upgrading puppet cleared the queue right up Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11... 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/groups/opt_out.
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Klavs Klavsen commented on an issue Re: kahadb has 1.1GB log files I was on puppet 3.4.2 (that's what the issue I linked to regards..). Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11... 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/groups/opt_out.
Jira (PUP-1878) PR (2414): Pup 1769 yum provider install options - petems
Title: Message Title gepetto-bot commented on an issue Re: PR (2414): Pup 1769 yum provider install options - petems puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1878 PR (2414): Pup 1769 yum provider install options - petems h2. Pup 1769 yum provider install options * Author: Peter Souter * Company: * Github ID: [petems|https://github.com/petems] * [Pull Request 2414 Discussion|https://github.com/puppetlabs/puppet/pull/2414] * [Pull Request 2414 File Diff|https://github.com/puppetlabs/puppet/pull/2414/files] h2. Pull Request Description (webhooks-id: b... 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/groups/opt_out.
Jira (PUP-1878) PR (2414): Pup 1769 yum provider install options - petems
Title: Message Title gepetto-bot commented on an issue Re: PR (2414): Pup 1769 yum provider install options - petems petems commented: Just checked the Travis failures, looks like time-out fails? (https://travis-ci.org/puppetlabs/puppet/jobs/20217304 and https://travis-ci.org/puppetlabs/puppet/jobs/20217304) Add Comment Puppet / PUP-1878 PR (2414): Pup 1769 yum provider install options - petems h2. Pup 1769 yum provider install options * Author: Peter Souter * Company: * Github ID: [petems|https://github.com/petems] * [Pull Request 2414 Discussion|https://github.com/puppetlabs/puppet/pull/2414] * [Pull Request 2414 File Diff|https://github.com/puppetlabs/puppet/pull/2414/files] h2. Pull Request Description (webhooks-id: b... 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-1769) yum provider to support install_options
Title: Message Title
Peter Souter commented on an issue
Re: yum provider to support install_options
Follow up PR here: https://github.com/puppetlabs/puppet/pull/2414
Add Comment
Puppet / PUP-1769
yum provider to support install_options
I'd like to this, yet I can't at the moment: {code} package { 'foo': install_options = [ '-x', 'bar' ] } {code}
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/groups/opt_out.
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Kenneth Barber commented on an issue Re: kahadb has 1.1GB log files Klavs Klavsen yeah, I just said Done none of the statuses available seem to make sense for this kind of thing. Oh well. Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11... 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/groups/opt_out.
Jira (PUP-1765) puppet apply --modulepath not respected when /etc/puppet/environments/production exists
Title: Message Title Tony Vu assigned an issue to Tony Vu Puppet / PUP-1765 puppet apply --modulepath not respected when /etc/puppet/environments/production exists Change By: Tony Vu Assignee: TonyVu 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/groups/opt_out.
Jira (PUP-1879) Library load tests in features should clear rubygems path cache
Title: Message Title
Dominic Cleal created an issue
Puppet / PUP-1879
Library load tests in features should clear rubygems path cache
Issue Type:
Improvement
Assignee:
Dominic Cleal
Components:
Types and Providers
Created:
06/Mar/14 10:35 AM
Environment:
EL6
Priority:
Normal
Reporter:
Dominic Cleal
When using features (i.e. puppet/features/ and puppet/util/features) to determine whether a Ruby library exists, rubygem paths should be reloaded on each test. When gems are installed (including as RPMs), the paths are usually unique per gem, so have to be refreshed else the library load will continue to fail until the Puppet process is restarted.
Here's an example (relies on EL6):
# cat test.pp
package { 'rubygem-foreman_api':
ensure = present,
} -
foreman_smartproxy { 'test': }
# puppet module install -i . theforeman/foreman
Preparing to install into /root ...
Downloading from http://forge.puppetlabs.com ...
Installing -- do not interrupt ...
/root
└─┬ theforeman-foreman (v2.0.1)
├─┬ puppetlabs-apache (v0.11.0)
│ └── puppetlabs-concat (v1.1.0-rc1)
├─┬ puppetlabs-postgresql (v3.3.2)
│ ├── puppetlabs-apt (v1.4.2)
│ └── puppetlabs-firewall (v1.0.2)
├── puppetlabs-stdlib (v4.1.0)
└── theforeman-concat_native (v1.3.0)
# rpm -ivh
Jira (PUP-1880) PR (230): [WIP] - apenney
Title: Message Title gepetto-bot created an issue Puppet / PUP-1880 PR (230): [WIP] - apenney Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 06/Mar/14 10:49 AM Labels: github Priority: Normal Reporter: gepetto-bot [WIP] Author: Ashley Penney ashley.pen...@puppetlabs.com Company: Puppetlabs Github ID: apenney Pull Request 230 Discussion Pull Request 230 File Diff Pull Request Description This is a work in progress PR to modernize some of the tests inside stdlib and free it from the
Jira (PUP-1881) Windows agents don't respect a 0 runinterval
Title: Message Title Joshua Cooper created an issue Puppet / PUP-1881 Windows agents don't respect a 0 runinterval Issue Type: Bug Assignee: Unassigned Created: 06/Mar/14 10:58 AM Labels: windows Priority: Normal Reporter: Joshua Cooper The configuration reference states, 'Note that a runinterval of 0 means “run continuously” rather than “never run.”' But on Windows, the value of 0 is conflated with an empty value, and will be ignored, causing the agent to default to 1800 seconds: https://github.com/puppetlabs/puppet/blob/master/ext/windows/service/daemon.rb#L69-L72 Add Comment
Jira (PUP-1766) Make systemd the default provider for RHEL7
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-1766 Make systemd the default provider for RHEL7 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/groups/opt_out.
Jira (FACT-376) Status of merged code in facter-2 vs. master
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-376 Status of merged code in facter-2 vs. master Issue Type: Task Affects Versions: 2.0.1 Assignee: Adrien Thebo Created: 06/Mar/14 11:31 AM Priority: Normal Reporter: Jasper Lievisse Adriaanse 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/facter/commits/facter-2?author=jasperla So what's the status of that? Will they be merged into facter-2 or ..? Add Comment
Jira (HI-223) Hiera 'deeper' merge knockout only knocks out from closest array
Title: Message Title Andrew Noonan created an issue Hiera / HI-223 Hiera 'deeper' merge knockout only knocks out from closest array Issue Type: Bug Assignee: Unassigned Created: 06/Mar/14 1:05 PM Priority: Normal Reporter: Andrew Noonan Consider the following hiera structure: host.yaml stuff: - ---alpha - ---beta - gamma datacenter.yaml stuff: - alpha global.yaml stuff: - beta Where the hierarchy is: :hierarchy: - host - datacenter - global What you'd expect is that a hiera_hash() call from the host matching the host.yaml is that alpha and beta would be knocked out, leaving just gamma in the resulting array. Instead, both gamma and beta are left in. This seems to be because the deep merge is performed in the most specific to least specific order, and the deep_merge gem will delete from the source array knockout
Jira (PUP-1220) dynamic variable lookup works in templates
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-1220 dynamic variable lookup works in templates 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/groups/opt_out.
Jira (PUP-1882) defaultfor method for providers should be allowed to be specified multiple times
Title: Message Title redmine.exporter created an issue Puppet / PUP-1882 defaultfor method for providers should be allowed to be specified multiple times Issue Type: New Feature Assignee: Unassigned Created: 06/Mar/14 1:43 PM Labels: redmine Priority: Normal Reporter: redmine.exporter You should be able to specify multiple defaultfor statements in providers: pre defaultfor :operatingsystem = :redhat, :lsbdistrelease = [2.1, 3, 4] defaultfor :operatingsystem = :oel, :operatingsystemrelease = [4, 5] /pre Add Comment
Jira (PUP-1882) defaultfor method for providers should be allowed to be specified multiple times
Title: Message Title Pieter Hollants commented on an issue Re: defaultfor method for providers should be allowed to be specified multiple times Right now, providers can only match on ONE particular combination on facts, eg. ONE specific version of CentOS. Considering that eg. many Linux distributions have begun to or will use systemd (RHEL7, SLES12, openSUSE 12.2 and later), there is a serious need to be able to do more complex defaultfor expressions, eg. with boolean operators along the lines of the following pseudo-code (osfamily == archlinux) || (operatingsystem == opensuse operatingsystemrelease = 12.2) The alternative would be to introduce special facts for each of these complex checks, eg. a has_systemd fact, but then we'd have to pollute facts space with possibly dozens of facts that might trigger on rare setups only... Add Comment Puppet / PUP-1882 defaultfor method for providers should be allowed to be specified multiple times You should be able to specify multiple defaultfor statements in providers: pre defaultfor :operatingsystem = :redhat, :lsbdistrelease = [2.1, 3, 4] defaultfor :operatingsystem = :oel, :operatingsystemrelease = [4, 5] /pre This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1124) Zypper package provider needs $HOME set to access username/password-protected repos
Title: Message Title
Pieter Hollants commented on an issue
Re: Zypper package provider needs $HOME set to access username/password-protected repos
Any progress on this one?
Add Comment
Puppet / PUP-1124
Zypper package provider needs $HOME set to access username/password-protected repos
zypper, the command used to install packages on SUSE distributions, supports package repositories that requires a username and a password to be accessed. Unlike other comparable utilities for other distributions, zypper stores such credentials information in a file in {{$HOME, $HOME/.zypp/credentials.cat}} to be precise. However, this requires the environ...
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/groups/opt_out.
Jira (PUP-389) Support ruby 2.0 x64 on windows
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-389 Support ruby 2.0 x64 on windows Change By: Joshua Cooper Summary: Supportruby 2.0 x64onwindows 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/groups/opt_out.
Jira (PUP-1883) PR (2416): (maint) Add rake task for parallelizing specs. - peterhuene
Title: Message Title gepetto-bot created an issue Puppet / PUP-1883 PR (2416): (maint) Add rake task for parallelizing specs. - peterhuene Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 06/Mar/14 2:21 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Add rake task for parallelizing specs. Author: Peter Huene peterhu...@gmail.com Company: Puppet Labs Github ID: peterhuene Pull Request 2416 Discussion Pull Request 2416 File Diff Pull Request Description Adding a
Jira (HI-223) Hiera 'deeper' merge knockout only knocks out from closest array
Title: Message Title
Andrew Noonan updated an issue
Hiera / HI-223
Hiera 'deeper' merge knockout only knocks out from closest array
Change By:
Andrew Noonan
Considerthefollowinghierastructure:host.yaml{code}stuff:alphabeta-gamma{code}datacenter.yaml{code}stuff:-alpha{code}global.yaml{code}stuff:-beta{code}Wherethehierarchyis:{code}:hierarchy:-host-datacenter-global{code}Whatyou'dexpectisthatahiera_hash()callfromthehostmatchingthehost.yamlisthatalphaandbetawouldbeknockedout,leavingjustgammaintheresultingarray.Instead,bothgammaandbetaareleftin.Thisseemstobebecausethedeepmergeisperformedinthemostspecifictoleastspecificorder,andthedeep_mergegemwilldelete knockoutvalues fromthesourcearray knockoutvalues iftheymatchdestinationvaluesor not eveniftheydon'tmatchanything .Becausetheyareremovedfromthearray,whenthenextarrayismerged(anarraythatmaycontainavaluetobeknockedout),theknockoutvalueisgone.Thislikelyalsoaddsaside-effect(Ihaven'ttested,butitseemscorrect)thatifavalueexistsmultipletimesinvariousfiles,itisonlyknockedoutintheclosestarraytotheknockoutvalue,andisthenpromptlyaddedbackinwhenseenagain.Apossiblesolutiontothiswouldbetoreversetheprocessingorderfordeep_mergesothattheknockoutsareprocessedfromleastspecifictomorespecific,butIsuspecttherewillbetonsofothersideeffects. Anotherpossibilityistoalwayskeepknockoutvaluesthroughoutthemerging,andthenhaveafinalpassafterthefinalmergetoremovetheknockoutvalues.Thiswouldallowforprocessingtocontinueinthecurrentorder.
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
Jira (PUP-744) Pool HTTPS connections
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-744 Pool HTTPS connections Change By: Kylo Ginsberg Fix Version/s: 4.0.0 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/groups/opt_out.
Jira (PUP-876) upstart service operating system confine should include redhat and centos
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-876 upstart service operating system confine should include redhat and centos 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-1884) Move puppet dependencies on windows into the puppet repo
Title: Message Title Joshua Cooper created an issue Puppet / PUP-1884 Move puppet dependencies on windows into the puppet repo Issue Type: Task Assignee: Unassigned Created: 06/Mar/14 3:27 PM Labels: windows Priority: Normal Reporter: Joshua Cooper Currently the logic for puppet dependencies on Windows is kept in the jenkins job used to build the MSI. This ticket is about moving that logic into the puppet repo. As outlined in RE-876: Add ext/windows_versions.yaml to puppet repo listing dependencies on facter, hiera, puppet-win32-ruby, and MSI artifacts (icons) in puppet_for_the_win. Also mcollective and plugins for PE. This will replace what is currently specified in the jenkins job when composing the MSI The one tricky part is that the puppet_for_the_win rake task currently assumes it is given all dependency info up front. The task will need to be reworked so that we clone and checkout a particular puppet commit, and then introspect the dependencies in puppet. Add Comment
Jira (PUP-1884) Move puppet dependencies on windows into the puppet repo
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1884 Move puppet dependencies on windows into the puppet repo Change By: Kylo Ginsberg Sprint: Week2014-3-12to2014-3-19 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-24) (#7643) Add WMI Operating System facts
Title: Message Title Joshua Cooper commented on an issue Re: (#7643) Add WMI Operating System facts See also https://github.com/openstack-hyper-v/puppet-windows_common/tree/master/lib/facter Add Comment Facter / FACT-24 (#7643) Add WMI Operating System facts Figure out which facts from WMI OperatingSystem would make sense to include in facter, e.g. caption, country code, etc. Also which of them match existing facts, and which would be new facts. 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-876) upstart service operating system confine should include redhat and centos
Title: Message Title
Joshua Partlow commented on an issue
Re: upstart service operating system confine should include redhat and centos
After talking with Adrien, we confirmed that you can start/stop an upstart service with manifest code that specifies the upstart provider.
So, given:
[root@gk0q9dhjekmei6y ~]# facter osfamily operatingsystemrelease
operatingsystemrelease = 6.3
osfamily = RedHat
[root@gk0q9dhjekmei6y ~]# puppet resource service vmware-tools --param=provider
service { 'vmware-tools':
ensure = 'stopped',
enable = 'true',
provider = 'upstart',
}
Applying this:
[root@gk0q9dhjekmei6y ~]# cat vmware.pp
service { 'vmware-tools':
ensure = running,
provider = upstart,
}
Uses upstart commands like so:
[root@gk0q9dhjekmei6y ~]# puppet apply vmware.pp --debug
...
Notice: Compiled catalog for gk0q9dhjekmei6y.delivery.puppetlabs.net in environment production in 0.11
seconds
...
Debug: Loaded state in 0.00 seconds [7/1931]
Info: Applying configuration version '1394151016'
Debug: Executing '/sbin/status vmware-tools'
Debug: Executing '/sbin/start vmware-tools'
Notice: /Stage[main]/Main/Service[vmware-tools]/ensure: ensure changed 'stopped' to 'running'
Debug: /Stage[main]/Main/Service[vmware-tools]: The container Class[Main] will propagate my refresh event
Info: /Stage[main]/Main/Service[vmware-tools]: Unscheduling refresh on Service[vmware-tools]
...
Notice: Finished catalog run in 0.87 seconds
...
And we end up with a running service:
[root@gk0q9dhjekmei6y ~]# puppet resource service vmware-tools --param=provider
service { 'vmware-tools':
ensure = 'running',
enable = 'true',
provider = 'upstart',
}
Specifying the provider is required because 'Redhat' is the default, sysvinit service, and there isn't currently a good way to distinguish between a sysvinit service that doesn't exist versus isn't running, so we don't have a fallback to upstart.
Jira (PUP-876) upstart service operating system confine should include redhat and centos
Title: Message Title Joshua Partlow commented on an issue Re: upstart service operating system confine should include redhat and centos Michael Stahnke is there anything else you'd like to test for this issue (or someone else I should ping about it?) Add Comment Puppet / PUP-876 upstart service operating system confine should include redhat and centos RedHat EL 6 and Centos 6 both use upstart for init. The upstart service type should be able to be used on those systems as well. I have done some very minor testing to make sure it at least works to ensure services are running and stopped. 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-1846) PR (2410): File content diffing should respect loglevel - wfarr
Title: Message Title Andrew Parker assigned an issue to Andrew Parker Puppet / PUP-1846 PR (2410): File content diffing should respect loglevel - wfarr Change By: Andrew Parker Assignee: AndrewParker 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-1846) PR (2410): File content diffing should respect loglevel - wfarr
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1846 PR (2410): File content diffing should respect loglevel - wfarr Change By: Andrew 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-1839) Puppet device results in SSL stack too deep error
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-1839 Puppet device results in SSL stack too deep error 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-1883) PR (2416): (maint) Add rake task for parallelizing specs. - peterhuene
Title: Message Title gepetto-bot commented on an issue Re: PR (2416): (maint) Add rake task for parallelizing specs. - peterhuene petems commented: Would it be an idea to use https://github.com/grosser/parallel_tests or is this to prevent external dependancies? Add Comment Puppet / PUP-1883 PR (2416): (maint) Add rake task for parallelizing specs. - peterhuene h2. (maint) Add rake task for parallelizing specs. * Author: Peter Huene peterhu...@gmail.com * Company: Puppet Labs * Github ID: [peterhuene|https://github.com/peterhuene] * [Pull Request 2416 Discussion|https://github.com/puppetlabs/puppet/pull/2416] * [Pull Request 2416 File Diff|https://github.com/puppetlabs/puppet/pull/2416/files] h2. Pull R... 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-1697) hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode
Could you give an example of how this Host entry is being defined? It looks like there are a few layers of classes and/or defined types that are wrapping the 'node2' definition.
Add Comment
Puppet / PUP-1697
hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode
The hosts resource doesn't trigger refresh of the /etc/hosts file when puppet agent is running in daemon mode. If a restart of the puppet agent is triggered, the changes are made. {code} Feb 11 11:17:59 node1 puppet-agent[5806]: Finished catalog run in 0.42 seconds Feb 11 11:20:59 node1 puppet-agent[5993]: Finished catalog run in 0.42 seconds Feb 11...
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-1883) PR (2416): (maint) Add rake task for parallelizing specs. - peterhuene
Title: Message Title gepetto-bot commented on an issue Re: PR (2416): (maint) Add rake task for parallelizing specs. - peterhuene peterhuene commented: There's two problems we have with parallel_tests. The first is we have too many spec files and they get passed on rpsec's command line, causing problems on Windows due to command line length limitations. Hence the existence of the 'rspec_runner' script which takes a single file as input containing a list of spec files to run. The second is that parallel_tests will run all the specs in a single process if you give it a process count of 1. What we'd like for Travis, since we're seeing rspec getting killed for rather insane memory usage, is recycle the process every X number of tests (with these changes, the rspec process gets recycled after every 1000 specs). Add Comment Puppet / PUP-1883 PR (2416): (maint) Add rake task for parallelizing specs. - peterhuene h2. (maint) Add rake task for parallelizing specs. * Author: Peter Huene peterhu...@gmail.com * Company: Puppet Labs * Github ID: [peterhuene|https://github.com/peterhuene] * [Pull Request 2416 Discussion|https://github.com/puppetlabs/puppet/pull/2416] * [Pull Request 2416 File Diff|https://github.com/puppetlabs/puppet/pull/2416/files] h2. Pull R... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1846) PR (2410): File content diffing should respect loglevel - wfarr
Title: Message Title Andrew Parker updated an issue Puppet / PUP-1846 PR (2410): File content diffing should respect loglevel - wfarr Change By: Andrew Parker Sprint: Week2014-3-05to2014-3-12 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-1883) PR (2416): (maint) Add rake task for parallelizing specs. - peterhuene
Title: Message Title gepetto-bot commented on an issue Re: PR (2416): (maint) Add rake task for parallelizing specs. - peterhuene petems commented: Cool, just curious, looking forward to more stable Travis :+1: Add Comment Puppet / PUP-1883 PR (2416): (maint) Add rake task for parallelizing specs. - peterhuene h2. (maint) Add rake task for parallelizing specs. * Author: Peter Huene peterhu...@gmail.com * Company: Puppet Labs * Github ID: [peterhuene|https://github.com/peterhuene] * [Pull Request 2416 Discussion|https://github.com/puppetlabs/puppet/pull/2416] * [Pull Request 2416 File Diff|https://github.com/puppetlabs/puppet/pull/2416/files] h2. Pull R... 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-1846) PR (2410): File content diffing should respect loglevel - wfarr
Title: Message Title Andrew Parker commented on an issue Re: PR (2410): File content diffing should respect loglevel - wfarr Rebased, fixed up commit message and merged in as 73d917 Add Comment Puppet / PUP-1846 PR (2410): File content diffing should respect loglevel - wfarr h2. File content diffing should respect loglevel * Author: Will Farrington wf...@github.com * Company: GitHub * Github ID: [wfarr|https://github.com/wfarr] * [Pull Request 2410 Discussion|https://github.com/puppetlabs/puppet/pull/2410] * [Pull Request 2410 File Diff|https://github.com/puppetlabs/puppet/pull/2410/files] h2. Pull Request Descriptio... 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-1399) Reboot acceptance test fails because it can't find the Reboot type
Title: Message Title
Joshua Cooper commented on an issue
Re: Reboot acceptance test fails because it can't find the Reboot type
Acceptance has been reliably passing, closing this.
Add Comment
Puppet / PUP-1399
Reboot acceptance test fails because it can't find the Reboot type
Puppet Module - Reboot Acceptance failed because puppet cannot find the Reboot type (https://jenkins.puppetlabs.com/job/Puppet%20Module%20-%20Reboot%20Acceptance/config=windows-2003r2-i386.cfg,label=acc-coord/23/console): {code} Windows Reboot Module - Reboot when Finished * Reboot After Finishing Complete Catalog e0o1l1fzagldyso (w2k3r2) $ env ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-150) Facter timeouts reap all subprocesses thus confusing Puppet
Title: Message Title Joshua Cooper updated an issue Facter / FACT-150 Facter timeouts reap all subprocesses thus confusing Puppet Change By: Joshua Cooper Assignee: JoshuaCooper 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 This is an issue when running as a non-Adminstrator user on Windows as you need a way to escalate privileges 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-207) Puppet Windows Exec providers don't support runas
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-207 Puppet Windows Exec providers don't support runas Change By: Joshua Cooper Assignee: JoshuaCooper 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-741) Stop reading entire file contents into memory (IO.binread)
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-741 Stop reading entire file contents into memory (IO.binread) Change By: Joshua Cooper Assignee: JoshuaCooper 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-1186) puppet module tool on windows will (sometimes) create a PaxHeader directory
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1186 puppet module tool on windows will (sometimes) create a PaxHeader directory Change By: Joshua Cooper Assignee: JoshuaCooper 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-1204) Puppet Master (3.2.2/CentOs) - Puppet Agent (3.2.2/W2008)
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1204 Puppet Master (3.2.2/CentOs) - Puppet Agent (3.2.2/W2008) Change By: Joshua Cooper Assignee: JoshuaCooper JasperLievisseAdriaanse 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-1204) Puppet Master (3.2.2/CentOs) - Puppet Agent (3.2.2/W2008)
Title: Message Title Joshua Cooper commented on an issue Re: Puppet Master (3.2.2/CentOs) - Puppet Agent (3.2.2/W2008) Jasper Lievisse Adriaanse if this issue is resolved for you, can you close the ticket? Add Comment Puppet / PUP-1204 Puppet Master (3.2.2/CentOs) - Puppet Agent (3.2.2/W2008) Hello, I am experiencing this issue. Could not retrieve domain: undefined method `gsub' for nil:NilClass Could not retrieve domain: undefined method `gsub' for nil:NilClass Could not retrieve domain: undefined method `gsub' for nil:NilClass Error: Failed to apply catalog: SSL_connect SYSCALL returned=5 errno=0 state=SSL v2/v3 read server hello 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-574) NTFS ACL module
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-574 NTFS ACL module Change By: Joshua Cooper Assignee: JoshuaCooper RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1372) with strict variable lookup option there is no way to check if var is defined
Title: Message Title Tony Vu assigned an issue to Tony Vu Puppet / PUP-1372 with strict variable lookup option there is no way to check if var is defined Change By: Tony Vu Assignee: TonyVu 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-1765) puppet apply --modulepath not respected when /etc/puppet/environments/production exists
Title: Message Title
Tony Vu commented on an issue
Re: puppet apply --modulepath not respected when /etc/puppet/environments/production exists
All test cases described in the PR have been manually verified.
Add Comment
Puppet / PUP-1765
puppet apply --modulepath not respected when /etc/puppet/environments/production exists
This appears to be a strange condition since the new directory environments work went in. When /etc/puppet/environments/production exists, puppet apply stops obeying --modulepath and instead attempts to look up the module in /etc only. For example: {noformat} # mkdir /etc/puppet/environments/production # puppet module install -i /tmp/test saz/ntp ...
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-1563) PR Puppet::ModuleTool::Applications::Installer::resolve_install_conflicts can get in a recursive loop
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1563 PR Puppet::ModuleTool::Applications::Installer::resolve_install_conflicts can get in a recursive loop Change By: Joshua Cooper Summary: PR Puppet::ModuleTool::Applications::Installer::resolve_install_conflictscangetinarecursiveloop 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-1563) PR (2322) Puppet::ModuleTool::Applications::Installer::resolve_install_conflicts can get in a recursive loop
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1563 PR (2322) Puppet::ModuleTool::Applications::Installer::resolve_install_conflicts can get in a recursive loop Change By: Joshua Cooper Summary: PR (2322) Puppet::ModuleTool::Applications::Installer::resolve_install_conflictscangetinarecursiveloop 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-851) Manage propagation
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-851 Manage propagation Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1839) Puppet device results in SSL stack too deep error
Title: Message Title Joshua Partlow commented on an issue Re: Puppet device results in SSL stack too deep error Merged to master in b4c499d Add Comment Puppet / PUP-1839 Puppet device results in SSL stack too deep error h1. Background Chris Spence and myself are working on a new module to manage F5 load balancers (version 11.5 IOS) as numerous clients have been asking for Puppet Labs to update this module. We will be handing over this work to the Module Team when they have time to continue the work, as Chris and I have limited time to spend on the development. h1 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-1596) Make modulepath, manifest, and config_version configurable per-environment
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-1596 Make modulepath, manifest, and config_version configurable per-environment Change By: Joshua Partlow Assignee: AndrewParker 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-1883) PR (2416): (maint) Add rake task for parallelizing specs. - peterhuene
Title: Message Title gepetto-bot commented on an issue Re: PR (2416): (maint) Add rake task for parallelizing specs. - peterhuene puppetcla commented: CLA signed by all contributors. Add Comment Puppet / PUP-1883 PR (2416): (maint) Add rake task for parallelizing specs. - peterhuene h2. (maint) Add rake task for parallelizing specs. * Author: Peter Huene peterhu...@gmail.com * Company: Puppet Labs * Github ID: [peterhuene|https://github.com/peterhuene] * [Pull Request 2416 Discussion|https://github.com/puppetlabs/puppet/pull/2416] * [Pull Request 2416 File Diff|https://github.com/puppetlabs/puppet/pull/2416/files] h2. Pull R... 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 (HI-224) PR (184): (#127) Allow escaping %{...} in hiera data so that hiera does not try to... - ChrisPortman
Title: Message Title
gepetto-bot created an issue
Hiera / HI-224
PR (184): (#127) Allow escaping %{...} in hiera data so that hiera does not try to... - ChrisPortman
Issue Type:
Task
Assignee:
Adrien Thebo
Components:
Community
Created:
06/Mar/14 6:09 PM
Labels:
github
Priority:
Normal
Reporter:
gepetto-bot
(#127) Allow escaping %{...} in hiera data so that hiera does not try to... * Author: * Company: * Github ID: ChrisPortman * Pull Request 184 Discussion * Pull Request 184 File Diff h2. Pull Request Description ... perform a replacement This change allows the escaping of %{...} with %%{...} so that the result is literally '%{...}'
It also support escaping the escape eg: var = 'value of var'
% {var} : 'value of var' %%{literal} : '%{literal}' %%%{var}
: '%value of var' {literal} : '%%{literal}
'
(webhooks-id: bb076e24d28f19d663b7bfe26d16036f)
Jira (PUP-30) Support Puppet Templates
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-30 Support Puppet Templates Change By: Henrik Lindberg Sprint: Week2014-3-05to2014-3-12 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-30) Support Puppet Templates
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-30 Support Puppet Templates Change By: Henrik Lindberg Fix Version/s: 3.6.0 Fix Version/s: 3.5.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-28) Add heredoc support in future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-28 Add heredoc support in future parser Change By: Henrik Lindberg Fix Version/s: 3.6.0 Fix Version/s: 3.5.0 Assignee: AndrewParker 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-28) Add heredoc support in future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-28 Add heredoc support in future parser Change By: Henrik Lindberg Sprint: Week2014-3-05to2014-3-12 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-30) Support Puppet Templates
Title: Message Title Henrik Lindberg commented on an issue Re: Support Puppet Templates For functional review (smoketest) puppet apply --parser future '$x = world notice epp(foo.epp)' --templatedir . And place the foo.epp template file in the current directory with the following content: Hello %= $x %! For an inline epp version of the same, change foo.epp to foo.pp with the following content: $x = world notice inline_epp(@(END)) Hello %= $x %! END and then run: puppet apply --parser future foo.pp Add Comment Puppet / PUP-30 Support Puppet Templates Add support for Puppet Templates. This is implemented and is based on the work in Puppet Heredoc. One feature (syntax checking) is not implemented, and is just like the support for Heredoc waiting for functionality to handle plugins (which is basically the same mechanism as data in modules) https://github.com/puppetlabs/puppet/pull/1660
Jira (PUP-28) Add heredoc support in future parser
Title: Message Title Henrik Lindberg commented on an issue Re: Add heredoc support in future parser See PUP-30 for functional review tests using heredoc (and templates). Add Comment Puppet / PUP-28 Add heredoc support in future parser https://github.com/puppetlabs/puppet/pull/1659 Adds support for heredoc but there is an ugly 'wart' on it that needs to be resolved before it can be merged. 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-1879) Library load tests in features should clear rubygems path cache
Title: Message Title Luke Chavers commented on an issue Re: Library load tests in features should clear rubygems path cache Related reading: http://alcy.github.io/2012/11/21/handling-gem-dependencies-in-custom-puppet-providers/ .. and .. https://groups.google.com/d/msg/foreman-users/u3peMoo2FA0/RxirwvkEmBgJ https://github.com/puppetlabs/puppet/pull/2415 .. and .. https://projects.puppetlabs.com/issues/17747 https://projects.puppetlabs.com/issues/6907 https://projects.puppetlabs.com/issues/7316 https://projects.puppetlabs.com/issues/14822 Add Comment Puppet / PUP-1879 Library load tests in features should clear rubygems path cache When using features (i.e. puppet/features/ and puppet/util/features) to determine whether a Ruby library exists, rubygem paths should be reloaded on each test. When gems are installed (including as RPMs), the paths are usually unique per gem, so have to be refreshed else the library load will continue to fail until the Puppet process is restarted. H... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
