Jira (PUP-1929) puppet apply should not return 0 if catalog compilation fails
Title: Message Title
Michael Prokop commented on an issue
Re: puppet apply should not return 0 if catalog compilation fails
Same here with puppet 2.7.23 (Debian/wheezy), also without '--detailed-exitcodes':
# puppet agent --test
info: Caching catalog for jenkins-dev
info: Applying configuration version '1398338846'
err: Could not apply complete catalog: Found 1 dependency cycle:
(File[snip] = Class[Jenkins::Ec2tools] = Class[Jenkins::Ssh] = snip)
Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz
notice: Finished catalog run in 0.39 seconds
# echo $?
0
It's quite dangerous and misleading because even in puppet dashboard you don't notice that a host running into such a problem doesn't receive any updates.
Add Comment
Puppet / PUP-1929
puppet apply should not return 0 if catalog compilation fails
When using the --detailed-exitcodes option, and preforming the following: {code} bundle exec puppet apply --detailed-exitcodes -e 'notify { foo: require = Notify[foo] }' /dev/mem: Permission denied Notice: Compiled catalog for blah in environment production in 0.04 seconds /dev/mem: Permission denied Error: Could not apply complete catalog: Fo...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-596) PR (943): (DOCUMENT-6) Update config page for PuppetDB module's improved settings ... - nfagerlund
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-596 PR (943): (DOCUMENT-6) Update config page for PuppetDB module's improved settings ... - nfagerlund Change By: Kenneth Barber Sprint: 20140423to20140507 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-596) PR (943): (DOCUMENT-6) Update config page for PuppetDB module's improved settings ... - nfagerlund
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-596 PR (943): (DOCUMENT-6) Update config page for PuppetDB module's improved settings ... - nfagerlund Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1699) Cache environments
Title: Message Title Henrik Lindberg commented on an issue Re: Cache environments Status update: We (Joshua Partlow and I) are currently looking at tests that are failing - not because of caching per se (in fact, caching is turned off because that is what most tests expect). The issues we are facing are that the tests have usage scenarios that are different than the normal operations, and there are expectancies that all partial usage of Catalog and Compiler should just work. Add Comment Puppet / PUP-1699 Cache environments Currently, the new directory environments are not cached - each catalog compilation will start from scratch and reparse all puppet manifests and reload types. This can be solved by caching the result. A naive implementation that never evicts anything proved this to have a positive effect, bringing down the execution time to about 50% of the first compi... 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
Jira (PDB-597) Add Trusty (Ubuntu 14.04) Packaging Support for 2.x (master)
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-597 Add Trusty (Ubuntu 14.04) Packaging Support for 2.x (master) Issue Type: New Feature Assignee: Unassigned Created: 24/Apr/14 6:56 AM Fix Versions: 2.0.0 Priority: Normal Reporter: Kenneth Barber Add packaging support for 2.x, this depends on Puppet 3.6.0 landing with that support (need to find the right ticket to link to). Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-465) Add Trusty (Ubuntu 14.04) Packaging Support
Title: Message Title Kenneth Barber commented on an issue Re: Add Trusty (Ubuntu 14.04) Packaging Support We've limited this to the 1.6.x branch, as 2.0.x is pinned against Puppet 3.5.1 we can't roll this for 2.x until Puppet releases a Trusty release (since we have a build and runtime dependency on it for terminus etc.). I've created another ticket (linked here) to track this work for 2.x. Add Comment PuppetDB / PDB-465 Add Trusty (Ubuntu 14.04) Packaging Support This involves adding/updating spen and acceptance tests for trusty, and making sure the build_defaults has been updated accordingly 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-335) Functions that require the future parser should be concretely identifiable
Title: Message Title Henrik Lindberg commented on an issue Re: Functions that require the future parser should be concretely identifiable New function API is in 3.6, but there is no time to move the iterative functions to it. Add Comment Puppet / PUP-335 Functions that require the future parser should be concretely identifiable Take a look at the function reference: http://docs.puppetlabs.com/references/3.latest/function.html There are a bunch of functions in there that will just plain explode on a stock Puppet 3.x install. (each, collect, etc.) This is because there’s no indication in these functions' code that they require the future parser. We need an indication of this ... 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-2357) Validation missing for meaningless sequences
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2357 Validation missing for meaningless sequences Issue Type: Bug Assignee: Andy Parker Components: DSL Created: 24/Apr/14 7:38 AM Fix Versions: 3.7.0 Priority: Normal Reporter: Henrik Lindberg There is currently no validation of the future parser's result wrt. evaluation of meaningless sequences. If user enters: 1 2 3 hello goodbye The evaluator will just do what it is told, and produce a 1, then a 2, etc. The only place were a side effect free _expression_ may appear is as the last _expression_ in a sequence / block as this is the produced value of an _expression_. The importance of this validation has increased since the future parser (since 3.6) handles calls without parentheses as reserved for a handful of built in calls (i.e. 'include', 'require', etc.). Thus, if users have code where calls without parentheses are used they are not informed about this issue - i.e. their code turned into a side effect free sequence that is just silently evaluated.
Jira (PDB-598) PR (945): Fix command API Content-Type - dalen
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-598 PR (945): Fix command API Content-Type - dalen Issue Type: Task Assignee: Unassigned Created: 24/Apr/14 7:49 AM Labels: github Priority: Normal Reporter: gepetto-bot Fix command API Content-Type Author: Erik Daln erik.gustav.da...@gmail.com Company: Spotify Github ID: dalen Pull Request 945 Discussion Pull Request 945 File Diff Pull Request Description (webhooks-id: af55cece543b8f7832a16b67a7db4a68)
Jira (PDB-598) PR (945): Fix command API Content-Type - dalen
Title: Message Title gepetto-bot commented on an issue Re: PR (945): Fix command API Content-Type - dalen pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-598 PR (945): Fix command API Content-Type - dalen h2. Fix command API Content-Type * Author: Erik Daln erik.gustav.da...@gmail.com * Company: Spotify * Github ID: [dalen|https://github.com/dalen] * [Pull Request 945 Discussion|https://github.com/puppetlabs/puppetdb/pull/945] * [Pull Request 945 File Diff|https://github.com/puppetlabs/puppetdb/pull/945/files] h2. Pull Request Description ... 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-598) PR (945): Fix command API Content-Type - dalen
Title: Message Title gepetto-bot commented on an issue Re: PR (945): Fix command API Content-Type - dalen pljenkinsro commented: Can one of the admins verify this patch? Add Comment PuppetDB / PDB-598 PR (945): Fix command API Content-Type - dalen h2. Fix command API Content-Type * Author: Erik Daln erik.gustav.da...@gmail.com * Company: Spotify * Github ID: [dalen|https://github.com/dalen] * [Pull Request 945 Discussion|https://github.com/puppetlabs/puppetdb/pull/945] * [Pull Request 945 File Diff|https://github.com/puppetlabs/puppetdb/pull/945/files] h2. Pull Request Description ... 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-598) PR (945): Fix command API Content-Type - dalen
Title: Message Title gepetto-bot commented on an issue Re: PR (945): Fix command API Content-Type - dalen Pull request Fix command API Content-Type has been closed. Add Comment PuppetDB / PDB-598 PR (945): Fix command API Content-Type - dalen h2. Fix command API Content-Type * Author: Erik Daln erik.gustav.da...@gmail.com * Company: Spotify * Github ID: [dalen|https://github.com/dalen] * [Pull Request 945 Discussion|https://github.com/puppetlabs/puppetdb/pull/945] * [Pull Request 945 File Diff|https://github.com/puppetlabs/puppetdb/pull/945/files] h2. Pull Request Description ... 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-1531) Puppet Master uanble to find module if the directory is a symlink
Title: Message Title Cody Ramaker commented on an issue Re: Puppet Master uanble to find module if the directory is a symlink This is still an issue on Puppet Master Version 3.5.1 - symlinks for modules aren't followed. Add Comment Puppet / PUP-1531 Puppet Master uanble to find module if the directory is a symlink During development of a module, I had a git checkout in my home directory and symlinked it into /etc/puppet/modules. Then I classified the output via dashboard. I found that Puppet Master would not find the class/module since the module was a symlink. I searched other tickets and didn't see this already filed, but it very well could be. Testing on 2... 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-596) PR (943): (DOCUMENT-6) Update config page for PuppetDB module's improved settings ... - nfagerlund
Title: Message Title gepetto-bot commented on an issue Re: PR (943): (DOCUMENT-6) Update config page for PuppetDB module's improved settings ... - nfagerlund Pull request ( DOCUMENT-6 ) Update config page for PuppetDB module's improved settings ... has been closed. Add Comment PuppetDB / PDB-596 PR (943): (DOCUMENT-6) Update config page for PuppetDB module's improved settings ... - nfagerlund h2. (DOCUMENT-6) Update config page for PuppetDB module's improved settings ... * Author: Nick Fagerlund * Company: * Github ID: [nfagerlund|https://github.com/nfagerlund] * [Pull Request 943 Discussion|https://github.com/puppetlabs/puppetdb/pull/943] * [Pull Request 943 File Diff|https://github.com/puppetlabs/puppetdb/pull/943/files] h2. Pull ... 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
Jira (PUP-2211) Confusing ArgumentError exception message when using future parser
Title: Message Title Andy Parker updated an issue Puppet / PUP-2211 Confusing ArgumentError exception message when using future parser Change By: Andy Parker 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 (PDB-599) PR (946): Fixed inconsistencies in the deprecation warning messages of commands - senior
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-599 PR (946): Fixed inconsistencies in the deprecation warning messages of commands - senior Issue Type: Task Assignee: Unassigned Created: 24/Apr/14 8:51 AM Labels: github Priority: Normal Reporter: gepetto-bot Fixed inconsistencies in the deprecation warning messages of commands Author: Ryan Senior senior.r...@gmail.com Company: Github ID: senior Pull Request 946 Discussion Pull Request 946 File Diff Pull Request Description (webhooks-id: 05313ac7bcf037908c8bc2b7ca5d6e3a)
Jira (PUP-2252) Legacy settings take precedence over directory settings in a puppet config print.
Title: Message Title Andy Parker assigned an issue to Joshua Partlow Is this still an issue. I think this might be fixed now. Puppet / PUP-2252 Legacy settings take precedence over directory settings in a puppet config print. Change By: Andy Parker Assignee: JoshuaPartlow Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2159) import is silently ignored using the future parser
Title: Message Title
Andy Parker commented on an issue
Re: import is silently ignored using the future parser
Looks like we accidentally duplicated this. The work has already been done and associated with PUP-2302.
Add Comment
Puppet / PUP-2159
import is silently ignored using the future parser
The import statement, when used like below, is silently ignored if you are using the future parser. {noformat} import nodes {noformat} PUP-490 says: {quote} i.e. future parser/evaluator will not issue deprecation, and will instead interpret import as if it is a function call (leading to unknown function error since there is no such functio...
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-1544) Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
Title: Message Title
Andy Parker commented on an issue
Re: Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
Gavin Williams, can you please open a pull request with these changes. We only use pull requests to track code contributions.
Add Comment
Puppet / PUP-1544
Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
When trying to test some tweaks to support PUP-958, an issue has been encountered whereby Puppet is throwing the following error: {noformat} sudo bundle exec puppet resource package bash ensure=held /home/vagrant/puppet/lib/puppet/util/logging.rb:34:in `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError) f...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PDB-561) Rename name to certname in nodes endpoint
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-561 Rename name to certname in nodes endpoint Change By: Ryan Senior Assignee: RyanSenior 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-2354) allow duplicate certs does not work with agent/master
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-2354
allow duplicate certs does not work with agent/master
Change By:
Charlie Sharpsteen
Onmymaster,Iset: {code} [main]allow_deplicate_certs=true {code} onthemaster,Iregenerateaprivatekey,Igetthefailure: pre {noformat} root@cygnet-2:~#puppetagent-t--ssldir=/tmp/info:CreatinganewSSLkeyforcygnet-2.cygnet.labwarning:peercertificatewon'tbeverifiedinthisSSLsessioninfo:Cachingcertificateforcawarning:peercertificatewon'tbeverifiedinthisSSLsessioninfo:Cachingcertificateforcygnet-2.cygnet.laberr:Couldnotrequestcertificate:Thecertificateretrievedfromthemasterdoesnotmatchtheagent'sprivatekey.Certificatefingerprint:B5:FE:4C:B6:D8:75:2C:8D:FD:05:48:53:43:DC:B4:10Tofixthis,removethecertificatefromboththemasterandtheagentandthenstartapuppetrun,whichwillautomaticallyregenerateacertficate.Onthemaster:puppetcertcleancygnet-2.cygnet.labOntheagent:rm-f/tmp/certs/cygnet-2.cygnet.lab.pempuppetagent-t {noformat} /pre Itappearsthattheagentdoesnotactuallyresenditscertreqifonealreadyexists,meaningthatallowduplicatecertsdoesnotworkwithpuppetagent.ThisissuewasobservedwithPuppet2.7.12,butIdonotbelieveitisaregression.
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-1635) current thread not owner after Puppet Agent receives USR1 signal
Title: Message Title Andy Parker updated an issue Puppet / PUP-1635 current thread not owner after Puppet Agent receives USR1 signal Change By: Andy Parker Component/s: CatalogApplication 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-2159) import is silently ignored using the future parser
Title: Message Title
Andy Parker commented on an issue
Re: import is silently ignored using the future parser
I marked this as a dup of the wrong ticket. PUP-2317 is the right one.
Add Comment
Puppet / PUP-2159
import is silently ignored using the future parser
The import statement, when used like below, is silently ignored if you are using the future parser. {noformat} import nodes {noformat} PUP-490 says: {quote} i.e. future parser/evaluator will not issue deprecation, and will instead interpret import as if it is a function call (leading to unknown function error since there is no such functio...
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-2093) PMT should use the Forge's /v3 API
Title: Message Title Andy Parker commented on an issue Re: PMT should use the Forge's /v3 API Pieter van de Bruggen, this has been merged, I believe. Can you update it with a reference to the merge commit and update its status? Add Comment Puppet / PUP-2093 PMT should use the Forge's /v3 API The PMT has been using an outdated, obsolete, and unscalable API for some time now. In an effort to deprecate those legacy APIs, we should update the PMT to use the more sustainable /v3 API. One side-effect of this change is that we will be forced to handle all dependency resolution in the PMT (since the server-side dependency resolution was not susta... 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-1544) Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
Title: Message Title
Gavin Williams commented on an issue
Re: Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
Andy Parker I didn't ever get it working tbh.
The patches attached were from my hacking around trying to get things working, and quickly got out of my depth... Adrien Thebo did give me some assistance at various points, so might remember the issues...
Add Comment
Puppet / PUP-1544
Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
When trying to test some tweaks to support PUP-958, an issue has been encountered whereby Puppet is throwing the following error: {noformat} sudo bundle exec puppet resource package bash ensure=held /home/vagrant/puppet/lib/puppet/util/logging.rb:34:in `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError) f...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from
Jira (PUP-2344) Functions unable to call functions in different modules
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2344 Functions unable to call functions in different modules Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2356) Add yum repo extra options
Title: Message Title David Caro updated an issue Puppet / PUP-2356 Add yum repo extra options Change By: David Caro 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-2358) puppet apply throws SELinux errors if $HOME is mounted via NFS
Title: Message Title Adam Moskowitz created an issue Puppet / PUP-2358 puppet apply throws SELinux errors if $HOME is mounted via NFS Issue Type: Bug Affects Versions: 3.2.2 Assignee: Eric Sorenson Components: Community Created: 24/Apr/14 9:37 AM Environment: CentOS 5.9 on x86_64 Priority: Normal Reporter: Adam Moskowitz When running puppet apply as myself (that is, NOT as root) I get errors like this: Warning: Failed to set SELinux context user_u:object_r:nfs_t on /home/amoskowi/.puppet Warning: Failed to set SELinux context system_u:object_r:user_home_t on /home/amoskowi/.puppet There should either be some way to specify that puppet not set SELinux attributes or that it use somewhere other than $HOME/.puppet
Jira (PUP-2093) PMT should use the Forge's /v3 API
Title: Message Title Pieter van de Bruggen commented on an issue Re: PMT should use the Forge's /v3 API Apologies; this was merged in 8732b5f4d0f72ed43a9eddd32de4024b5cce0cce. Add Comment Puppet / PUP-2093 PMT should use the Forge's /v3 API The PMT has been using an outdated, obsolete, and unscalable API for some time now. In an effort to deprecate those legacy APIs, we should update the PMT to use the more sustainable /v3 API. One side-effect of this change is that we will be forced to handle all dependency resolution in the PMT (since the server-side dependency resolution was not susta... 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-2284) Add a user interview for creating a metadata.json file
Title: Message Title
Pieter van de Bruggen commented on an issue
Re: Add a user interview for creating a metadata.json file
This was merged in c1e5ae1582c1270e3ce6f74bcbc5ff560b50032e.
Add Comment
Puppet / PUP-2284
Add a user interview for creating a metadata.json file
In order to make working with {{metadata.json}} a bit less painful for users, we should perform a brief interview as a part of the {{puppet module generate}} action, so that we can pre-populate the metadata with useful values.
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-2285) Update PMT generate's README template
Title: Message Title Pieter van de Bruggen commented on an issue Re: Update PMT generate's README template This was merged in 19c087717dd8fbea781d54adc902ed67580afc2a. Add Comment Puppet / PUP-2285 Update PMT generate's README template We have a wonderful README template (found at http://docs.puppetlabs.com/puppet/latest/reference/modules_documentation.html) which we've believed was shipped in core Puppet for some time now. We should actually do the work of integrating it into the PMT's default module skeleton. 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-2278) puppet module install fails when given path containing spaces
Title: Message Title Pieter van de Bruggen commented on an issue Re: puppet module install fails when given path containing spaces This was merged in 547af9b8208fe9a3c1657738824d55b2c4a9cf6b. Add Comment Puppet / PUP-2278 puppet module install fails when given path containing spaces I apologize if I haven't set this issue up correctly. First time. :) I found while using Librarian-Puppet that I couldn't install modules into paths containing spaces. I thought this was a problem with Librarian so I filed an issue there. https://github.com/rodjek/librarian-puppet/issues/201 It turns out the problem is with puppet module install. A... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1976) `puppet module build` should use `metadata.json` as input format
Title: Message Title Pieter van de Bruggen commented on an issue Re: `puppet module build` should use `metadata.json` as input format This was merged in ea39a3de5705020d79ae89d6ab513b37fa662ce7. Add Comment Puppet / PUP-1976 `puppet module build` should use `metadata.json` as input format `puppet module build` This action is most impacted by this change though we will maintain compatibility with users still using Modulefile as their input format. Here's how that will work when a user initiates build. - If the user provides a Modulefile at the root of their module, PMT will use it exclusively to build the release and issue a deprecati... 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-1977) `puppet module build` should create `metadata.json` instead of `Modulefile`
Title: Message Title
Pieter van de Bruggen commented on an issue
Re: `puppet module build` should create `metadata.json` instead of `Modulefile`
This was merged in ede281b70275d70550d4210cc055e222fd653d28.
Add Comment
Puppet / PUP-1977
`puppet module build` should create `metadata.json` instead of `Modulefile`
Since we're moving away from the {{Modulefile}} as the canonical source of metadata, we should do our users the favor of no longer generating a {{Modulefile}} – instead, we should generate the {{metadata.json}} file we expect them to use.
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-2309) Yum provider errors on priority undef
Title: Message Title
Adrien Thebo commented on an issue
Re: Yum provider errors on priority undef
Where does the yumrepo documentation indicate that undef is a valid value?
Add Comment
Puppet / PUP-2309
Yum provider errors on priority undef
Prior to 3.5 this code worked just fine. yumrepo { 'centos-6-os-x86_64': baseurl = $url, gpgkey = $gpgkey, priority = undef, } After upgrading to 3.5 I get an error: Failed to apply catalog: Parameter priority failed on Yumrepo[centos-6-os-x86_64]: Must be within range 1-99 yumrepo documentation states that und...
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-2309) Yum provider errors on priority undef
Title: Message Title Adrien Thebo assigned an issue to Sergei Genchev Puppet / PUP-2309 Yum provider errors on priority undef Change By: Adrien Thebo Assignee: KyloGinsberg SergeiGenchev 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-2359) Add a umask option to set the agent's umask predictably
Title: Message Title redmine.exporter created an issue Puppet / PUP-2359 Add a umask option to set the agent's umask predictably Issue Type: New Feature Assignee: Unassigned Created: 24/Apr/14 10:15 AM Labels: redmine Priority: Normal Reporter: redmine.exporter Right now, the Puppet agent inherits its umask from the process that launches it, and allows this umask to propagate through to commands run via exec and via providers and types. This can lead to surprising results if, for example, a git post-receive hook runs puppet agent with a different umask than the systemwide puppet agent service. This also interacts poorly with the lack of control over exec umasks (see #4424). Add Comment
Jira (PUP-2360) Yumrepo type allows invalid values
Title: Message Title David Caro created an issue Puppet / PUP-2360 Yumrepo type allows invalid values Issue Type: Bug Assignee: David Caro Created: 24/Apr/14 10:18 AM Priority: Normal Reporter: David Caro The regexps that validate the values are not restricting the whole line, allowing values like whateverTrueIwant inside yumrepo boolean options. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to
Jira (PDB-599) PR (946): Fixed inconsistencies in the deprecation warning messages of commands - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (946): Fixed inconsistencies in the deprecation warning messages of commands - senior pljenkinsro commented: :green_heart: Test passed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/388/ Add Comment PuppetDB / PDB-599 PR (946): Fixed inconsistencies in the deprecation warning messages of commands - senior h2. Fixed inconsistencies in the deprecation warning messages of commands * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 946 Discussion|https://github.com/puppetlabs/puppetdb/pull/946] * [Pull Request 946 File Diff|https://github.com/puppetlabs/puppetdb/pull/946/files] h2. 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
Jira (PUP-2361) Shellquote function includes words of 0 length
Title: Message Title Stephen Benjamin updated an issue Puppet / PUP-2361 Shellquote function includes words of 0 length Change By: Stephen Benjamin Summary: Shellquotefunction ncludes includes wordsof0length 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-2361) Shellquote function ncludes words of 0 length
Title: Message Title
Stephen Benjamin created an issue
Puppet / PUP-2361
Shellquote function ncludes words of 0 length
Issue Type:
Bug
Affects Versions:
3.4.3
Assignee:
Eric Sorenson
Components:
Community
Created:
24/Apr/14 10:30 AM
Priority:
Normal
Reporter:
Stephen Benjamin
Given the following code in a puppet manifest:
$foo = '--foo' $bar = '' $baz =--baz
$command = shellquote('asdf',$foo,$bar,$baz)
It produces this value for $command:
asdf --foo \\ --baz
Whereas I think it should produce:
asdf --foo --baz
Add Comment
Jira (PUP-2354) allow duplicate certs does not work with agent/master
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2354 allow duplicate certs does not work with agent/master The issue here does not appear to be a problem with allow_duplicate_certs. What appears to be happening is that the agent never submits a new CSR if it finds an old certificate on the master. Instead, it downloads the old certificate and fails to continue because the old certificate does not match the new private key generated by the agent. allow_duplicate_certs does not come into play until the agent actually submits a CSR. Kylo Ginsberg: Any thoughts about this? If an agent has to generate a new private key, should it automatically submit a CSR for a new cert? Change By: Charlie Sharpsteen Component/s: NetworkingServices Affects Version/s: 3.x 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
Jira (PUP-2354) allow duplicate certs does not work with agent/master
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2354 allow duplicate certs does not work with agent/master Change By: Charlie Sharpsteen Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2361) Shellquote function includes words of 0 length
Title: Message Title
Stephen Benjamin commented on an issue
Re: Shellquote function includes words of 0 length
PR https://github.com/puppetlabs/puppet/pull/2576
Add Comment
Puppet / PUP-2361
Shellquote function includes words of 0 length
Given the following code in a puppet manifest: $foo = '--foo' $bar = '' $baz =--baz $command = shellquote('asdf',$foo,$bar,$baz) It produces this value for $command: asdf --foo \\ --baz Whereas I think it should produce: asdf --foo --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-2362) ssh_authorized_keys temporary file Operation not permitted
Title: Message Title Adam Gibbins created an issue Puppet / PUP-2362 ssh_authorized_keys temporary file Operation not permitted Issue Type: Bug Affects Versions: 3.4.3 Assignee: Unassigned Created: 24/Apr/14 10:43 AM Environment: 64-bit Ubuntu 12.04.4 ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] Priority: Normal Reporter: Adam Gibbins Occasionally (fairly regularly) we've been getting flickers when running Puppet 3.4.3 catalogs: Apr 24 05:50:43 hostname puppet-agent[838]: (/Stage[main]/Users/Users::Create_user[user1]/Ssh_authorized_key[user1]) Could not evaluate: Puppet::Util::FileType::FileTypeFlat could not write /home/user1/.ssh/authorized_keys: Operation not permitted - /tmp/puppet20140424-838-slrj8c-0 It appears the temporary file is owned by a user that was deployed previously in the catalog: agibbins@hostname ~ % ls -l /tmp/puppet20140424-838-slrj8c-0 -rw--- 1 user2 users 573 Apr 24 05:50 /tmp/puppet20140424-838-slrj8c-0
Jira (PUP-2362) ssh_authorized_keys temporary file Operation not permitted
Title: Message Title Andy Parker updated an issue Puppet / PUP-2362 ssh_authorized_keys temporary file Operation not permitted Change By: Andy Parker Component/s: TypesandProviders 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-2362) ssh_authorized_keys temporary file Operation not permitted
Title: Message Title Andy Parker assigned an issue to Kylo Ginsberg I've had several people people bring up this issue to me. It seems to have been around for a while now and ends up causing random failures in puppet runs. Puppet / PUP-2362 ssh_authorized_keys temporary file Operation not permitted Change By: Andy Parker Assignee: KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2309) Yum provider errors on priority undef
Title: Message Title
Sergei Genchev commented on an issue
Re: Yum provider errors on priority undef
Sorry, I mixed things up. Should have seen 'absent' instead of 'undef'. The code that does not work is: { 'centos-6-os-x86_64': baseurl = $url, gpgkey = $gpgkey, priority = 'absent', }
'absent' is a valid value according to http://docs.puppetlabs.com/references/latest/type.html#yumrepo-attribute-priority
Add Comment
Puppet / PUP-2309
Yum provider errors on priority undef
Prior to 3.5 this code worked just fine. yumrepo { 'centos-6-os-x86_64': baseurl = $url, gpgkey = $gpgkey, priority = undef, } After upgrading to 3.5 I get an error: Failed to apply catalog: Parameter priority failed on Yumrepo[centos-6-os-x86_64]: Must be within range 1-99 yumrepo documentation states that und...
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-2363) yumrepo priority absent is still broken.
Title: Message Title Jason A. Smith created an issue Puppet / PUP-2363 yumrepo priority absent is still broken. Issue Type: Bug Affects Versions: 3.5.1 Assignee: Kylo Ginsberg Components: Types and Providers Created: 24/Apr/14 11:24 AM Environment: open source puppet on RHEL6 Priority: Critical Reporter: Jason A. Smith According to the types reference documentation: http://docs.puppetlabs.com/references/latest/type.html#yumrepo-attribute-priority the priority attribute can also take the value 'absent' which should mean that the priority is removed from the repo file, but puppet 3.5.1 currently complains: puppet apply --verbose /tmp/test.pp Error: Parameter priority failed on Yumrepo[test]: Must be within range 1-99 at /tmp/test.pp:3 Wrapped exception: Must be within range 1-99
Jira (PDB-600) Create docs indexes for environments end-point and benchmark docs
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-600 Create docs indexes for environments end-point and benchmark docs Change By: Kenneth Barber Sprint: 20140423to20140507 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-600) Create docs indexes for environments end-point and benchmark docs
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-600 Create docs indexes for environments end-point and benchmark docs Issue Type: Bug Assignee: Unassigned Components: DOCS Created: 24/Apr/14 12:16 PM Fix Versions: 2.0.0 Priority: Normal Reporter: Kenneth Barber We're adding a new end-point for environments, and we're adding docs for benchmark. These both need indexes created in puppet-docs. Add Comment
Jira (PDB-599) PR (946): Fixed inconsistencies in the deprecation warning messages of commands - senior
Title: Message Title gepetto-bot commented on an issue Re: PR (946): Fixed inconsistencies in the deprecation warning messages of commands - senior Pull request Fixed inconsistencies in the deprecation warning messages of commands has been closed. Add Comment PuppetDB / PDB-599 PR (946): Fixed inconsistencies in the deprecation warning messages of commands - senior h2. Fixed inconsistencies in the deprecation warning messages of commands * Author: Ryan Senior senior.r...@gmail.com * Company: * Github ID: [senior|https://github.com/senior] * [Pull Request 946 Discussion|https://github.com/puppetlabs/puppetdb/pull/946] * [Pull Request 946 File Diff|https://github.com/puppetlabs/puppetdb/pull/946/files] h2. 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 (PDB-599) PR (946): Fixed inconsistencies in the deprecation warning messages of commands - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-599 PR (946): Fixed inconsistencies in the deprecation warning messages of commands - senior Change By: Kenneth Barber Sprint: 20140423to20140507 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-598) PR (945): Fix command API Content-Type - dalen
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-598 PR (945): Fix command API Content-Type - dalen Change By: Kenneth Barber Sprint: 20140423to20140507 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-599) PR (946): Fixed inconsistencies in the deprecation warning messages of commands - senior
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-599 PR (946): Fixed inconsistencies in the deprecation warning messages of commands - senior Change By: Kenneth Barber Story Points: 1 Fix Version/s: 2.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 (PDB-598) PR (945): Fix command API Content-Type - dalen
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-598 PR (945): Fix command API Content-Type - dalen Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2182) Package resource not working as expected in 3.5.0
Title: Message Title
Sergei Genchev commented on an issue
Re: Package resource not working as expected in 3.5.0
I have another use case in 3.5.1 where it breaks my code and I am not sure how to work around it. I want to use rsyslog instead of syslog on all my servers, so in my manifest I have:
package { 'syslog':
ensure = 'absent',
}
package {'rsyslog':
ensure = latest,
}
In this example, once I have syslog uninstalled, puppet will also remove rsyslog (because it provides syslog) and then install it again (because it is being told to do so).
Add Comment
Puppet / PUP-2182
Package resource not working as expected in 3.5.0
One of my modules has the following code: {code} package { 'inetd': ensure = absent; } {code} On the next Puppet run, Puppet tries to remove the xinetd package (debug output): {code} Debug: Executing '/bin/rpm -q inetd --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' Debug: Executing '/bin/rpm -q i...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2047) Create branch and update CI for Puppet 4
Title: Message Title Charlie Sharpsteen commented on an issue Re: Create branch and update CI for Puppet 4 Breanch created: https://github.com/puppetlabs/puppet/tree/puppet-4 Now we need to get CI up and running. Add Comment Puppet / PUP-2047 Create branch and update CI for Puppet 4 We're starting to look at committing code for Puppet 4, but we still plan to develop 3.x releases. In order to have these parallel lines of development we need to have an independent branch for code that is only destined for Puppet 4. This will require the following at a minimum: * Create and push a new branch for Puppet 4 * Clone CI jobs for t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2182) Package resource not working as expected in 3.5.0
Title: Message Title
Peter Huene commented on an issue
Re: Package resource not working as expected in 3.5.0
From this feedback, it sounds like ensure = absent should not check for virtual packages. The use case here seems to be that you want to ensure some legacy package isn't installed and that some newer version that provides the same name as the legacy package is installed.
The only downside I see to this is that it may be confusing for users to be able to ensure = latest | present a package by a name that they can't uninstall using ensure = absent.
Add Comment
Puppet / PUP-2182
Package resource not working as expected in 3.5.0
One of my modules has the following code: {code} package { 'inetd': ensure = absent; } {code} On the next Puppet run, Puppet tries to remove the xinetd package (debug output): {code} Debug: Executing '/bin/rpm -q inetd --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' Debug: Executing '/bin/rpm -q i...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google
Jira (PUP-2073) Multiple values for diff_args causes diff execution failure
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2073 Multiple values for diff_args causes diff execution failure Change By: Joshua Cooper Component/s: Community 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-2073) PR (2477) Multiple values for diff_args causes diff execution failure
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2073 PR (2477) Multiple values for diff_args causes diff execution failure Change By: Joshua Cooper Summary: PR(2477) Multiplevaluesfordiff_argscausesdiffexecutionfailure 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-2073) PR (2477) Multiple values for diff_args causes diff execution failure
Title: Message Title Joshua Cooper commented on an issue Re: PR (2477) Multiple values for diff_args causes diff execution failure Merged in a78fdb3 to be released in 3.6.0 Add Comment Puppet / PUP-2073 PR (2477) Multiple values for diff_args causes diff execution failure Inserting multiple switches for diff_args in puppet.conf causes diff execution to fail. I experienced this in both Windows and Linux. Example: diff_args = -u --strip-trailing-cr This commit will fix the problem: https://github.com/mshean/puppet/commit/7972585779f3a12cfe62449df3c5e9d3b96c6136 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-2073) PR (2477) Multiple values for diff_args causes diff execution failure
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2073 PR (2477) Multiple values for diff_args causes diff execution failure This was a community contribution that we reviewed at the pr triage on Weds. I didn't realize there was already a ticket filed, and hence didn't include it at the planning meeting. Change By: Joshua Cooper Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2357) Validation missing for meaningless sequences
Title: Message Title Henrik Lindberg commented on an issue Re: Validation missing for meaningless sequences Definition: idem (latin: 'the same') denotes that an _expression_ has no side effect. We can statically determine a subset of expressions that are idem, but not all. To do that, every function would have to declare if they were idem or not. Essentially, the rules then become: BlockExpression - can only have an idem _expression_ last A Class, Define, or Node, may not have a body that ends with an idem _expression_ A literal is idem A literal list is idem if all of its elements are idem A hash is idem if all of its keys and values are idem An interpolated string is idem if its interpolated expressions are idem Case, If / Unless, Selector requires a bit more thought Add Comment Puppet / PUP-2357 Validation missing for meaningless sequences There is currently no validation of the future parser's result wrt. evaluation of meaningless
Jira (PUP-2177) PR (2494) Insecure shipped Cipher settings in Passenger example config
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2177 PR (2494) Insecure shipped Cipher settings in Passenger example config Change By: Joshua Cooper Labels: community github 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-2177) PR (2494) Insecure shipped Cipher settings in Passenger example config
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2177 PR (2494) Insecure shipped Cipher settings in Passenger example config Change By: Joshua Cooper Labels: community github 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-2177) PR (2494) Insecure shipped Cipher settings in Passenger example config
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2177 PR (2494) Insecure shipped Cipher settings in Passenger example config Change By: Joshua Cooper Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-185) No EC2 facts shown on newly-built Amazon Linux host
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Facter / FACT-185 No EC2 facts shown on newly-built Amazon Linux host Change By: Kurt Wall Assignee: KurtWall 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-2279) Add support for 'skip_if_unavailable' parameter to `yumrepo`
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2279 Add support for 'skip_if_unavailable' parameter to `yumrepo` Change By: Kurt Wall Assignee: KurtWall 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-2279) Add support for 'skip_if_unavailable' parameter to `yumrepo`
Title: Message Title
Kurt Wall commented on an issue
Re: Add support for 'skip_if_unavailable' parameter to `yumrepo`
This is pre-verified in master at SHA=a78fdb3. After it passes CI it can be moved straight to resolved. On the shipping puppet 3.5.1, this manifest produces an error. In master at the SHA mentioned, this manifest works:
# x.pp
yumrepo { 'jenny':
skip_if_unavailable = true,
ensure = present,
}
Shipping 3.5.1:
# puppet apply x.pp --verbose
Error: Invalid parameter skip_if_unavailable at /root/puppet/x.pp:4 on node centos6-master.localdomain
Wrapped exception:
Invalid parameter skip_if_unavailable
Error: Invalid parameter skip_if_unavailable at /root/puppet/x.pp:4 on node centos6-master.localdomain
In master:
# puppet apply x.pp --verbose
Notice: Compiled catalog for centos6-master.localdomain in environment production in 0.06 seconds
Info: Applying configuration version '1398379052'
Info: create new repo jenny in file /etc/yum.repos.d/jenny.repo
Notice: /Stage[main]/Main/Yumrepo[jenny]/ensure: created
Info: changing mode of /etc/yum.repos.d/jenny.repo from 600 to 644
Notice: Finished catalog run in 0.04 seconds
Add Comment
Puppet / PUP-2279
Add support for 'skip_if_unavailable' parameter to `yumrepo`
Jira (FACT-185) No EC2 facts shown on newly-built Amazon Linux host
Title: Message Title Corby Wilson commented on an issue Re: No EC2 facts shown on newly-built Amazon Linux host Note: The latest AMI (2014.03.1 = - ami-fb8e9292) will cause all kinds of problems when installing puppet because they switched to ruby20 by default. You will have to: rpm -ivh http://yum.puppetlabs.com/el/6/products/x86_64/puppetlabs-release-6-10.noarch.rpm yum -q -y erase ruby* yum-config-manager --setopt=puppetlabs-deps.priority=10 --save puppetlabs-deps --setopt=puppetlabs-products.priority=10 --save puppetlabs-products yum -q -y install patch ruby18 rubygems18 puppet --exclude=puppet-2.*alternatives --set ruby /usr/bin/ruby1.8 To get puppet to work on the latest AMI. You will see the problem when you try it out Add Comment Facter / FACT-185 No EC2 facts shown on newly-built Amazon Linux host `facter|grep ec2` yields only the 'domain' and 'fqdn' facts for me, not a gaggle of them including stuff like 'ec2_profile'. The same versions on another host are working fine. Any tips on troubleshooting? An strace isn't showing anything promising to me, although it confirms that it's firing up the ec2.rb library. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2182) Package resource not working as expected in 3.5.0
Title: Message Title
Peter Huene commented on an issue
Re: Package resource not working as expected in 3.5.0
I agree that we shouldn't be favoring a convenience feature over maintaining compatibility. The feature in question was that some users expected the package provider (specifically yum) to behave like yum and install packages successfully based on a virtual package name. The pre-3.5.0 behavior was that yum would actually install the package, but rpm would later fail to query it despite the successful installation.
I think we have a few options here: 1. Back out the whatprovides commit so that you can no longer install by virtual package name. 2. Change the provider to not allow uninstall querying with whatprovides, working around the issues we're experiencing here based on the pattern of I don't want this old package with this physical package name, but I do want the replacement package which provides the old name. 3. Keep the whatprovides functionality, but limit it to an explicit opt-in with a feature:
package { 'vim':
ensure = present,
allow_virtual = true
}
Add Comment
Puppet / PUP-2182
Package resource not working as expected in 3.5.0
One of my modules has the following code: {code} package { 'inetd': ensure = absent; } {code} On the next Puppet run, Puppet tries to remove the xinetd package (debug output): {code} Debug: Executing '/bin/rpm -q inetd --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' Debug: Executing '/bin/rpm -q i...
Jira (PUP-2291) yumrepo priority can not be sent to absent
Title: Message Title
Kurt Wall commented on an issue
Re: yumrepo priority can not be sent to absent
This bug is pre-verified in master at SHA=a78fdb3. When it passes CI it can be moved directly to Resolved. The yumrepo attribute now accepts priority = absent:
# x.pp
yumrepo { 'jenny':
priority = absent,
ensure = present,
}
# puppet apply x.pp --verbose
Notice: Compiled catalog for centos6-master.localdomain in environment production in 0.06 seconds
Info: Applying configuration version '1398379823'
Notice: Finished catalog run in 0.03 seconds
# cat /etc/yum.repos.d/jenny.repo
[jenny]
priority=50
Add Comment
Puppet / PUP-2291
yumrepo priority can not be sent to absent
yumrepo{ 'foo': priority = absent, } $ puppet apply test.pp Notice: Compiled catalog for dev050 in environment production in 0.10 seconds Error: Parameter priority failed on Yumrepo[foo]: Must be within range 1-99 at /root/test.pp:4 Wrapped exception: Must be within range 1-99: absent
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2291) yumrepo priority can not be sent to absent
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2291 yumrepo priority can not be sent to absent Change By: Kurt Wall Assignee: KurtWall 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-2292) Insufficient tests on yumrepo's = absent
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2292 Insufficient tests on yumrepo's = absent Change By: Kurt Wall Assignee: KurtWall 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-2292) Insufficient tests on yumrepo's = absent
Title: Message Title
Kurt Wall commented on an issue
Re: Insufficient tests on yumrepo's = absent
This bug is pre-verified in master at SHA=a78fdb3. When it passes CI it can be moved directly to Resolved. The yumrepo attribute now accepts priority = absent:
# x.pp
yumrepo { 'jenny':
priority = absent,
ensure = present,
}
# puppet apply x.pp --verbose
Notice: Compiled catalog for centos6-master.localdomain in environment production in 0.06 seconds
Info: Applying configuration version '1398379823'
Notice: Finished catalog run in 0.03 seconds
# cat /etc/yum.repos.d/jenny.repo
[jenny]
priority=50
Add Comment
Puppet / PUP-2292
Insufficient tests on yumrepo's = absent
When you set = absent on a yumrepo property, the result is a string in ruby. However, it happens that we expect only a symbol there.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the
Jira (PUP-2073) PR (2477) Multiple values for diff_args causes diff execution failure
Title: Message Title Joshua Cooper commented on an issue Re: PR (2477) Multiple values for diff_args causes diff execution failure To reproduce: $ bundle exec puppet config set show_diff true $ bundle exec puppet config set -- diff_args '-u --strip-trailing-cr' $ bundle exec puppet agent --configprint diff_args -u --strip-trailing-cr Create an empty file: $ touch /tmp/newfile Create a file manifest with some content with newlines, e.g. content = hello\nworld\n Apply the manifest with --debug and you should see a diff that ignores newlines: $ bundle exec puppet apply file.pp --debug ... Debug: Executing 'diff -u --strip-trailing-cr /tmp/newfile /var/folders/2q/qhdc5tpx4knd4pjr1hdskmjcgn/T/puppet-file20140424-38379-1qwccx0' Notice: /Stage[main]/Main/File[/tmp/newfile]/content: --- /tmp/newfile 2014-04-24 16:15:29.0 -0700 +++ /var/folders/2q/qhdc5tpx4knd4pjr1hdskmjcgn/T/puppet-file20140424-38379-1qwccx0 2014-04-24 16:15:36.0 -0700 @@ -0,0 +1,2 @@ +hello +world Previously, you would see the debug statement that it was executing the diff command, but nothing would actually be printed Add Comment Puppet / PUP-2073 PR (2477) Multiple values for diff_args causes diff execution failure
Jira (PUP-2182) Package resource not working as expected in 3.5.0
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Package resource not working as expected in 3.5.0
Michael Stahnke do you have any input on this? This is a fallout consideration from the support for virtual packages you advocated for, so your thoughts would be appreciated.
Add Comment
Puppet / PUP-2182
Package resource not working as expected in 3.5.0
One of my modules has the following code: {code} package { 'inetd': ensure = absent; } {code} On the next Puppet run, Puppet tries to remove the xinetd package (debug output): {code} Debug: Executing '/bin/rpm -q inetd --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' Debug: Executing '/bin/rpm -q i...
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-2182) Package resource not working as expected in 3.5.0
Title: Message Title
Sergei Genchev commented on an issue
Re: Package resource not working as expected in 3.5.0
Option 1 is certainly a possibility as far as I am concerned. Probably, the easiest to implement.
Option 2 does not look like it would solve jre use case above, unless I am mistaken.
Option 3 to me sounds like the best solution if it can be implemented.
Add Comment
Puppet / PUP-2182
Package resource not working as expected in 3.5.0
One of my modules has the following code: {code} package { 'inetd': ensure = absent; } {code} On the next Puppet run, Puppet tries to remove the xinetd package (debug output): {code} Debug: Executing '/bin/rpm -q inetd --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' Debug: Executing '/bin/rpm -q i...
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.
Jira (PUP-2164) require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
Title: Message Title
Bryce Johnson commented on an issue
Re: require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
puppet should not be loading certain aspects of itself to perform certain operations, but I believe that is a separate issue
Andy Parker will there be a JIRA for that?
Add Comment
Puppet / PUP-2164
require 'puppet' now throws an error in 3.5.0 with Ruby 1.8.7 as rubygems is not initialized
We now ship {{rubygems-json}} for EL 6.x as a dependency of Puppet 3.5.0. However, Ruby 1.8.7 does not initialize the Gem search paths by default which leads to the following error: {noformat} # yum install -y puppet-3.5.0-1.el6 # ... much yum output ... # ruby -e ' require puppet ' /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3:in `require':...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Rudy McComb commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log This is a similar to an issue on 10.9.2 OSX, happens at random. This error occurs even though the run completed successfully. Level Resource message err Puppet Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation err Puppet Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation info Puppet Redefining component in Puppet::Type err /File[/var/lib/puppet/lib] Failed to generate additional resources using 'eval_generate': undefined method `exist?' for Puppet::FileSystem:Module info Puppet Retrieving plugin Nothing to show Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-459) MTU interface facts not being reported on Archlinux.
Title: Message Title Peter Huene updated an issue Facter / FACT-459 MTU interface facts not being reported on Archlinux. Change By: Peter Huene Assignee: PeterHuene EricSorenson 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-2309) Yum provider errors on priority undef
Title: Message Title Sergei Genchev assigned an issue to Adrien Thebo Not sure if it is appropriate for me to reassign it to you. I am sorry if I broke some written or unwritten rules. Please point me to puppet jira 101 page if there is one. Thank you! Puppet / PUP-2309 Yum provider errors on priority undef Change By: Sergei Genchev Assignee: SergeiGenchev AdrienThebo 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-2182) Package resource not working as expected in 3.5.0
Title: Message Title
Peter Huene commented on an issue
Re: Package resource not working as expected in 3.5.0
Sergei Genchev Correct, #2 won't fix the jre package issue that Sean Edge is seeing. I'm still having problems reproducing that particular problem.
Sean Edge Sorry I didn't reply sooner, I missed the notification that you had replied to the issue. With the debug output above, it doesn't appear to be installing any package; was the Oracle jre or java package already installed when you ran puppet for that particular output? Additionally, judging from your earlier output, yum finds the jre package in the latest repo when doing just yum install jre. Is this a local repo you've created or something else?
Add Comment
Puppet / PUP-2182
Package resource not working as expected in 3.5.0
One of my modules has the following code: {code} package { 'inetd': ensure = absent; } {code} On the next Puppet run, Puppet tries to remove the xinetd package (debug output): {code} Debug: Executing '/bin/rpm -q inetd --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}\n' Debug: Executing '/bin/rpm -q i...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
