Jira (FACT-746) ipaddress fact doesn't function properly with dummy interfaces (linux)
Title: Message Title Bjrn Henkel created an issue Facter / FACT-746 ipaddress fact doesn't function properly with dummy interfaces (linux) Issue Type: Bug Affects Versions: FACT 2.2.0 Assignee: Eric Sorenson Created: 23/Oct/14 11:17 PM Environment: Linux, RHEL 6.5 Priority: Normal Reporter: Bjrn Henkel There is the old Bug #3713 that describes the issue. The ipaddress of the dummy device is returned as by the ipaddress fact, which is not what one expects. ifconfig dummy0 Link encap:Ethernet HWaddr 36:D9:A2:FF:6D:92 inet addr:10.6.0.143 Bcast:10.6.0.255 Mask:255.255.255.0 inet6 addr: fe80::34d9:a2ff:feff:6d92/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:210 (210.0 b) eth0 Link encap:Ethernet HWaddr E4:11:5B:AB:D3:06 inet addr:192.168.102.86 Bcast:192.168.102.255 Mask:255.255.255.0 inet6 addr: fe80::e611:5bff:feab:d306/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5879523 errors:0 dropped:0 overruns:0 frame:0 TX packets:4151717 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:611191340 (582.8 MiB) TX bytes:5553146297 (5.1 GiB) lo Link encap:Local Loopback inet
Jira (PUP-3516) Puppet breaks on 32-bit Windows XP
Title: Message Title
Bjrn Stabel commented on an issue
Re: Puppet breaks on 32-bit Windows XP
I originally encountered this bug, daenney kindly reported this for me. I did some research into what causes the problem and it seems that win32-eventlog:13d817f2a5 introduced it. That commit is between releases 0.5.3 and 0.6.0 of that gem. puppet:ac8d4e257f bumped the gem version from 0.5.3 to 0.6.1.
so what needs to happen in order to solve this issue is:
win32-eventlog: Make Wow64DisableWow64FsRedirection optional (again?)
win32-eventlog: Release a new version
puppet: bump the gem version to that new version
Until then, a workaround is not to upgrade to 3.6.2 if you're on a 32 bit system before vista
Add Comment
Puppet / PUP-3516
Puppet breaks on 32-bit Windows XP
The new win32-eventlog version that Puppet is using is looking for {{Wow64DisableWow64FsRedirection}}. However, that only exists in {{kernel.dll}} on Windows XP 64bit Edition and Vista and upwards. This currently results in Puppet exploding on 'normal' Windows XP: {noformat} C:/Programme/Puppet Labs/Puppet/sys/ruby/lib/ruby/gems/1.9.1/gems/ffi-1.9
Jira (PUP-3528) yumrepo needs sslverify value to be capitalized
Title: Message Title
cristi falcas created an issue
Puppet / PUP-3528
yumrepo needs sslverify value to be capitalized
Issue Type:
Bug
Assignee:
Unassigned
Created:
24/Oct/14 1:58 AM
Priority:
Normal
Reporter:
cristi falcas
Defining this results in catalog compilation failure:
yumrepo { 'repo': baseurl = 'some_repo', descr = 'repo', enabled = 1, gpgcheck = 0, mirrorlist = absent, priority = 1, failovermethod = priority, metadata_expire = 60, sslcacert = absent, sslclientcert = absent, sslclientkey = absent, sslverify = false, }
Failed to apply catalog: Parameter sslverify failed on Yumrepo[optymyze]: Invalid value false. Valid values are absent. Valid values match /True|False/. at /etc/puppet/environments/production/modules/manage_repos/manifests/enable_repos.pp:20 Wrapped exception: Invalid value false. Valid values are absent. Valid values match /True|False/.
It seems that sslverify can only be set capitalized.
Add Comment
Jira (PUP-3529) --genconfig generates deprecated settings
Title: Message Title Robert Hyerle created an issue Puppet / PUP-3529 --genconfig generates deprecated settings Issue Type: Bug Affects Versions: PUP 3.7.1 Assignee: Kylo Ginsberg Attachments: puppet.agent.out, puppet.conf Components: Client, Puppet Server Created: 24/Oct/14 2:20 AM Environment: Darwin 13.4.0, Ubuntu 14.04 Priority: Minor Reporter: Robert Hyerle Use of the --genconfig command line option generates several settings for options that have been deprecated (even the generated puppet.conf file notes in the comments that the option has been deprecated). Running puppet (server or client) then emits deprecation warnings. These generated option settings are not needed (the generated values are the defaults). Fix: comment out the generated settings. I.e. the --genconfig output should prepend each deprecated option
Jira (PUP-3530) Pass array to custom define fails
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-3530
Pass array to custom define fails
Issue Type:
Bug
Assignee:
Unassigned
Created:
24/Oct/14 2:57 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
I'm trying to pass a simple array to a custom define and fails with error:
`err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship source Foo::Map[idbazip2.2.2.2] `
I think that code is very correct:
`$foo = [ {id = bar, ip = 1.1.1.1}
, {id = baz, ip = 2.2.2.2}
]`
`foo::map {$foo:}`
`define foo::map () { notify {$name['id']: } } `
Add Comment
Jira (PUP-3531) --genconf generates options that are error prone to configure manually using defaults
Title: Message Title Robert Hyerle created an issue Puppet / PUP-3531 --genconf generates options that are error prone to configure manually using defaults Issue Type: Bug Affects Versions: PUP 3.7.1 Assignee: Kylo Ginsberg Attachments: client_yaml.grep, puppet.conf, vardir.grep Components: Client, Puppet Server Created: 24/Oct/14 3:01 AM Environment: Ubuntu 14.04, Darwin 13.4.0, all? Priority: Minor Reporter: Robert Hyerle The puppet configuration logic with its systems of defaults works fairly well. The scheme of important and safe to change options as explained on https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html is a good way to approach the multitude of possible settings. In particular, settings such server and vardir have potential impacts for many other settings because these root
Jira (PUP-3530) Pass array to custom define fails
Title: Message Title
Wannes Van Causbroeck commented on an issue
Re: Pass array to custom define fails
Hello,
we've recently upgraded upgraded to puppet 3.7.1 and we still experience this issue. I'm retrieving an array from hiera. Each element contains a hash with two elements. I pass this array to a custom resource. Our puppet master is 3.7.1 and we have two clients: one 3.7.1 and the others 2.7.20. The puppet runs fails on the newer client 2/3. On the old version it fails 1/10. If i run the old version with option: --preferred_serialization_format yaml puppet runs fine.
Add Comment
Puppet / PUP-3530
Pass array to custom define fails
I'm trying to pass a simple array to a custom define and fails with error: `err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship source Foo::Map[idbazip2.2.2.2] ` I think that code is very correct:`$foo = [{id = bar, ip = 1.1.1.1}, {id = baz, ...
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
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title B W updated an issue Puppet / PUP-3500 Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings. Change By: B W Assignee: AaronArmstrong 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-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title Bill W updated an issue Puppet / PUP-3500 Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings. Change By: Bill W Assignee: AaronArmstrong 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-3494) Could not create vm on azure
Title: Message Title Bill W commented on an issue Re: Could not create vm on azure You should report this issue to https://github.com/MSOpenTech/azure-puppet/issues Add Comment Puppet / PUP-3494 Could not create vm on azure I`m trying to automate an infrasctructure using puppet. I could create puppet master an slave using azure portal. Right now, I`m trying to create slaves using puppet cli. I`m following the description from github link. First, I`ve generated my pem file using the following command: openssl req \ -x509 -nodes -days 365 \ -newkey rsa:1024 -keyout... 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-3494) Could not create vm on azure
Title: Message Title Bill W commented on an issue Re: Could not create vm on azure You should report the issue to https://github.com/MSOpenTech/azure-puppet/issues Add Comment Puppet / PUP-3494 Could not create vm on azure I`m trying to automate an infrasctructure using puppet. I could create puppet master an slave using azure portal. Right now, I`m trying to create slaves using puppet cli. I`m following the description from github link. First, I`ve generated my pem file using the following command: openssl req \ -x509 -nodes -days 365 \ -newkey rsa:1024 -keyout... 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-3531) --genconf generates options that are error prone to configure manually using defaults
Title: Message Title Robert Hyerle updated an issue Puppet / PUP-3531 --genconf generates options that are error prone to configure manually using defaults Change By: Robert Hyerle Thepuppetconfigurationlogicwithitssystemsofdefaultsworksfairlywell.Theschemeofimportantandsafetochangeoptionsasexplainedonhttps://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.htmlisagoodwaytoapproachthemultitudeofpossiblesettings.Inparticular,settingssuchserverandvardirhavepotentialimpactsformanyothersettingsbecausetheserootsettingspropagatedownasdefaultsforothersettings.Itisimportanttopreservethispropagation/inheritanceandoverridethesubsequentoptionsonlywhentheydon'tfollowthedefaultrule.Otherwise,achangeatthetoplevelwillnotbepropagatedasexpected:inthebestcase,theadminwillhavetocarefullyandmanuallycheckalltheothersettingsinpuppet.conftoinsurecorrectbehavior.Notethatthegeneratedpuppet.conffileisverylong.Unfortunately,thegeneratedpuppet.conf*doesnot*followtheabovelogic:itexplicitlysetsseveraloptions(10's)tothedefaultvaluemeaningthatwhensomeonechangesahigherlevelsetting(e.g.vardirorserver),thedefaultsdonotpropagate.Oneexample:vardirisregularlyusedasadefaultstartingpointformanyotherdirectories(seetheattachedfilevardir.greptoseehowmanytimesitappearsinthegeneratedpuppet.conffile.However,changingitmay,ormaynot,changethesubsequentvalues(thegeneratedpuppet.conffileisinconsistentinthismanneraswell).Here,theclientyamldirsettingwouldnotbeimpacted(seeattachedclient_yaml.grep)asonemightexpect.Theadminneedstosearchthroughandfindeveryplacewherethingsshould(normally)change.Explicitoverridesshouldbejustthat:explicitandoverrides.Fix:--genconfoutputshouldnotexplicitlysetvaluesthathavereasonabledefaults.Thesepotentialsettingsshouldremainintheconffileascomments.E.g.theclient_yamlsettingshouldbecome:#Thedefaultvalueis'$vardir/client_yaml'.#clientyamldir=/var/lib/puppet/client_yaml Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3531) --genconf generates options that are error prone to configure manually using defaults
Title: Message Title Robert Hyerle updated an issue Puppet / PUP-3531 --genconf generates options that are error prone to configure manually using defaults Change By: Robert Hyerle Thepuppetconfigurationlogicwithitssystemsofdefaultsworksfairlywell.Theschemeofimportantandsafetochangeoptionsasexplainedonhttps://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.htmlisagoodwaytoapproachthemultitudeofpossiblesettings.Inparticular,settingssuchserverandvardirhavepotentialimpactsformanyothersettingsbecausetheserootsettingspropagatedownasdefaultsforothersettings.Itisimportanttopreservethispropagation/inheritanceandoverridethesubsequentoptionsonlywhentheydon'tfollowthedefaultrule.Otherwise,achangeatthetoplevelwillnotbepropagatedasexpected:inthebestcase,theadminwillhavetocarefullyandmanuallycheckalltheothersettingsinpuppet.conftoinsurecorrectbehavior.Notethatthegeneratedpuppet.conffileisverylong.Unfortunately,thegeneratedpuppet.conf*doesnot*followtheabovelogic:itexplicitlysetsseveraloptions(10's)tothedefaultvaluemeaningthatwhensomeonechangesahigherlevelsetting(e.g.vardirorserver),thedefaultsdonotpropagate.Oneexample:vardirisregularlyusedasadefaultstartingpointformanyotherdirectories(seetheattachedfilevardir.greptoseehowmanytimesitappearsinthegeneratedpuppet.conffile.However,changingitmay -- , ormaynot -- , changethesubsequentvalues(thegeneratedpuppet.conffileisinconsistentinthismanneraswell).Here,theclientyamldirsettingwouldnotbeimpacted(seeattachedclient_yaml.grep)asonemightexpect.Theadminneedstosearchthroughandfindeveryplacewherethingsshould(normally)change.Explicitoverridesshouldbejustthat:explicitandoverrides.Fix:--genconfoutputshouldnotexplicitlysetvaluesthathavereasonabledefaults.Thesepotentialsettingsshouldremainintheconffileascomments.E.g.theclient_yamlsettingshouldbecome:#Thedefaultvalueis'$vardir/client_yaml'.#clientyamldir=/var/lib/puppet/client_yaml Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3531) --genconf generates options that are error prone to configure manually using defaults
Title: Message Title Robert Hyerle updated an issue Puppet / PUP-3531 --genconf generates options that are error prone to configure manually using defaults Change By: Robert Hyerle Thepuppetconfigurationlogicwithitssystemsofdefaultsworksfairlywell.Theschemeofimportantandsafetochangeoptionsasexplainedonhttps://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.htmlisagoodwaytoapproachthemultitudeofpossiblesettings.Inparticular,settingssuchserverandvardirhavepotentialimpactsformanyothersettingsbecausetheserootsettingspropagatedownasdefaultsforothersettings.Itisimportanttopreservethispropagation/inheritanceandoverridethesubsequentoptionsonlywhentheydon'tfollowthedefaultrule.Otherwise,achangeatthetoplevelwillnotbepropagatedasexpected:inthebestcase,theadminwillhavetocarefullyandmanuallycheckalltheothersettingsinpuppet.conftoinsurecorrectbehavior.Notethatthegeneratedpuppet.conffileisverylong.Unfortunately,thegeneratedpuppet.conf*doesnot*followtheabovelogic:itexplicitlysetsseveraloptions(10's)tothedefaultvaluemeaningthatwhensomeonechangesahigherlevelsetting(e.g.vardirorserver),thedefaultsdonotpropagate.Oneexample:vardirisregularlyusedasadefaultstartingpointformanyotherdirectories(seetheattachedfilevardir.greptoseehowmanytimesitappearsinthegeneratedpuppet.conffile.However,changingitmay,ormaynot,changethesubsequentvalues(thegeneratedpuppet.conffileisinconsistentinthismanneraswell).Here,theclientyamldirsettingwouldnotbeimpacted(seeattachedclient_yaml.grep)asonemightexpect.Theadminneedstosearchthroughandfindeveryplacewherethingsshould(normally)change.Explicitoverridesshouldbejustthat:explicitandoverrides.Fix:--genconfoutputshouldnotexplicitlysetvaluesthathavereasonabledefaults.Thesepotentialsettingsshouldremainintheconffileascomments.E.g.theclient_yamlsettingshouldbecome: #Thedefaultvalueis'$vardir/client_yaml'.#clientyamldir=/var/lib/puppet/client_yaml Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-996) Duplicate declaration during compilation with default parameters and future parser
Title: Message Title Brian Kane created an issue PuppetDB / PDB-996 Duplicate declaration during compilation with default parameters and future parser Issue Type: Bug Affects Versions: module-4.0.0 Assignee: Unassigned Components: Module Created: 24/Oct/14 6:59 AM Environment: Puppet master: 3.7.2 Puppet agent: 3.7.1 Master/agent OS: RHEL6.4 parser = future Priority: Normal Reporter: Brian Kane When using the puppetdb module with default parameters and the future parser, the following error is thrown during compilation: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Exec[validate postgres connection for localhost/puppetdb]
Jira (PDB-996) Duplicate declaration during compilation with default parameters and future parser
Title: Message Title
Kenneth Barber commented on an issue
Re: Duplicate declaration during compilation with default parameters and future parser
Can you provide an adequate manifest only example to prove this, without an ENC? What I mean is, reproduce in your site.pp or equivalent and show us this code please.
Add Comment
PuppetDB / PDB-996
Duplicate declaration during compilation with default parameters and future parser
When using the puppetdb module with default parameters and the future parser, the following error is thrown during compilation: {noformat} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Exec[validate postgres connection for localhost/puppetd...
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-947) Export from puppetdb (HSQLDB) abnormally slow
Title: Message Title jon yeargers commented on an issue Re: Export from puppetdb (HSQLDB) abnormally slow (sorry - I realize this has been resolved) Issue with export file based on your recommendations: puppetdb import --infile pdb.tgz java.lang.IllegalStateException: Unable to find export metadata file 'puppetdb-bak/export-metadata.json' in archive 'pdb.tgz' at com.puppetlabs.puppetdb.cli.import$parse_metadata$fn__11684.invoke (import.clj:46) com.puppetlabs.puppetdb.cli.import$parse_metadata.invoke (import.clj:43) com.puppetlabs.puppetdb.cli.import$_main.doInvoke (import.clj:152) clojure.lang.RestFn.invoke (RestFn.java:421) clojure.lang.Var.invoke (Var.java:383) clojure.lang.AFn.applyToHelper (AFn.java:156) clojure.lang.Var.applyTo (Var.java:700) clojure.core$apply.invoke (core.clj:624) com.puppetlabs.puppetdb.core$run_command.invoke (core.clj:87) com.puppetlabs.puppetdb.core$_main.doInvoke (core.clj:95) clojure.lang.RestFn.invoke (RestFn.java:436) clojure.lang.Var.invoke (Var.java:388) clojure.lang.AFn.applyToHelper (AFn.java:160) clojure.lang.Var.applyTo (Var.java:700) clojure.core$apply.invoke (core.clj:624) clojure.main$main_opt.invoke (main.clj:315) clojure.main$main.doInvoke (main.clj:420) clojure.lang.RestFn.invoke (RestFn.java:482) clojure.lang.Var.invoke (Var.java:401) clojure.lang.AFn.applyToHelper (AFn.java:171) clojure.lang.Var.applyTo (Var.java:700) clojure.main.main (main.java:37) What I did: 1. create 'pdb.tgz' per included instructions 2. change 'puppetdb/database.ini' to point to postgresql instance 3, run above command Verify missing piece(s): tar -ztvf pdb.tgz | grep puppetdb-bak # Add Comment PuppetDB / PDB-947 Export from puppetdb (HSQLDB) abnormally slow
Jira (PDB-996) Duplicate declaration during compilation with default parameters and future parser
Title: Message Title
Brian Kane commented on an issue
Re: Duplicate declaration during compilation with default parameters and future parser
site.pp
node 'XXX' {
class { 'puppetdb': }
class { 'puppetdb::master::config':
puppet_service_name = 'httpd',
}
}
Add Comment
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title
Aaron Armstrong commented on an issue
Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Joshua Partlow is this in pe_puppet now?
Add Comment
Puppet / PUP-3500
Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
When using directory environments, if you have a setting like 'certname' set in puppet.conf (either in main, or in the section that will correspond to the run_mode of your application), setting values will be cached for the production environment which will return legacy default values for manifest and modulepath. {noformat} jpartlow@percival:~/work/p...
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-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Christopher Price commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. Wayne Warren are you in the loop on this? Joshua Partlow you should ping at least Wayne Warren and potentially just jump into the pe-green team if you are having any issues related to puppet server running OSS Puppet acceptance tests. We've spent lots and lots of time on this and can probably recognize most of these failure cases pretty quickly. Add Comment Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments. 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-947) Export from puppetdb (HSQLDB) abnormally slow
Title: Message Title
Wyatt Alt commented on an issue
Re: Export from puppetdb (HSQLDB) abnormally slow
jon yeargers I'm wondering if you have the right pdb.tgz there.
The tarball should extract into a directory called puppetdb-bak – if that's not happening and the export seemed to run successfully you might be using the pdb.tgz you sent us earlier, which would be the wrong one. I just extracted my tarball from your data and export-metadata.json contains this content: { timestamp : 2014-10-22T22:44:52.822Z, command-versions : { replace-catalog : 3, store-report : 2 }
}
If you ls the extracted directory it should be easy to see. Here's what it should look like:
[~/Desktop] $ ls puppetdb-bak/ catalogs export-metadata.json facts reports
Add Comment
PuppetDB / PDB-947
Export from puppetdb (HSQLDB) abnormally slow
Started 'puppetdb export --outfile file' on 2014/10/07 06:30 am. As of 2014/10/09 04:00 am it has dumped ~75 / 110 servers. Expected: it shouldn't take this long. This means the data that will be imported into Postgres (ultimate goal of this exercise) will be 48 hours out of date. System: Dell PE 2950 8 Core / 32Gb RAM / CentOS 6.5 x64 Insta...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title
Joshua Partlow commented on an issue
Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Aaron Armstrong Yes, this was merged in yesterday morning, and Moses Mendoza got a pe build composed and smoked. The tests have run twice last for pe-puppet last night and have stabilized around 41 failures (details in PUP-3277)
Add Comment
Puppet / PUP-3500
Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
When using directory environments, if you have a setting like 'certname' set in puppet.conf (either in main, or in the section that will correspond to the run_mode of your application), setting values will be cached for the production environment which will return legacy default values for manifest and modulepath. {noformat} jpartlow@percival:~/work/p...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PDB-996) Duplicate declaration during compilation with default parameters and future parser
Title: Message Title Kenneth Barber commented on an issue Re: Duplicate declaration during compilation with default parameters and future parser Huh, thats weird, when I tried to replicate I get a very different error from postgresql: root@puppetdb1:/etc/puppet/manifests# puppet agent -t --noop Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Error: Could not retrieve catalog from remote server: Error 400 on SERVER: This Type-Name is not productive. A non productive construct may only be placed last in a block/sequence at /etc/puppet/modules/postgresql/manifests/server/database.pp:73:3 on node puppetdb1.vm Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Have you seen this yourself? Add Comment
Jira (PDB-996) Duplicate declaration during compilation with default parameters and future parser
Title: Message Title
Brian Kane commented on an issue
Re: Duplicate declaration during compilation with default parameters and future parser
Yes, that's a bug in the 4.0.0 version of the postgresql module with the future parser. The fix is pushed to the master branch already. https://github.com/puppetlabs/puppetlabs-postgresql/commit/289de739c3c92e58652529456a4c8cff5fb2eecd
I applied the change manually to get around this.
Add Comment
PuppetDB / PDB-996
Duplicate declaration during compilation with default parameters and future parser
When using the puppetdb module with default parameters and the future parser, the following error is thrown during compilation: {noformat} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Exec[validate postgres connection for localhost/puppetd...
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
Jira (PUP-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Joshua Partlow commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. Wayne Warren do you have any ideas on the check_woy_cache_works.rb failure? Josh Cooper has a theory that it's a beaker issue with the curl command used to check for a running puppet master not using tls, but I can't understand why it would certain around this one test. Neither I nor, Eric Thompson can reproduce (I just tried again last night on the same pooler node that failed in the test, running that exact same commands). Add Comment Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments. 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-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Wayne Warren commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. Christopher Price No, I haven't heard about this. Add Comment Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments. 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-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title
Aaron Armstrong commented on an issue
Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
John Duarte - the fix for this is in builds now - see Josh's comment above.
Add Comment
Puppet / PUP-3500
Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
When using directory environments, if you have a setting like 'certname' set in puppet.conf (either in main, or in the section that will correspond to the run_mode of your application), setting values will be cached for the production environment which will return legacy default values for manifest and modulepath. {noformat} jpartlow@percival:~/work/p...
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-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title
John Duarte commented on an issue
Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Aaron Armstrong thanks. QA has been instructed to use build 3.4.0-rc1-1709-gc89b548 which has this change in it.
Add Comment
Puppet / PUP-3500
Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
When using directory environments, if you have a setting like 'certname' set in puppet.conf (either in main, or in the section that will correspond to the run_mode of your application), setting values will be cached for the production environment which will return legacy default values for manifest and modulepath. {noformat} jpartlow@percival:~/work/p...
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-947) Export from puppetdb (HSQLDB) abnormally slow
Title: Message Title Wyatt Alt commented on an issue Re: Export from puppetdb (HSQLDB) abnormally slow If you didn't, you'll also need to restart PuppetDB after changing the config and before running the import, but that isn't the issue you're having here. Add Comment PuppetDB / PDB-947 Export from puppetdb (HSQLDB) abnormally slow Started 'puppetdb export --outfile file' on 2014/10/07 06:30 am. As of 2014/10/09 04:00 am it has dumped ~75 / 110 servers. Expected: it shouldn't take this long. This means the data that will be imported into Postgres (ultimate goal of this exercise) will be 48 hours out of date. System: Dell PE 2950 8 Core / 32Gb RAM / CentOS 6.5 x64 Insta... 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-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Christopher Price commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. I know that Wayne Warren and/or Jeremy Barlow hit some transient failures on check_woy_cache in the past. Not sure what the solution was. Add Comment Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments. 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-996) Duplicate declaration during compilation with default parameters and future parser
Title: Message Title Kenneth Barber commented on an issue Re: Duplicate declaration during compilation with default parameters and future parser Oh good to know they have fixed that in upstream, that was my primary concern. So in regards to your issue, the bad news is I can't immediately replicate the problem on my reasonably clean machine: root@puppetdb1:/etc/puppet/manifests# cat /etc/puppet/routes.yaml --- master: facts: terminus: puppetdb cache: yaml root@puppetdb1:/etc/puppet/manifests# cat /etc/puppet/puppet.conf [main] parser=future logdir=/var/log/puppet
Jira (PUP-3505) Future parser handling undef's incorrectly
Title: Message Title Aaron Armstrong commented on an issue Re: Future parser handling undef's incorrectly Henrik Lindberg Moses Mendoza is this PR in a PE build now? CC Joshua Partlow Add Comment Puppet / PUP-3505 Future parser handling undef's incorrectly Trying to run the future parser with PE I ran in to the following error https://github.com/puppetlabs/puppetlabs-pe_staging/blob/3.2.x/manifests/file.pp#L18 The manifest above is failing because the future parser is overriding the variable $environment with the top-level puppet variable ($environment) set to 'production' in our case. The error I got ... 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-3530) Pass array to custom define fails
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Pass array to custom define fails
Wannes Van Causbroeck: Which operating system and ruby version are you using?
Add Comment
Puppet / PUP-3530
Pass array to custom define fails
I'm trying to pass a simple array to a custom define and fails with error: `err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship source Foo::Map[idbazip2.2.2.2] ` I think that code is very correct:`$foo = [{id = bar, ip = 1.1.1.1}, {id = baz, ...
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-3530) Pass array to custom define fails
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3530 Pass array to custom define fails Change By: Charlie Sharpsteen Assignee: WannesVanCausbroeck 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-3530) Pass array to custom define fails
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-3530
Pass array to custom define fails
Change By:
Charlie Sharpsteen
I'mtryingtopassasimplearraytoacustomdefineandfailswitherror: ` {code} err:Couldnotretrievecatalogfromremoteserver:Couldnotinternfrompson:Couldnotconvertfrompson:CouldnotfindrelationshipsourceFoo::Map[idbazip2.2.2.2] ` {code} Ithinkthatcodeisverycorrect: {code} ` $foo=[{id=bar,ip=1.1.1.1},{id=baz,ip=2.2.2.2}] ` ` foo::map{$foo:} ` ` definefoo::map(){notify{$name['id']:}} ` {code}
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-3530) Pass array to custom define fails
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Pass array to custom define fails
Also, are you trying to pass an array of hashes to a defined type? Could you give an example of the Puppet code that is failing?
Add Comment
Puppet / PUP-3530
Pass array to custom define fails
I'm trying to pass a simple array to a custom define and fails with error: {code} err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship source Foo::Map[idbazip2.2.2.2] {code} I think that code is very correct: {code} $foo = [{id = bar, ip = 1.1.1.1},...
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-3479) Windows ffi dependency fails for Ruby 2.1.3
Title: Message Title Michael Smith updated an issue Puppet / PUP-3479 Windows ffi dependency fails for Ruby 2.1.3 Change By: Michael Smith Ruby2.1.xwasreleasedonWindowsforthefirsttimewithRuby2.1.3inSeptember:https://www.ruby-forum.com/topic/5768030RunningRubyfromsourceonWindowswithRuby2.1.3fails,becauseffi1.9.3isn'tcompatiblewithRuby2.1.x.Theffidependencyneedstobeupdatedtorequireffi1.9.5+ onallourprojectsthatdependonit:atleastpuppet,facter,hiera . 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-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Joshua Partlow commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. Second run from last night, showed that that the check_woy_cache_works and selinux issues are stable (same pattern), and the transient issues moved around as expected. Interestingly the installer itself failed to start the master on ubuntu 1004: /Stage[main]/Puppet_enterprise::Profile::Mcollective::Peadmin/Puppet_enterprise::Mcollective::Client[peadmin]/Puppet_enterprise::Mcollective::Client::User[peadmin]/Pe_accounts::User[peadmin]/Pe_accounts::Home_dir[/var/lib/peadmin]/File[/var/lib/peadmin/.ssh/authorized_keys]/ensure: created Notice: Finished catalog run in 22.20 seconds !! ERROR: The puppet master service failed to start within 120 seconds; unable to proceed Add Comment Puppet / PUP-3277
Jira (FACT-747) Improve Solaris $::ipaddress accuracy
Title: Message Title Ryan Anderson created an issue Facter / FACT-747 Improve Solaris $::ipaddress accuracy Issue Type: Improvement Affects Versions: FACT 2.2.0, FACT 1.7.5 Assignee: Eric Sorenson Created: 24/Oct/14 9:49 AM Environment: Solaris 8/9/10 on SPARC, observed on numerous SPARC models Priority: Normal Reporter: Ryan Anderson On Solaris, in the ifconfig output, NICS show up as driverinstance (eg bge0, bge1, hme0, etc). In facter, the $::ipaddress fact is derived from the NIC that is alphabetically first, but this is not always accurate. For example, interface ge0 has the IP of the hostname, but bge0 may be configured for a storage or cluster network and it will show up as $::ipaddress since 'bge' comes before 'ge', even though this is wrong. Here is a real-world example of mine, ipaddress_bge0 is on a non-routable admin network and ipaddress_nxge0 is the IP of the server in DNS: ipaddress = 192.168.1.17 ipaddress_bge0 = 192.168.1.17 ipaddress_lo0 = 127.0.0.1 ipaddress_nxge0 = 10.19.1.3 ipaddress_nxge1 = 10.19.1.4 ipaddress_sppp0 = 192.168.224.3 Can the behavior be changed on Solaris so $::ipaddress equals the IP that matches the hostname?
Jira (PUP-3505) Future parser handling undef's incorrectly
Title: Message Title Moses Mendoza commented on an issue Re: Future parser handling undef's incorrectly Aaron Armstrong this is not in a build yet. It appears to be waiting on merge of https://github.com/puppetlabs/puppet/pull/3229, and then merge to pe-puppet. Add Comment Puppet / PUP-3505 Future parser handling undef's incorrectly Trying to run the future parser with PE I ran in to the following error https://github.com/puppetlabs/puppetlabs-pe_staging/blob/3.2.x/manifests/file.pp#L18 The manifest above is failing because the future parser is overriding the variable $environment with the top-level puppet variable ($environment) set to 'production' in our case. The error I got ... 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-996) Duplicate declaration during compilation with default parameters and future parser
Title: Message Title
Brian Kane commented on an issue
Re: Duplicate declaration during compilation with default parameters and future parser
I was just able to reproduce with the vagrant puppetlabs/centos-6.5-64-nocm box. I deployed it, installed puppet/puppet-server 3.7.2. Installed the puppetlabs/puppetdb modules, applied the fix to the postgresql module, and reproduced it. I notice your test box appears to be Debian based (dpkg), whereas I'm using RHEL/CentOS.
[root@localhost manifests]# cat site.pp
node 'localhost.corp.microstrategy.com' {
class { 'puppetdb': }
class { 'puppetdb::master::config': }
}
[root@localhost manifests]# cat /etc/puppet/puppet.conf
[main]
# The Puppet log directory.
Jira (PUP-3505) Future parser handling undef's incorrectly
Title: Message Title Aaron Armstrong commented on an issue Re: Future parser handling undef's incorrectly Andy Parker - can we get this reviewed and merged today? Add Comment Puppet / PUP-3505 Future parser handling undef's incorrectly Trying to run the future parser with PE I ran in to the following error https://github.com/puppetlabs/puppetlabs-pe_staging/blob/3.2.x/manifests/file.pp#L18 The manifest above is failing because the future parser is overriding the variable $environment with the top-level puppet variable ($environment) set to 'production' in our case. The error I got ... 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-3130) Remove hidden $_timestamp fact
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3130 Remove hidden $_timestamp fact Change By: Kylo Ginsberg Component/s: DOCS 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-3514) Future parser not showing line/column for error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3514 Future parser not showing line/column for error Change By: Henrik Lindberg 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-3514) Future parser not showing line/column for error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3514 Future parser not showing line/column for error Change By: Henrik Lindberg Fix Version/s: PUP3.7.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-3514) Future parser not showing line/column for error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3514 Future parser not showing line/column for error 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-3130) Remove hidden $_timestamp fact
Title: Message Title Kylo Ginsberg commented on an issue Re: Remove hidden $_timestamp fact Nicholas Fagerlund this PR is now (quietly) deprecating strip_internal in Puppet 4.0. Add Comment Puppet / PUP-3130 Remove hidden $_timestamp fact 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-996) Duplicate declaration during compilation with default parameters and future parser
Title: Message Title
Kenneth Barber commented on an issue
Re: Duplicate declaration during compilation with default parameters and future parser
Can you supply me with the exact Vagrantfile as well, so I can be lazy?
Add Comment
PuppetDB / PDB-996
Duplicate declaration during compilation with default parameters and future parser
When using the puppetdb module with default parameters and the future parser, the following error is thrown during compilation: {noformat} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Exec[validate postgres connection for localhost/puppetd...
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-996) Duplicate declaration during compilation with default parameters and future parser
Title: Message Title Brian Kane commented on an issue Re: Duplicate declaration during compilation with default parameters and future parser bkane_local$ vagrant init puppetlabs/centos-6.5-64-nocm bkane_local$ vagrant box add puppetlabs/centos-6.5-64-nocm https://vagrantcloud.com/puppetlabs/boxes/centos-6.5-64-nocm/versions/3/providers/virtualbox.box bkane_local$ vagrant up bkane_local$ cat Vagrantfile # -*- mode: ruby -*- # vi: set ft=ruby : # Vagrantfile API/syntax version. Don't touch unless you know what you're doing! VAGRANTFILE_API_VERSION = 2
Jira (PUP-2706) Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Title: Message Title
Melissa Stone commented on an issue
Re: Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Kenneth Barber I've attached a pull request that includes the changes suggested by Haus. I wasn't able to reproduce the error, but hopefully this will help with relieving the failure...
Add Comment
Puppet / PUP-2706
Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
We keep getting this error during Puppet installation for our PuppetDB builds: {code} Setting up ruby-augeas (0.5.0-2) ... Setting up libaugeas-ruby (0.5.0-2) ... Setting up ruby-shadow (2.2.0-1) ... Setting up ruby-json (1.8.0-1build1) ... Setting up hiera (1.3.3-1puppetlabs1) ... Setting up puppet-common (3.6.1-1puppetlabs1) ... chage: the sha...
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-2706) Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Title: Message Title
Kenneth Barber commented on an issue
Re: Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Melissa Stone Yay, let me track down a ticket for adding Ubuntu 14.04 back into our testing/packaging pipeline. Thanks very much!
Add Comment
Puppet / PUP-2706
Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
We keep getting this error during Puppet installation for our PuppetDB builds: {code} Setting up ruby-augeas (0.5.0-2) ... Setting up libaugeas-ruby (0.5.0-2) ... Setting up ruby-shadow (2.2.0-1) ... Setting up ruby-json (1.8.0-1build1) ... Setting up hiera (1.3.3-1puppetlabs1) ... Setting up puppet-common (3.6.1-1puppetlabs1) ... chage: the sha...
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-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Joshua Partlow commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. So talking with Dan, Ruth and Nathaniel in the node classifier channel, the sporadic PSQL issue showing up in the concurrency test is turning up a race condition in the activity service for simultaneous node requests. PE-6571 which looks like a blocker. Add Comment Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments. 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-3505) Future parser handling undef's incorrectly
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3505 Future parser handling undef's incorrectly 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 (PDB-997) Add Ubuntu 14.04/trusty to acceptance testing
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-997 Add Ubuntu 14.04/trusty to acceptance testing Issue Type: Improvement Assignee: Unassigned Created: 24/Oct/14 10:41 AM Priority: Normal Reporter: Kenneth Barber This would require: New vm image via puppetlabs-packer And the Ubuntu 14.04 packages re-enabled during build The acceptance tests to be ran on this new image Add Comment
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Logan Attwood commented on an issue Re: current thread not owner after Puppet Agent receives USR1 signal Also chiming in on this. [centos@galen-stage ~]$ ruby -v ruby 2.0.0p353 (2013-11-22) [x86_64-linux] [centos@galen-stage ~]$ rpm -qa | grep puppet puppetlabs-release-7-11.noarch puppet-3.7.1-1.el7.noarch mcollective-puppet-agent-1.9.1-1.el7.noarch mcollective-puppet-common-1.9.1-1.el7.noarch Add Comment
Jira (PUP-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Logan Attwood updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Logan Attwood Environment: Ubuntu12.04.2LTSRuby2.0.0(patchlevel353)ORRuby2.1.0(patchlevel0) CentOS7Ruby2.0.0(patchlevel353) 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-3505) Future parser handling undef's incorrectly
Title: Message Title Andy Parker commented on an issue Re: Future parser handling undef's incorrectly Merged into stable in 783217. Add Comment Puppet / PUP-3505 Future parser handling undef's incorrectly Trying to run the future parser with PE I ran in to the following error https://github.com/puppetlabs/puppetlabs-pe_staging/blob/3.2.x/manifests/file.pp#L18 The manifest above is failing because the future parser is overriding the variable $environment with the top-level puppet variable ($environment) set to 'production' in our case. The error I got ... 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-3532) Need way to pass array to class to APPEND to defaults
Title: Message Title redmine.exporter created an issue Puppet / PUP-3532 Need way to pass array to class to APPEND to defaults Issue Type: Bug Assignee: Unassigned Created: 24/Oct/14 10:45 AM Labels: redmine Priority: Normal Reporter: redmine.exporter A way to pass an array to a class so that it would APPEND that array to the default array for that class would be excellent. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3130) Remove hidden $_timestamp fact
Title: Message Title Nicholas Fagerlund commented on an issue Re: Remove hidden $_timestamp fact Ha, interesting. So this is a method that will be deprecated in 4.x and removed in 5.0? I think that's the first of those, isn't it? Add Comment Puppet / PUP-3130 Remove hidden $_timestamp fact 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-996) Duplicate declaration during compilation with default parameters and future parser
Title: Message Title
Kenneth Barber commented on an issue
Re: Duplicate declaration during compilation with default parameters and future parser
Aah, there we go - got it now. Thanks: https://gist.github.com/kbarber/b433f5ad24e46cb1c565
Add Comment
PuppetDB / PDB-996
Duplicate declaration during compilation with default parameters and future parser
When using the puppetdb module with default parameters and the future parser, the following error is thrown during compilation: {noformat} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Exec[validate postgres connection for localhost/puppetd...
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-996) Duplicate declaration during compilation with default parameters and future parser
Title: Message Title
Kenneth Barber commented on an issue
Re: Duplicate declaration during compilation with default parameters and future parser
You know what, I'm such a tool. This is a postgresql module error isn't it? We don't maintain that as part of the PuppetDB project. Let me figure out where this ticket belongs.
Add Comment
PuppetDB / PDB-996
Duplicate declaration during compilation with default parameters and future parser
When using the puppetdb module with default parameters and the future parser, the following error is thrown during compilation: {noformat} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Exec[validate postgres connection for localhost/puppetd...
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-3513) Puppet failing to autoload provider
Title: Message Title Charlie Sharpsteen commented on an issue Re: Puppet failing to autoload provider It would be helpful to see the Ruby code that is causing this problem. Is it being triggered by a module from the Forge? If it is a custom module, is the code somewhere that we could see it? Add Comment Puppet / PUP-3513 Puppet failing to autoload provider Receiving the following error: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload puppet/type/domain: Could not autoload puppet/provider/domain/asadmin: no such file to load -- puppet/provider/asadmin on node when attempting to pull from master: the providers exists in: /puppet/modules/glassfish/lib/... 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-3513) Puppet failing to autoload provider
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3513 Puppet failing to autoload provider Change By: Charlie Sharpsteen Assignee: AdamScarborough 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-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/129/ Add Comment PuppetDB / PDB-990 PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt h2. Ticket/master/pdb 954 fallback acceptance * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129] * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files] h2. Pull Request Description (webhooks-id... 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-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Jeremy Barlow commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. The only improvement to check_woy_cache specifically that I remember is the work integrated for PUP-3175 , which I believe is already in the acceptance tests as of the 3.7.1 release. The spurious fails we'd seen before that change went away with the exception of the occasional failure due to SERVER-38. Add Comment Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments. 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 (PDB-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt wkalt commented: @pljenkinsro retest this please Add Comment PuppetDB / PDB-990 PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt h2. Ticket/master/pdb 954 fallback acceptance * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129] * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files] h2. Pull Request Description (webhooks-id... 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-3505) Future parser handling undef's incorrectly
Title: Message Title Aaron Armstrong commented on an issue Re: Future parser handling undef's incorrectly Joshua Partlow Moses Mendoza - can this be merged over to pe_puppet now? Add Comment Puppet / PUP-3505 Future parser handling undef's incorrectly Trying to run the future parser with PE I ran in to the following error https://github.com/puppetlabs/puppetlabs-pe_staging/blob/3.2.x/manifests/file.pp#L18 The manifest above is failing because the future parser is overriding the variable $environment with the top-level puppet variable ($environment) set to 'production' in our case. The error I got ... 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-3505) Future parser handling undef's incorrectly
Title: Message Title Moses Mendoza commented on an issue Re: Future parser handling undef's incorrectly Aaron Armstrong this has been merged over, and builds are in process. Add Comment Puppet / PUP-3505 Future parser handling undef's incorrectly Trying to run the future parser with PE I ran in to the following error https://github.com/puppetlabs/puppetlabs-pe_staging/blob/3.2.x/manifests/file.pp#L18 The manifest above is failing because the future parser is overriding the variable $environment with the top-level puppet variable ($environment) set to 'production' in our case. The error I got ... 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-2788) Puppet package source check fails with DFS share
Title: Message Title
Ethan Brown commented on an issue
Re: Puppet package source check fails with DFS share
Ping Kurt Gardiner - any luck debugging to inspect the contents of REPARSE_DATA_BUFFER?
Add Comment
Puppet / PUP-2788
Puppet package source check fails with DFS share
{noformat} package { 'NetFx452': ensure = installed, source = '//dfs_share/software/dotNetFx452_Full_x86_x64.exe', install_options = ['/q'], } {noformat} fails with error {noformat} Error: The source does not exist: '//dfs_share/software/dotNetFx452_Full_x86_x64.exe' {noformat} Digging through th...
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-3533) File resource doesn't handle NTFS junctions well
Title: Message Title Brian Krische created an issue Puppet / PUP-3533 File resource doesn't handle NTFS junctions well Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Unassigned Created: 24/Oct/14 11:28 AM Environment: Windows Server 2012 R2 Priority: Normal Reporter: Brian Krische Puppet (specifically the file resource) doesn't seem to consistently handle NTFS folder junctions in Windows. Here are some steps to reproduce: Create a directory and directory junction in Windows mkdir C:\directory mklink /J C:\junction C:\directory Create a file inside the junction (this works)
Jira (PUP-3291) Remove autoloader from Puppet::Interface
Title: Message Title
William Hopper commented on an issue
Re: Remove autoloader from Puppet::Interface
Functional review: as of SHA 3073c3105d, the code is indeed removed from the codebase. Since this is a minor code removal, and specs / acceptance are passing, we can call it resolved.
Add Comment
Puppet / PUP-3291
Remove autoloader from Puppet::Interface
{noformat} lib/puppet/interface.rb:35: # @deprecated lib/puppet/interface.rb:37: Puppet.deprecation_warning(Puppet::Interface.autoloader is deprecated; please use Puppet::Interface#loader instead) {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-2782) Yumrepo target attribute does not work
Title: Message Title
Hunter Haugen commented on an issue
Re: Yumrepo target attribute does not work
The yumrepo resource type defines target to be a parameter 1 and so therefore it is not read from the system during self.instances as a property would be, and thus cannot be updated by itself. (Parameters are used to modify the behavior of the provider when sync'ing properties, but are not themselves sync'd.)
But it doesn't seem to be taken into account even when creating the repo... during the create, the provider calls the store class method 2 which is for a Puppet::Util::IniConfig object 3. (NB, virtual_inifile is a collection of all .repo files into one big ini structure.) The iniconfig file collection will store each ini structure in a file named after its key in the virtual_inifile object 4 which doesn't take target into account at all.
To start fixing this, it would probably require updating the description section 5 to be able to use target instead of descr if it is available, and the description is not currently one of the pre-existing sections. But that would probably also run into issues with destroying 6, among other things.
I assume we would not want to allow targets to be changed once a repo entry exists... or at least I can't imagine how puppet would handle such an operation.
Add Comment
Puppet / PUP-2782
Yumrepo target attribute does not work
Simplified example: yumrepo { 'foo-bar': descr = 'Foo Bar', target = '/tmp/foo-bar.repo' } yumrepo { 'foo-bat': descr = 'Foo Bat', target = '/tmp/foo-bar.repo' }Notice: /Stage[main]/Yum/Yumrepo[foo-bat]/ensure: created Info: changing mode of /etc/yum.repos.d/foo-bat.repo from 600 to 644 Not...
Jira (PDB-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/130/ Add Comment PuppetDB / PDB-990 PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt h2. Ticket/master/pdb 954 fallback acceptance * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129] * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files] h2. Pull Request Description (webhooks-id... 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-3130) Remove hidden $_timestamp fact
Title: Message Title Kylo Ginsberg commented on an issue Re: Remove hidden $_timestamp fact Yeah I think it is. Hooray! I think? Add Comment Puppet / PUP-3130 Remove hidden $_timestamp fact 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-2788) Puppet package source check fails with DFS share
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2788 Puppet package source check fails with DFS share Change By: Ethan Brown Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3130) Remove hidden $_timestamp fact
Title: Message Title Nicholas Fagerlund commented on an issue Re: Remove hidden $_timestamp fact Col. Okay, I've filed DOC-1320 to track deprecated features for 4.0. Add Comment Puppet / PUP-3130 Remove hidden $_timestamp fact 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-3505) Future parser handling undef's incorrectly
Title: Message Title Aaron Armstrong commented on an issue Re: Future parser handling undef's incorrectly Nick Walker AJ Roetker - can one of you validate this fix in a PE build? # 1729 should have all of the fixes merged in. Add Comment Puppet / PUP-3505 Future parser handling undef's incorrectly Trying to run the future parser with PE I ran in to the following error https://github.com/puppetlabs/puppetlabs-pe_staging/blob/3.2.x/manifests/file.pp#L18 The manifest above is failing because the future parser is overriding the variable $environment with the top-level puppet variable ($environment) set to 'production' in our case. The error I got ... 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-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title
Aaron Armstrong commented on an issue
Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
John Duarte - have you been able to verify this fix in a PE build?
Add Comment
Puppet / PUP-3500
Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
When using directory environments, if you have a setting like 'certname' set in puppet.conf (either in main, or in the section that will correspond to the run_mode of your application), setting values will be cached for the production environment which will return legacy default values for manifest and modulepath. {noformat} jpartlow@percival:~/work/p...
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
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title Eric Thompson commented on an issue Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings. verified in trusty at SHA: 7832174 root@t1i1pix4vmeyavq:/etc/puppet# puppet apply -e 'notice($settings::modulepath) notice($settings::manifest) notice($settings::config_version)' Notice: Scope(Class[main]): Notice: Scope(Class[main]): no_manifest Notice: Scope(Class[main]): Notice: Compiled catalog for foo in environment production in 0.01 seconds Notice: /File[/etc/puppet/environments/production]/ensure: created Notice: Finished catalog run in 0.02 seconds Add Comment
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title Eric Thompson commented on an issue Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings. verified on trusty at SHA 7832174 with: # after changes to puppet.conf to add environment path and certname root@k0fhefwhypbgin2:~# puppet apply -e 'notice($settings::modulepath) notice($settings::manifest) notice($settings::config_version)' Notice: Scope(Class[main]): /etc/puppet/environments/production/modules:/etc/puppet/modules:/usr/share/puppet/modules Notice: Scope(Class[main]): /etc/puppet/environments/production/manifests Notice: Scope(Class[main]): Notice: Compiled catalog for k0fhefwhypbgin2 in environment production in 0.02 seconds Notice: Finished catalog run in 0.02 seconds Add Comment
Jira (PUP-3500) Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings.
Title: Message Title Eric Thompson commented on an issue Re: Adding a setting to puppet.conf that has a :hook handled on define preloads incorrect directory environment settings. verified in pe at version 3.4.0-rc1-1709-gc89b548 in scientific6 #after changing environmentpath to /tmp/environments [root@gjg0iiff12qcisp puppet]# puppet apply -e 'notice($settings::modulepath) notice($settings::manifest) notice($settings::config_version)' Notice: Scope(Class[main]): /tmp/environments/production/modules:/etc/puppetlabs/puppet/modules:/opt/puppet/share/puppet/modules Notice: Scope(Class[main]): /tmp/environments/production/manifests Notice: Scope(Class[main]): Notice: Compiled catalog for gjg0iiff12qcisp in environment production in 0.03 seconds Notice: Finished catalog run in 0.19 seconds Add Comment
Jira (PDB-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/131/ Add Comment PuppetDB / PDB-990 PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt h2. Ticket/master/pdb 954 fallback acceptance * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129] * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files] h2. Pull Request Description (webhooks-id... 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-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt wkalt commented: @pljenkinsro retest this please Add Comment PuppetDB / PDB-990 PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt h2. Ticket/master/pdb 954 fallback acceptance * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129] * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files] h2. Pull Request Description (webhooks-id... 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-3300) Rework Puppet::Util::Checksums to not extend itself
Title: Message Title
Andy Parker commented on an issue
Re: Rework Puppet::Util::Checksums to not extend itself
Merged into master in 9812ca
Add Comment
Puppet / PUP-3300
Rework Puppet::Util::Checksums to not extend itself
The comment in the code states: {code} # In Puppet 4 we should switch this to `module_function` to make these methods # private when this class is included. {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/d/optout.
Jira (PUP-3536) If the /etc/hosts file includes the line continuation character '\' the host resource overwrites everything
Title: Message Title
Tim Purkerson created an issue
Puppet / PUP-3536
If the /etc/hosts file includes the line continuation character '\' the host resource overwrites everything
Issue Type:
Bug
Assignee:
Unassigned
Components:
Puppet Server
Created:
24/Oct/14 3:57 PM
Priority:
Normal
Reporter:
Tim Purkerson
/etc/hosts file: 127.0.0.1 localhost 127.0.1.1 pe-332-master.puppetdebug.vlan pe-332-master 10.20.1.2 pe-332-master.puppetdebug.vlan pe-332-master 192.168.194.131 gk_int.bna.com \ access-p.bna.com \ access.bna.com \ accounting_gk-p.bna.com
Sample pp file: host { 'fooby': name = 'www.google.com', ensure = present, comment = this is a comment, host_aliases = 'www.test.com', ip = '1.1.1.1', }
/etc/hosts file after puppet apply fooby.pp
HEADER: This file was autogenerated at 2014-10-24 22:56:44 +
HEADER: by puppet. While it can still be managed manually, it
HEADER: is definitely not recommended. 1.1.1.1 www.google.com www.test.com # this is a comment
Jira (PUP-3537) Failed puppet report submissions should be spooled for later submission
Title: Message Title Eric Sorenson moved an issue Puppet / PUP-3537 Failed puppet report submissions should be spooled for later submission Change By: Eric Sorenson Workflow: Engineering Platform Workflow Issue Type: MarketProblem Improvement Key: ROAD PUP - 498 3537 Project: Roadmap Puppet Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-990) PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/132/ Add Comment PuppetDB / PDB-990 PR (1129): Ticket/master/pdb 954 fallback acceptance - wkalt h2. Ticket/master/pdb 954 fallback acceptance * Author: Wyatt Alt * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1129 Discussion|https://github.com/puppetlabs/puppetdb/pull/1129] * [Pull Request 1129 File Diff|https://github.com/puppetlabs/puppetdb/pull/1129/files] h2. Pull Request Description (webhooks-id... 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-3538) Create terminii for JSON
Title: Message Title Andy Parker created an issue Puppet / PUP-3538 Create terminii for JSON Issue Type: Improvement Assignee: Unassigned Created: 24/Oct/14 4:33 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker All of the indirector terminii that currently use YAML need to have a JSON terminus written. In addition, the node terminus needs a WriteOnlyJson terminus so that we don't regress on Redmine 16753. Once all of those are in place, the defaults need to be switched to use them instead of YAML. Add Comment
Jira (PUP-3505) Future parser handling undef's incorrectly
Title: Message Title Nick Walker commented on an issue Re: Future parser handling undef's incorrectly Aaron Armstrong AJ Roetker this appears to work [root@pe-34nightly-master ~]# puppet agent -t Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Info: Caching catalog for pe-34nightly-master.puppetdebug.vlan Info: Applying configuration version '1414194006' Notice: Finished catalog run in 5.37 seconds [root@pe-34nightly-master ~]# puppet --version 3.7.2 (Puppet Enterprise 3.4.0-rc1-1741-gf192d47)
Jira (PUP-3289) Remove deprecated serialization and dynamic facts settings
Title: Message Title
Andy Parker commented on an issue
Re: Remove deprecated serialization and dynamic facts settings
Merged into master in b2d846
Add Comment
Puppet / PUP-3289
Remove deprecated serialization and dynamic facts settings
{{catalog_format}} and {{dynamicfacts}} are deprecated and need to be removed.
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-3539) add additional spec tests to cover globbing ACL matches in fileserver.conf
Title: Message Title Eric Thompson commented on an issue Re: add additional spec tests to cover globbing ACL matches in fileserver.conf spec/unit/network/authstore_spec.rb Add Comment Puppet / PUP-3539 add additional spec tests to cover globbing ACL matches in fileserver.conf 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-3539) add additional spec tests to cover globbing ACL matches in fileserver.conf
Title: Message Title Eric Thompson created an issue Puppet / PUP-3539 add additional spec tests to cover globbing ACL matches in fileserver.conf Issue Type: Bug Assignee: Unassigned Created: 24/Oct/14 5:06 PM Priority: Normal Reporter: Eric Thompson 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-3539) add additional spec tests to cover globbing ACL matches in fileserver.conf
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3539 add additional spec tests to cover globbing ACL matches in fileserver.conf Change By: Eric Thompson Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3539) add additional spec tests to cover globbing ACL matches in fileserver.conf
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3539 add additional spec tests to cover globbing ACL matches in fileserver.conf Change By: Eric Thompson Priority: Normal Minor 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-3540) Remove all uses of PSON and replace with JSON
Title: Message Title Andy Parker created an issue Puppet / PUP-3540 Remove all uses of PSON and replace with JSON Issue Type: Improvement Assignee: Unassigned Created: 24/Oct/14 5:19 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker Right now puppet uses something called PSON instead of JSON. This is all over the place. PSON needs to be removed and replaced with JSON. At the same time replace all uses of x.to_json or x.to_pson with JSON.generate(x.to_data_hash) and then delete all of the custom to_pson and to_json methods. Remove puppet/external/pson. Create a stubbed PSON module that simply forwards all calls to JSON. When a call against PSON is made it need to emit a deprecation warning. We can't simply remove PSON because a large number of modules appear to depend on it. Add Comment
Jira (PUP-3541) Remove client and server yaml directories
Title: Message Title Andy Parker created an issue Puppet / PUP-3541 Remove client and server yaml directories Issue Type: Improvement Assignee: Unassigned Created: 24/Oct/14 5:31 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker Currently, some data that puppet saves is written to the yamldir (or clientyamldir) if it is YAML or to server_datadir (or client_datadir) if it is not. All data needs to be written to server_datadir for the master and client_datadir for the client, no matter if it is YAML or not. The yamldir settings can then be removed. Question: can we just combine the client and server data dirs? What is the reason they are separate? Add Comment
Jira (PUP-2289) Puppet will purge the /etc/hosts if it have some invalid lines
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2289 Puppet will purge the /etc/hosts if it have some invalid lines Change By: Kylo Ginsberg QA Contact: NarmadhaPerumal 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-2289) Puppet will purge the /etc/hosts if it have some invalid lines
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2289 Puppet will purge the /etc/hosts if it have some invalid lines Change By: Kylo Ginsberg Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3542) Write statefile in JSON
Title: Message Title Andy Parker created an issue Puppet / PUP-3542 Write statefile in JSON Issue Type: Improvement Assignee: Unassigned Created: 24/Oct/14 5:39 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Andy Parker Currently the statefile is written in YAML format. It needs to be changed to JSON. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-880) Remove localconfig Setting
Title: Message Title Andy Parker updated an issue Puppet / PUP-880 Remove localconfig Setting Change By: Andy Parker Ican'tfindanyreferencetothissetting,weshould deprecate justremove it. 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.
