Jira (PUP-3000) Could not get fact fqdn/ipaddress
Title: Message Title
Naftuli Tzvi Kay updated an issue
Puppet / PUP-3000
Could not get fact fqdn/ipaddress
Change By:
Naftuli Tzvi Kay
I have a weird issue where the Puppet Master is generating a certificate called ".mydomain.com" (ie: ".$domain"). Looking into the logs, I see the following:Aug 1 00:01:14 kungfumaster puppet-master[447]: Could not retrieve fact fqdnAug 1 00:01:14 kungfumaster puppet-master[447]: Could not retrieve fact ipaddressIn the codebase it's located here: https://github.com/puppetlabs/puppet/blob/07a37ff92efac39e264f8279613594c95d650d63/lib/puppet/indirector/catalog/compiler.rb#L169When I insert the following code in the set_server_facts method:Facter.loadfactsPuppet.warning Facter.to_hashI see the following output in syslog:Aug 1 02:10:40 kungfumaster puppet-master[5565]: {"domain"=>"mydomain.com", "timezone"=>"UTC", "uptime"=>"6 days", "memorysize"=>"0.00 MB", "memoryfree"=>"0.00 MB", "memorysize_mb"=>"0.00", "memoryfree_mb"=>"0.00", "ps"=>"ps -ef", "uptime_days"=>6, "uptime_seconds"=>518934, "path"=>":/usr/sbin:/sbin", "puppetversion"=>"3.6.2", "augeasversion"=>"1.2.0", "sshdsakey"=>"B3NzaC1kc3MAAACBALgbR5MWx0PsKsLGV9o+krvqbiSc55TKavimNdXKjDGTZ6GQQ8CjyJKP52rt2QrxwkiCcFk+KibsY1VOyBVdZvH5fWo551xqpSVt9YaY74SxgyvVMcX6ROVTbm3jWVBlEzS312jtoMFbWZMxQP2CN2IOi9wu15+sHj8VUTqihRShFQDFWCgbS/u9Ld3o/Oyvq1Ab3SOORQAAAIACfGOvHQb5jVXmsQWi1HKOsVQx8mC2qXwa8bqQSHTN1O+91vQ9czjZY/ZlibvBirtqlG3L14kMDehzf9GueVgzF7YK8UVYx5AsZ3GBp/xUw6QmQV874RwKq8PO4+j8ze4/xi3oiJKQOHWWN5HHAiW4bMFaqTfY9ClIDyiY290vhIBEhHD1qvlZAqVtg83Itmz9qArM9KghkWpT3TIqcCCCVJaQahX9ESj/i28bDSyMpPsUpga/7yPGpZ1x997a37Ez3wR/+KNkjCN3FkjY1Kr3C64v4JWAviQid33V3wJfpVI+VIfayR/OS8qy1ZrIqdUlsiLr27TBg/umZmtfx1g9Iw==", "sshfp_dsa"=>"SSHFP 2 1 ba4c2e9a86297ff0ad38b522425d624d888ce778\nSSHFP 2 2 25c636a0682c8ea0d546aaa2ab4e12016ea6cfc603a241a84c0907fc9c22a388", "sshrsakey"=>"B3NzaC1yc2EDAQABAAABAQCfOO6ZxMjN53A6XpEs/yUFhp5GhDem6gCcMxfYTNvcyaEFiaVb7p6F9C3aFVs6cf2rG6/ToHktMWvdn4ctNFaH1kwGvlY7BJvsqQ9MlYhIHYb23Uk+9PE83d6aNJuvR8QuEtZAmBq1Wwku5c0G4gHVvJj/U/NaZlTE70JSyMax5EGo8m0JYiFL4Z+pQubUi3rqwRGhZYsyXwzZrAMfWsuG+sPUCPpejoUY/XXRIwQ3gfvsbzrn99zVeGxQ90eZkAQTs+s/iEiWQ8zToMG0PyYu/Dht52gu98GfZqC8yT7mCwl771u9IcibdyHU+XHFRyWO89avpbUDgIpSafH1bJJj", "sshfp_rsa"=>"SSHFP 1 1 a02b44bd5d841119d359a38cdec285f4e107a12f\nSSHFP 1 2 1337686dc142d375e803c9b09413509629141baa0e7abe1d2aa8fb7a88369883", "sshecdsakey"=>"E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBC8AtVEIzCTjKv1efUC7AGPqcqnrSrbe5Mt3tVhhT9lP2Rn8ZtCQYwaey+YKvbs7wEFZ+BEeR2aMnjXPXSoWcGc=", "sshfp_ecdsa"=>"SSHFP 3 1 02935f27031c5b8a1ea125ba0e7c99c78722b407\nSSHFP 3 2 2f95d655a7fe1a41ce15e23721678a0cdb4acc36bbeaba1642588b996dbc1975", "sshed25519key"=>"C3NzaC1lZDI1NTE5IK3eXW1MyH61XmaLCmii1uNH2L5DAmg1GbroeTWahV/7", "sshfp_ed25519"=>"SSHFP 4 1 479b19005f3f428e031753bce06ef2ea5e02086e\nSSHFP 4 2 fe6ffd9e147621fbef429b3e190c4cdc56e1ac1b8a368682f183bd8cc0c1f85e", "facterversion"=>"2.1.0", "rubysitedir"=>"/usr/local/lib/site_ruby/1.9.1", "uptime_hours"=>144, "rubyversion"=>"1.9.3"}As you can see, there's no IP address present there or FQDN in the facts for some reason. Using Ruby on the same machine, I can get the FQDN and IP address facts easily: require "facter" puts Facter.value("fqdn") puts Facter.value("ipaddress")The above code works without any problems just runnin
Jira (PUP-3000) Could not get fact fqdn/ipaddress
Title: Message Title Naftuli Tzvi Kay commented on an issue Re: Could not get fact fqdn/ipaddress Since I'm essentially using the provided rack configuration file which is installed by Puppet in /usr/share/puppet/ext/rack/config.ru, I'm not sure why it's not able to load the ipaddress and fqdn facts. Add Comment Puppet / PUP-3000 Could not get fact fqdn/ipaddress I have a weird issue where the Puppet Master is generating a certificate called ".mydomain.com" (ie: ".$domain"). Looking into the logs, I see the following: Aug 1 00:01:14 kungfumaster puppet-master[447]: Could not retrieve fact fqdn Aug 1 00:01:14 kungfumaster puppet-master[447]: Could not retrieve fact ipaddress In the codebase it's locate... 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
Jira (PUP-3000) Could not get fact fqdn/ipaddress
Title: Message Title Naftuli Tzvi Kay created an issue Puppet / PUP-3000 Could not get fact fqdn/ipaddress Issue Type: Bug Affects Versions: 3.6.2 Assignee: Andy Parker Components: Server Created: 31/Jul/14 7:29 PM Environment: https://github.com/rfkrocktk/docker-puppetmaster . Ubuntu 14.04 amd64, Docker container, using the Puppet APT repository with the latest Puppet version. No other bugs except for this, fully-functional master and agent. Labels: github Priority: Normal Reporter: Naftuli Tzvi Kay I have a weird issue where the Puppet Master is generating a certificate called ".mydomain.com" (ie: ".$domain"). Looking into the logs, I see the following: Aug 1 00:01:14 kungfumaster puppet-master[447]: Could not retrieve fact fqdn Aug 1 00
Jira (PUP-2999) Merge clay-davis branch of FOSS puppet into upstream repository.
Title: Message Title Wayne Warren moved an issue Puppet / PUP-2999 Merge clay-davis branch of FOSS puppet into upstream repository. Change By: Wayne Warren Component/s: JVM Puppet Master Component/s: Test Infrastructure Affects Version/s: 3.4.0 Affects Version/s: 3.4.0 Workflow: Puppet Enterprise Platform Workflow Key: PE PUP - 4847 2999 Project: Puppet Enterprise [Internal] Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-390) Modify build process to generate x86 and x64 versions of ruby
Title: Message Title Ethan Brown commented on an issue Re: Modify build process to generate x86 and x64 versions of ruby Melissa Stone is working on the necessary Jenkins job changes http://jenkins-release.delivery.puppetlabs.net/job/MelissaBuildsWindows3.xOnDemand/ to get this properly building x86 / x64 configs. Add Comment Puppet / PUP-390 Modify build process to generate x86 and x64 versions of ruby The [build process|https://github.com/puppetlabs/puppet_for_the_win] needs to be able to package x86 and x64 versions of ruby with the appropriate set of gems (some containing native code), which is then packaged up into two puppet MSI installers. 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-1965) Clients are hung when server has intermittent service
Title: Message Title Mike Fitzgerald commented on an issue Re: Clients are hung when server has intermittent service I have updated ruby on these clients to version 1.9.3 and the problem looks to no longer be occurring. Add Comment Puppet / PUP-1965 Clients are hung when server has intermittent service Unrelated server in data center (same subnet) comes under DOS attack. Network service to other machines in subnet is slow, sparse and subject to failure during this time. All puppet clients that attempt to connect / update during this period are hung. Process list shows puppet agent service process and 'puppet agent: applying configuration' process. ... 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-1680) "incorrect header check" using Ruby 2
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1680 "incorrect header check" using Ruby 2 Change By: Josh Cooper Summary: "incorrect header check" using Ruby 2 .1.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-769) Deprecate pre 9.3 PostgreSQL
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-769 Deprecate pre 9.3 PostgreSQL Change By: Kenneth Barber Assignee: Kenneth Barber 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-798) Regexp querying support against path for /facts-node
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-798 Regexp querying support against path for /facts-node Issue Type: New Feature Assignee: Unassigned Created: 31/Jul/14 3:49 PM Fix Versions: 2.2.0 Priority: Normal Reporter: Kenneth Barber 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 em
Jira (PDB-797) Add 'fact' field to 'fact-nodes'
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-797 Add 'fact' field to 'fact-nodes' Change By: Kenneth Barber Sprint: 20140813 20140730 to 20140827 20140813 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-798) Regexp querying support against path for /facts-node
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-798 Regexp querying support against path for /facts-node Change By: Kenneth Barber Sprint: 20140813 to 20140827 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-746) Query support for structured facts /facts-something - Globbing support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-746 Query support for structured facts /facts-something - Globbing support Change By: Kenneth Barber Summary: Query support for structured facts /facts-something - Globbing /Regexp support 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-2991) User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2991 User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10 Change By: Kylo Ginsberg Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-765) Puppetdb connection to postgresql using client certificate
Title: Message Title Kenneth Barber commented on an issue Re: Puppetdb connection to postgresql using client certificate Justin Holguin yes please to fixing up that documentation, if we can prove it works we shouldn't keep pushing the old crappy method. As far as your comment about globals, yes I believe this to be true actually. I adapted that pattern for postgresql with this kind of thing in mind actually, just completely forgot about it . Add Comment PuppetDB / PDB-765 Puppetdb connection to postgresql using client certificate For people wanting to authenticate on a posgresql server, using a X509 client certificate, this procedure might help. This procedure does it in the java way, ie it take a jks store, not pem files. First create a jks with the private key for your account and put in it all the needed certificates in the chain (both server and user). The cn for user cert... 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 e
Jira (PDB-765) Puppetdb connection to postgresql using client certificate
Title: Message Title Justin Holguin commented on an issue Re: Puppetdb connection to postgresql using client certificate Kenneth Barber Ok, I see what you're saying. I wasn't enthusiastic about modifying the global keystore, but it seemed like the thing to do based on the docs. If it's not advisable, then I can have a go at rewriting that section myself to use the LibPQFactory method. The reason I had to disable DB management was just so that I could install Postgres 9.2. RHEL 6 ships 8.4, so you need to modify postgresql::globals in order to get the right version. Thinking about it now, I suppose it should be possible to apply the globals class before puppetdb and get the same effect? Add Comment PuppetDB / PDB-765 Puppetdb connection to postgresql using client certificate For people wanting to authenticate on a posgresql server, using a X509 client certificate, this procedure might help. This procedure does it in the java way, ie it take a jks store, not pem files. First create a jks with the private key for your account and put in it all the needed certificates in the chain (both server and user). The cn for user cert... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1427) a metaparameter to control the timeout of that resource evaluation/application, along with a default value.
Title: Message Title Patrick Hemmer commented on an issue Re: a metaparameter to control the timeout of that resource evaluation/application, along with a default value. I think a default infinity would be fine as long as there were a way to globally set it. You can set resource defaults per resource type, but if there's a way to set a parameter for all resources types, I am unaware of what it is. Every time I've been bitten by this issue, it's been on a resource that was not expected (a package installation, a service restart, etc). I know my systems, and that puppet never takes more than a minute or so for any given resource, so I'd like to set a global default of 5 minutes. Add Comment Puppet / PUP-1427 a metaparameter to control the timeout of that resource evaluation/application, along with a default value. I had some service (iscsid) which hung for ever for some reason (missing config file), when stopping it via `service iscsid stop`. As puppet should stop that service, puppet hung as well. Over days... I think it's pretty reasonable to expect services to be stopped after some time (like 10 minutes?) and if they didn't return so far, give up (and kill... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1427) a metaparameter to control the timeout of that resource evaluation/application, along with a default value.
Title: Message Title Zachary Stern commented on an issue Re: a metaparameter to control the timeout of that resource evaluation/application, along with a default value. +1 to Charlie's idea. "As a sysadmin" I would expect most resources to "just work" most of the time, and to have perhaps one or two that misbehave, that I could set a timeout on. Add Comment Puppet / PUP-1427 a metaparameter to control the timeout of that resource evaluation/application, along with a default value. I had some service (iscsid) which hung for ever for some reason (missing config file), when stopping it via `service iscsid stop`. As puppet should stop that service, puppet hung as well. Over days... I think it's pretty reasonable to expect services to be stopped after some time (like 10 minutes?) and if they didn't return so far, give up (and kill... 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. T
Jira (PDB-765) Puppetdb connexion to postgresql using client certificate
Title: Message Title Kenneth Barber commented on an issue Re: Puppetdb connexion to postgresql using client certificate Justin Holguin I can release the module whenever we need to I guess. What particular reason do you have for having to turn off the db management in the PDB module? I'm just curious because it looked like all the settings you have in that GIST are correct. Oh and BTW, you're not quite following the route Brian Cain had laid out, in particular his instructions did not require modifying the global JKS, which is actually a bit of a bad thing. Instead it uses the libpqfactory method, you can see this outlined here: http://docs.puppetlabs.com/puppetdb/master/postgres_ssl.html#using-your-own-self-signed-ca. Having another look at that documentation, ideally even the Puppet cert instructions need to be modified to use this really instead of JKS. I think I made a mess of the documentation review, I guess I wasn't paying enough attention at the time. If you want a better explanation ping me on hipchat or something. Add Comment PuppetDB / PDB-765 Puppetdb connexion to postgresql using client certificate For people wanting to authenticate on a posgresql server, using a X509 client certificate, this procedure might help. This procedure does it in the java way, ie it take a jks store, not pem files. First create a jks with the private key for your account and put in it all the needed certificates in the chain (both server and user). The cn for user cert... This mess
Jira (PDB-765) Puppetdb connection to postgresql using client certificate
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-765 Puppetdb connection to postgresql using client certificate Change By: Kenneth Barber Summary: Puppetdb connexion connection to postgresql using client certificate 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-1427) a metaparameter to control the timeout of that resource evaluation/application, along with a default value.
Title: Message Title Charlie Sharpsteen commented on an issue Re: a metaparameter to control the timeout of that resource evaluation/application, along with a default value. It sounds like a good first iteration for this feature would be to implement the metaparameter with the timeout defaulting to infinity. This would leave the current behavior of catalog application unchanged while providing the tools to control resource timeouts for those who need them. Add Comment Puppet / PUP-1427 a metaparameter to control the timeout of that resource evaluation/application, along with a default value. I had some service (iscsid) which hung for ever for some reason (missing config file), when stopping it via `service iscsid stop`. As puppet should stop that service, puppet hung as well. Over days... I think it's pretty reasonable to expect services to be stopped after some time (like 10 minutes?) and if they didn't return so far, give up (and kill... 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
Jira (PDB-765) Puppetdb connexion to postgresql using client certificate
Title: Message Title Justin Holguin commented on an issue Re: Puppetdb connexion to postgresql using client certificate Kenneth Barber I managed to replicate Brian Cain's results with PuppetDB 2.1.0 and Puppet 3.6.2 (open source), but there were many more steps involved. If you like, you can check out my notes/pre-docs from the process in this gist. Bottom line, I found two major issues: 1. I had to check out puppetlabs-puppetdb from GitHub because I needed to be able to set the manage_dbserver parameter to false, and the latest version on the Forge doesn't have that parameter. Without it, the module will install PostgreSQL 8.4 on RHEL 6, which doesn't support this kind of configuration. 2. The new HBA rule has to be added as a puppet resource or any changes will just get overwritten. My question really is this: when do you think there will be a new release of the module? I'm not very enthusiastic about publishing this doc until the manage_dbserver param is part of an official release. Alternatively, if there's a workaround that I'm missing then that would also help. Add Comment PuppetDB / PDB-765 Puppetdb connexion to postgresql using client certificate For people wanting to authenticate on a posgresql server, using a X509 client certificate, this procedure might help. This procedure does it in the java way, ie it take a jks store, not pem files. First create a jks with the private key for your account and put in it all the needed certificates in the chain (both server and user). The cn for user cert...
Jira (PUP-511) Specify Resource Expression Evaluation
Title: Message Title Henrik Lindberg commented on an issue Re: Specify Resource _expression_ Evaluation Merged PR 15 to specs. Add Comment Puppet / PUP-511 Specify Resource _expression_ Evaluation Resource _expression_ Evaluation requires a specification of the behavior. Here are some examples of issues in need of resolution: * if title is undef - error * if title is an array, several resources are created - what happens if and entry is undef? Is this silently ignored, or is it an error? * suggest it is an error (i.e. user would have to ... 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-2388) Run Puppet acceptance against ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2388 Run Puppet acceptance against ruby 2.0 x64 Change By: Josh Cooper Flagged: Impediment 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-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-391 Validate FFI'ed native windows code against Ruby 2 x64 Change By: Josh Cooper Flagged: Impediment 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-511) Specify Resource Expression Evaluation
Title: Message Title Andy Parker commented on an issue Re: Specify Resource _expression_ Evaluation Opened Specs PR 15 to allow nested arrays of titles. Add Comment Puppet / PUP-511 Specify Resource _expression_ Evaluation Resource _expression_ Evaluation requires a specification of the behavior. Here are some examples of issues in need of resolution: * if title is undef - error * if title is an array, several resources are created - what happens if and entry is undef? Is this silently ignored, or is it an error? * suggest it is an error (i.e. user would have to ... 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-2860) Optimize startup of puppet apply (future parser)
Title: Message Title
Andy Parker commented on an issue
Re: Optimize startup of puppet apply (future parser)
Merged into master in d117e3.
I believe that this can skip functional review. There are no functional changes in this. The benchmark jenkins jobs should show whether it actually had a measurable improvement in any scenarios and the rest of the tests should have enough coverage for catching any regressions.
Add Comment
Puppet / PUP-2860
Optimize startup of puppet apply (future parser)
The {{puppet apply}} command is very often used as a development tool testing small snippets of puppet as well as larger scenarios. Users may thus the command over and over again. Any delays are very irritating (the smaller the snippet being tested, the more irritation). This creates an impression of Puppet's speed when used in production. (which is 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...@googlegrou
Jira (PUP-1427) a metaparameter to control the timeout of that resource evaluation/application, along with a default value.
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-1427 a metaparameter to control the timeout of that resource evaluation/application, along with a default value. Change By: Eric Sorenson Assignee: Charlie Sharpsteen 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-1427) a metaparameter to control the timeout of that resource evaluation/application, along with a default value.
Title: Message Title Eric Sorenson commented on an issue Re: a metaparameter to control the timeout of that resource evaluation/application, along with a default value. I agree with the comments on the original redmine that it seems like a pretty reasonable thing to want. I can think of two areas offhand that need some design consideration: 1. In my experience there are lots of these actions which stall out in uninterruptible/unkillable ways, like an NFS mount going away, so the implementation would need to take that into consideration. The worst thing would be littering the process table with tons of orphaned commands. 2. I've seen intentionally very-long-running manifests (~2hr) where people are installing a database and restoring data into it; we'd need to preserve the current ability for resources to take un-know-ably long periods of time to complete. Charlie Sharpsteen given the support escalations can you shepherd this ticket and make sure it gets some attention? I'm targeting it in the 4.x series, so not a 4.0 blocker but it oughta come up for scoping/estimation pretty quickly afterwards. Add Comment Puppet / PUP-1427 a metaparameter to control the timeout of that resource evaluation/application, along with a default value. I had some service (iscsid) which hung for ever for some reason (missing config file), when stopping it via `service iscsid stop`. As puppet should stop that service, puppet hung as well. Over days... I think it's pretty reasonable to expect services to be stopped after some time (like 10 minutes?) and if they didn't return so far, give up (and kill...
Jira (PUP-1427) a metaparameter to control the timeout of that resource evaluation/application, along with a default value.
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-1427 a metaparameter to control the timeout of that resource evaluation/application, along with a default value. Change By: Eric Sorenson Fix Version/s: 4.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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2860) Optimize startup of puppet apply (future parser)
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2860 Optimize startup of puppet apply (future parser) Change By: Andy Parker Assignee: Henrik Lindberg Andy Parker 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-716) HTTP API gets stuck
Title: Message Title Kenneth Barber commented on an issue Re: HTTP API gets stuck Some users have reported random entropy problems, and proven that by switching to use /dev/urandom this solves their issues. The symptom similarity is hard to guess without a lot more data however. Anyone who gets this issue should ensure they have this setting in their JAVA_ARGS: -Djava.security.egd=file:/dev/urandom This might not have been placed correctly during a package upgrade, due to the handling around configuration files in dpkg, and rpm. ie. the user usually gets prompted to replace these files, or at least a warning, but mostly the default is not to override them. Add Comment PuppetDB / PDB-716 HTTP API gets stuck Sometimes the HTTP API seems to get completely stuck. Other parts continue working though according to logs. Attaching 10 stack trace dumps taken a few seconds apart with jstack -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 g
Jira (FACT-630) facter 2.1.0 errors out on Mavericks
Title: Message Title Adrien Thebo updated an issue Facter / FACT-630 facter 2.1.0 errors out on Mavericks Change By: Adrien Thebo Summary: factor facter 2.1.0 errors out on Mavericks 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-746) Query support for structured facts /facts-something - Globbing/Regexp support
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-746 Query support for structured facts /facts-something - Globbing/Regexp support Change By: Kenneth Barber Assignee: Kenneth Barber 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-630) factor 2.1.0 errors out on Mavericks
Title: Message Title Brian Warsing commented on an issue Re: factor 2.1.0 errors out on Mavericks I see what is causing this now... The .pkg is installing factor in a different location. I was originally testing with Facter 1.7.4. I then upgraded by running the 2.1.0 installer. The 1.7.4 installer (and presumably others) use pkgroot /Library/Ruby/Site/2.0.0 – the 2.1.0 installer uses /Library/Ruby/Site but does not remove/overwrite the previous versions. So, it's not a problem with Facter, it's a problem with the installer. Add Comment Facter / FACT-630 factor 2.1.0 errors out on Mavericks Previous release 2.0.2 works. Running facter 2.1.0 on Mavericks 10.9.4, just dies with: [09:05:54]fry# facter /Library/Ruby/Site/facter/ec2/rest.rb:6: warning: already initialized constant Facter::EC2::CONNECTION_ERRORS /Library/Ruby/Site/facter/ec2/rest.rb:6: warning: previous definition of CONNECTION_ERRORS was here /Library/Ruby/Site/facter/ec2/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this mes
Jira (PDB-797) Add 'fact' field to 'fact-nodes'
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-797 Add 'fact' field to 'fact-nodes' Change By: Kenneth Barber Sprint: 20140813 to 20140827 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-797) Add 'fact' field to 'fact-nodes'
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-797 Add 'fact' field to 'fact-nodes' Issue Type: Task Assignee: Unassigned Created: 31/Jul/14 10:35 AM Fix Versions: 2.2.0 Priority: Normal Reporter: Kenneth Barber During the development of fact-nodes I've realised we need a 'fact' field so we can do subqueries against /facts. Now Wyatt Alt is adding a column to do just that right now in PDB-772. Since the fact-nodes patch landed sooner, this small ticket is to track the addition of that field after PDB-772 is merged. Add Comment
Jira (PUP-2388) Run Puppet acceptance against ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2388 Run Puppet acceptance against ruby 2.0 x64 Change By: Josh Cooper Flagged: Impediment 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-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-391 Validate FFI'ed native windows code against Ruby 2 x64 Change By: Josh Cooper Flagged: Impediment 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-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-391 Validate FFI'ed native windows code against Ruby 2 x64 Change By: Josh Cooper Flagged: Impediment 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-2388) Run Puppet acceptance against ruby 2.0 x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2388 Run Puppet acceptance against ruby 2.0 x64 Change By: Josh Cooper Flagged: Impediment 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-630) factor 2.1.0 errors out on Mavericks
Title: Message Title Adrien Thebo commented on an issue Re: factor 2.1.0 errors out on Mavericks Could you run facter --trace and provide the output of that? Add Comment Facter / FACT-630 factor 2.1.0 errors out on Mavericks Previous release 2.0.2 works. Running facter 2.1.0 on Mavericks 10.9.4, just dies with: [09:05:54]fry# facter /Library/Ruby/Site/facter/ec2/rest.rb:6: warning: already initialized constant Facter::EC2::CONNECTION_ERRORS /Library/Ruby/Site/facter/ec2/rest.rb:6: warning: previous definition of CONNECTION_ERRORS was here /Library/Ruby/Site/facter/ec2/... 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-2991) User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2991 User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10 Change By: Kylo Ginsberg Sprint: 2014-08-06 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-2991) User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10
Title: Message Title
Kylo Ginsberg commented on an issue
Re: User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10
This was introduced in 3.5.0.
Add Comment
Puppet / PUP-2991
User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10
h4.Summary https://github.com/puppetlabs/puppet/commit/73b0c2b0f59db920a14d4d0951b1f1c40d603cb4. Seems to have broken the shell parameter for the user type in Solaris. One is now unable to specify a user's shell after the user has been created. This currently affects all users utilizing Puppet 3.6.2. h4.Test Code: {code} user { 'jay': ensure ...
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-2991) User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2991 User type shell parameter no longer functions properly in PE 3.3 (Puppet 3.6.2) in Solaris 10 Change By: Kylo Ginsberg Affects Version/s: 3.5.0 Affects Version/s: 3.5.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2989) 3.x "profile = true" and "--profile" does nothing.
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2989 3.x "profile = "" and "--profile" does nothing. Change By: Charlie Sharpsteen Assignee: Celia Cottle Charlie Sharpsteen 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-2998) Allow log_level option to be specified in configuration file in addition to command line
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2998 Allow log_level option to be specified in configuration file in addition to command line Change By: Charlie Sharpsteen Assignee: Charlie Sharpsteen 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-2998) Allow log_level option to be specified in configuration file in addition to command line
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2998 Allow log_level option to be specified in configuration file in addition to command line Change By: Charlie Sharpsteen Summary: Allow verbose and debug options log_level option to be specified in configuration file in addition to command line 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-2998) Allow verbose and debug options to be specified in configuration file in addition to command line
Title: Message Title redmine.exporter created an issue Puppet / PUP-2998 Allow verbose and debug options to be specified in configuration file in addition to command line Issue Type: New Feature Assignee: Unassigned Created: 31/Jul/14 8:28 AM Labels: redmine Priority: Normal Reporter: redmine.exporter If the verbose or debug option is set in /etc/puppet/puppet.conf, the puppet agent doesn't seem to respect them. It seems that these two options can only be set on the command line. Being able to set them in the configuration file would be helpful when debugging puppet agents running into system on EC2. Add Comment
Jira (FACT-630) factor 2.1.0 errors out on Mavericks
Title: Message Title Brian Warsing commented on an issue Re: factor 2.1.0 errors out on Mavericks No. Facter was installe fusing the provided package. No puppetlabs gems are installed. [08:21:55]fry# which ruby /usr/bin/ruby [08:22:10]fry# ruby -v ruby 2.0.0p451 (2014-02-24 revision 45167) [universal.x86_64-darwin13] [08:22:19]fry# gem list LOCAL GEMS *** bigdecimal (1.2.0) CFPropertyList (2.2.0) io-console (0.4.2) json (1.7.7) libxml-ruby (2.6.0) minitest (4.3.2) nokogiri (1.5.6) psych (2.0.0) rake (0.9.6) rdoc (4.0.0) sqlite3 (1.3.7) test-unit (2.0.0.0) [08:22:28]fry# facter /Library/Ruby/Site/facter/ec2/rest.rb:6: warning: already initialized constant Facter::EC2::CONNECTION_ERRORS /Library/Ruby/Site/facter/ec2/rest.rb:6: warning: previous definition of CONNECTION_ERRORS was here /Library/Ruby/Site/facter/ec2/rest.rb:48: warning: already initialized constant Facter::EC2::Metadata::DEFAULT_URI /Library/Ruby/Site/facter/ec2/rest.rb:48: warning: previous definition of DEFAULT_URI was here /Library/Ruby/Site/facter/ec2/rest.rb:112: warning: already initialized constant Facter::EC2::Userdata::DEFAULT_URI /Library/Ruby/Site/facter/ec2/rest.rb:112: warning: previous definition of DEFAULT_URI was here /Library/Ruby/Site/facter/gce/metadata.rb:8: warning: already initialized constant Facter::GCE::Metadata::CONNECTION_ERRORS /Library/Ruby/Site/facter/gce/metadata.rb:8: warning: previous definition of CONNECTION_ERRORS was here /Library/Ruby/Site/facter/gce/metadata.rb:20: warning: already initialized constant Facter::GCE::Metadata::METADATA_URL /Library/Ruby/Site/facter/gce/metadata.rb:20: warning: previous definition of METADATA_URL was here Error: Could not find fact 'define_fact' Add Comment Facter / FACT-630
Jira (PUP-2989) 3.x "profile = true" and "--profile" does nothing.
Title: Message Title Charlie Sharpsteen commented on an issue Re: 3.x "profile = "" and "--profile" does nothing. There are definitely some genuine bugs here, notably: log_level and logdest don't do anything when put into puppet.conf. Passing --debug to the master in config.ru does raise the log level and some debugging messages do show up in syslog. However, profiling messages are missing for some strange reason. In the short term, a documentation patch will probably be the quickest way to make things better. Add Comment Puppet / PUP-2989 3.x "profile = "" and "--profile" does nothing. Currently, adding "profile = "" or doing runs with --debug and --profile (since you need debug with it) returns none of the PROFILE lines mentioned in the documentation, or as far as I can tell, any extra output at all. I restarted services, tried it a few times, checked the logs repeatedly, nothing. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2997) Logdest cannot be set in the puppet.conf
Title: Message Title redmine.exporter created an issue Puppet / PUP-2997 Logdest cannot be set in the puppet.conf Issue Type: New Feature Assignee: Unassigned Created: 31/Jul/14 8:17 AM Labels: redmine customer Priority: Normal Reporter: redmine.exporter This is potentially a duplicate issue of a few things floating around out there, but most focus on masterlog, so I'm opening this up separately. Currently you can use --logdest /var/log/somelogfile, but you cannot set it in the puppet.conf. This seems like an oversight, especially since there seems to be a good number of people who wish to keep all puppet logs out of /var/log/messages. There are ways around this (etc/init.d/pe-puppet), but they are purely workarounds. It looks like some of the reason for this is the old masterlog option, which it seems is no longer in use, used to be the preferred way of setting in the puppet.conf. Potentially related tickets: https://projects.puppetlabs.com/issues/5952 https://projects.puppetlabs.com/issues/4550 https://projects.puppetlabs.com/issues/12361 Add Comment
Jira (PUP-2997) Logdest cannot be set in the puppet.conf
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2997 Logdest cannot be set in the puppet.conf Change By: Charlie Sharpsteen Assignee: Charlie Sharpsteen 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-877) Deprecate "masterlog" Setting
Title: Message Title Charlie Sharpsteen commented on an issue Re: Deprecate "masterlog" Setting Pull request submitted. Add Comment Puppet / PUP-877 Deprecate "masterlog" Setting "masterlog" appears in our "defaults" option list for the master, as well as in our documentation (e.g. http://docs.puppetlabs.com/references/2.7.9/configuration.html ). However it does not appear to be used in the code anywhere (it seems that --logdest is the preferred method for dealing with this these days). There were some tickets related to thi... 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-877) Deprecate "masterlog" Setting
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-877 Deprecate "masterlog" Setting Change By: Charlie Sharpsteen Assignee: Charlie Sharpsteen 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-877) Deprecate "masterlog" Setting
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-877 Deprecate "masterlog" Setting Change By: Charlie Sharpsteen Assignee: Charlie Sharpsteen 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-2996) user expiry expect numeric
Title: Message Title
Danny Tung created an issue
Puppet / PUP-2996
user expiry expect numeric
Issue Type:
Bug
Affects Versions:
3.4.3
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
31/Jul/14 7:27 AM
Environment:
Open Source Puppet 3.4.3 (Client and Master) All in RHEL 6.3
Priority:
Normal
Reporter:
Danny Tung
Based on documentation https://projects.puppetlabs.com/issues/14170 user { "joesmoe": expiry => absent, }
that is the implementation to set the account not being expired at all.
In my environment, the error give me back: Error: /Stage[main]/Tomcat/User[tomcat7]: Could not evaluate: expected numeric
I did isolated to that attribute, not others inside the "user" resource.
Jira (PUP-2994) puppet parser validate shouldn't puke on exported resources
Title: Message Title
Henrik Lindberg commented on an issue
Re: puppet parser validate shouldn't puke on exported resources
with --parser future it is a warning if storeconfigs are not configured
Add Comment
Puppet / PUP-2994
puppet parser validate shouldn't puke on exported resources
{code} [root@master /etc/puppetlabs/puppet/modules/hosts]# puppet parser validate manifests/init.pp Warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 25 in file /etc/puppetlabs/puppet/modules/hosts/manifests/init.pp {code} This kinda makes {{puppet parser validate}} really non user ...
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-2994) puppet parser validate shouldn't puke on exported resources
Title: Message Title
Henrik Lindberg commented on an issue
Re: puppet parser validate shouldn't puke on exported resources
This is built into the parser in 3.x. We recently changed this in PUP-2898, and the validation moved to the separate validator. It should really be a runtime check and not a static check, but this is not much easier to do since the check is broken out from the parser itself.
We should fix this for 3.7, future parser.
Add Comment
Puppet / PUP-2994
puppet parser validate shouldn't puke on exported resources
{code} [root@master /etc/puppetlabs/puppet/modules/hosts]# puppet parser validate manifests/init.pp Warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 25 in file /etc/puppetlabs/puppet/modules/hosts/manifests/init.pp {code} This kinda makes {{puppet parser validate}} really non user ...
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
Jira (PUP-2994) puppet parser validate shouldn't puke on exported resources
Title: Message Title
Henrik Lindberg commented on an issue
Re: puppet parser validate shouldn't puke on exported resources
i.e. this check in checker 4.0:
# This is a runtime check - the model is valid, but will have runtime issues when evaluated
# and storeconfigs is not set.
if acceptor.will_accept?(Issues::RT_NO_STORECONFIGS) && o.exported
acceptor.accept(Issues::RT_NO_STORECONFIGS_EXPORT, o)
end
should be become a call to fail in EvaluatorImpl, eval_ResourceExpression.
Add Comment
Puppet / PUP-2994
puppet parser validate shouldn't puke on exported resources
{code} [root@master /etc/puppetlabs/puppet/modules/hosts]# puppet parser validate manifests/init.pp Warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 25 in file /etc/puppetlabs/puppet/modules/hosts/manifests/init.pp {code} This kinda makes {{puppet parser validate}} really non user ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2994) puppet parser validate shouldn't puke on exported resources
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2994 puppet parser validate shouldn't puke on exported resources 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-2994) puppet parser validate shouldn't puke on exported resources
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2994 puppet parser validate shouldn't puke on exported resources Change By: Henrik Lindberg Fix Version/s: 3.7.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-2946) FileUtils implementation broke compare_stream
Title: Message Title
Maksym Melnychok commented on an issue
Re: FileUtils implementation broke compare_stream
code improvement pushed, thanks
Add Comment
Puppet / PUP-2946
FileUtils implementation broke compare_stream
{{FileUtils.compare_stream}} implementation in ruby 1.9.3 was doing something along the lines of {code:ruby} a = b = nil while something a = as.read size b = bs.read size return false if a != b end {code} {{FileUtils.compare_stream}} in 2.0 instead does this: {code:ruby} a = "" b = "" while some...
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-2995) Proposal for custom trusted oid mapping file
Title: Message Title
Remi Ferrand created an issue
Puppet / PUP-2995
Proposal for custom trusted oid mapping file
Issue Type:
Improvement
Assignee:
Andy Parker
Components:
Server
Created:
31/Jul/14 12:56 AM
Priority:
Normal
Reporter:
Remi Ferrand
Hi,
I've been using trusted facts and custom OIDs and I realized that for non puppet-administrators (i.e puppet users) it could be quite confusing to deal with something like
bare_trusted_oid
if $trusted[extensions][1.3.6.1.4.1.34380.1.2.1.1] == 'some_value' { ... }
My proposal is to introduce an external file that could allow puppet administrators to provide a user-friendly mapping like you did for your custom OIDs.
For instance a mapping file such as
example_trusted_oid_mapping_file.yaml
# /etc/puppet/trusted_oid_mapping.yaml
---
oid_mapping:
- ['1.3.6.1.4.1.34380.1.2.1.1', 'shortname', 'Long name']
- ['1.3.6.1.4.1.34380.1.2.1.2', 'othershortname', 'Other Long name']
