Jira (PDB-4369) Hiera IA: Store "inputs" for catalogs and add query for certnames that might be affected by an input
Title: Message Title Daniel Dreier updated an issue PuppetDB / PDB-4369 Hiera IA: Store "inputs" for catalogs and add query for certnames that might be affected by an input Change By: Daniel Dreier Product Owner: Carl Caum Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308640.1557868512000.56247.1561075081522%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4369) Hiera IA: Store "inputs" for catalogs and add query for certnames that might be affected by an input
Title: Message Title Daniel Dreier updated an issue PuppetDB / PDB-4369 Hiera IA: Store "inputs" for catalogs and add query for certnames that might be affected by an input Change By: Daniel Dreier Product Manager: Carl Caum Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308640.1557868512000.56239.1561075081160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7966) Enable Coverity scanning on puppetlabs/puppet
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-7966 Enable Coverity scanning on puppetlabs/puppet Change By: Daniel Dreier Sprint: WHO 2017-02-23 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7966) Enable Coverity scanning on puppetlabs/puppet
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-7966 Enable Coverity scanning on puppetlabs/puppet Change By: Daniel Dreier Sprint: WHO 2017-02-23 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4182) add a flag to get JSON output from puppet resource
Title: Message Title Daniel Dreier commented on PUP-4182 Re: add a flag to get JSON output from puppet resource The really compelling thing about JSON here is basically the jq CLI tool; I'm not aware of a similarly good tool for working with YAML. That said, I don't have an immediate use case for this so it's probably not worth prioritizing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3077) When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment
Title: Message Title Daniel Dreier commented on PUP-3077 Re: When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment Josh Cooper based on the PR description, the new behavior (not saving cached catalogs during noop runs) seems like a reasonable fix to me. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5895) puppet parser validate fails for functions
Title: Message Title
Daniel Dreier created an issue
Puppet / PUP-5895
puppet parser validate fails for functions
Issue Type:
Bug
Assignee:
Unassigned
Components:
Language
Created:
2016/02/12 1:40 PM
Priority:
Normal
Reporter:
Daniel Dreier
The following is valid puppet code in puppet 4, and will run using a puppet apply, but fails a puppet parser validate:
function validate_this() {
notice('hello, puppet')
}
Jira (PUP-5778) dsl-defined functions should accept blocks
Title: Message Title
Daniel Dreier created an issue
Puppet / PUP-5778
dsl-defined functions should accept blocks
Issue Type:
Improvement
Assignee:
Unassigned
Components:
Language
Created:
2016/01/29 3:26 PM
Priority:
Normal
Reporter:
Daniel Dreier
I would like to write functions in the puppet language that accept a block of code, so that I can write my own iterators and other functions that accept code, without the context switch of doing it in ruby.
The specific use case I have is that we often need to run some piece of puppet code once among a group of nodes. To do that, we do a puppetdbquery to find similarly-classified nodes, then sort that list and see if the current node's certname is the first one on the list. If true, run some bit of code.
I would like to write a function like:
function runonce() {
$pdb_leader = join([
Jira (PUP-5778) dsl-defined functions should accept blocks
Title: Message Title Daniel Dreier commented on PUP-5778 Re: dsl-defined functions should accept blocks that sounds awesome. I'm really excited to play with what you come up with. I appreciate the detailed response. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3182) puppet catalog download fails
Title: Message Title Daniel Dreier commented on PUP-3182 Re: puppet catalog download fails Josh Cooper – thanks - I think you are correct that it's a different issue. I'll open a different ticket if I'm able to come up with a good test case. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2007) munging catalog fails with :undef tags
Title: Message Title Daniel Dreier commented on PDB-2007 Re: munging catalog fails with :undef tags it looks like https://ask.puppetlabs.com/question/15272/comparison-of-string-with-undef-failed-puppetmaster-failing-between-submit-facts-and-submit-catalog/ may be the same issue – he traced it to failures when an exported resources was tagged with undef. It looks like we just ran into it again in ops, which surprised me because that's on a pretty old version of PE. https://tickets.puppetlabs.com/browse/OPS-7169 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-29) Notification hooks
Title: Message Title Daniel Dreier commented on PDB-29 Re: Notification hooks Another use case for this will be direct puppet – right now they don't have an answer (as far as I can tell) for the issue of exported resources, puppetdbquery, etc getting changed. For example, if I have a load balancer and web nodes getting classified using facts / ENC, and I bring up a new web node, it'll export a load balancer backend resource but if the load balancer is using direct puppet it will never notice because the code didn't change. Notification hooks in puppetdb would provide the basic capability needed to make that work. If I understand the plans correctly I don't think that they're targeting that capability in the first release, but I suspect that there will be urgent demand for it once it goes into production because it will break a large number of workflows that depend on exported resources. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3182) puppet catalog download fails
Title: Message Title Daniel Dreier commented on PUP-3182 Re: puppet catalog download fails root@consul-server01-dev:~# puppet catalog download --trace Error: Could not call 'find' on 'catalog': Error 403 on SERVER: Forbidden request: 10.224.7.160(10.224.7.160) access to /puppet/v3/catalog/consul-server01-dev.aws.puppetlabs.com [find] at :1 /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/indirector/rest.rb:207:in `is_http_200?' /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/indirector/rest.rb:100:in `find' /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/indirector/indirection.rb:201:in `find' /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/indirector/face.rb:42:in `call_indirection_method' /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/indirector/face.rb:71:in `block (2 levels) in ' /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/interface/action.rb+eval[wrapper]:242:in `find' /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/face/catalog.rb:119:in `block (4 levels) in '
Jira (PUP-1334) Empty clientbucket files produce errors
Title: Message Title Daniel Dreier commented on PUP-1334 Re: Empty clientbucket files produce errors I'm currently seeing this issue on tahoe.delivery.puppetlabs.net, internally. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1334) Empty clientbucket files produce errors
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1334 Empty clientbucket files produce errors Change By: Daniel Dreier Comment: I'm currently seeing this issue on tahoe.delivery.puppetlabs.net, internally. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3182) puppet catalog download fails
Title: Message Title Daniel Dreier commented on PUP-3182 Re: puppet catalog download fails I have reproduced this issue with PE 3.8.2 and PE 2015.2.1 clients against a PE 2015.2.1 master. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2007) munging catalog fails with :undef tags
Title: Message Title Daniel Dreier commented on PDB-2007 Re: munging catalog fails with :undef tags Kurt Wall The reason it's only impacting us now is that we're working on migrating from PE 3.3.0 / PuppetDB 1.5.2 to 2015.2.1 / PuppetDB 3.1.1. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2007) munging catalog fails with :undef tags
Title: Message Title Daniel Dreier created an issue PuppetDB / PDB-2007 munging catalog fails with :undef tags Issue Type: Bug Assignee: Unassigned Created: 2015/09/29 7:10 PM Priority: Normal Reporter: Daniel Dreier In 2015.2, if you have an undef tag on a resource an error occurs during munging that causes the agent run to fail. I'm not sure whether that bit of code is owned by the puppetdb team, so this ticket may need to be moved. I'm also not sure whether this is expected behavior. We set a lot of variables to undef so if undef tags break things we may need to touch a lot of code. From the agent side, it looks like: root@pl-files02-dev:/etc/puppetlabs/puppet# p Info: Retrieving pluginfacts Info: Retrieving plugin
Jira (PDB-2001) Command API does not validate date format for fact submission
Title: Message Title Daniel Dreier created an issue PuppetDB / PDB-2001 Command API does not validate date format for fact submission Issue Type: Bug Assignee: Unassigned Created: 2015/09/23 4:39 PM Priority: Normal Reporter: Daniel Dreier I realize this is a bit of an edge case. I'm experimenting with scripts to submit facts to PuppetDB and I accidentally submitted facts with producer_timestamp in MM-DD- format rather than the expected -MM-DD format. I got a 200 and a UUID back, but the node facts aren't in puppetdb and in the logs, I get errors like the following: 2015-09-23 16:36:52,495 ERROR [p.p.mq-listener] message receive failed clojure.lang.ExceptionInfo: Input to maybe-activate-node! does not match schema: [nil (named (not (datetime? nil)) time)] at puppetlabs.puppetdb.scf.storage$eval16589$maybe_activate_node_BANG___16590.invoke(storage.clj:1195) ~[na:na]
Jira (PDB-2001) Command API does not validate date format for fact submission
Title: Message Title
Daniel Dreier updated an issue
PuppetDB / PDB-2001
Command API does not validate date format for fact submission
Change By:
Daniel Dreier
I realize this is a bit of an edge case. I'm experimenting with scripts to submit facts to PuppetDB and I accidentally submitted facts with producer_timestamp in MM-DD- format rather than the expected -MM-DD format. I got a 200 and a UUID back, but the node facts aren't in puppetdb and in the logs, I get errors like the following:{code}2015-09-23 16:36:52,495 ERROR [p.p.mq-listener] message receive failedclojure.lang.ExceptionInfo: Input to maybe-activate-node! does not match schema: [nil (named (not (datetime? nil)) time)]at puppetlabs.puppetdb.scf.storage$eval16589$maybe_activate_node_BANG___16590.invoke(storage.clj:1195) ~[na:na]at puppetlabs.puppetdb.command$eval30122$fn__30125$fn__30133.invoke(command.clj:224) ~[na:na]at puppetlabs.puppetdb.jdbc$with_transacted_connection_fn$fn__6270$fn__6271$fn__6272.invoke(jdbc.clj:234) ~[na:na]at clojure.java.jdbc.internal$transaction_STAR_.invoke(internal.clj:204) ~[na:na]at puppetlabs.puppetdb.jdbc$with_transacted_connection_fn$fn__6270$fn__6271.invoke(jdbc.clj:234) ~[na:na]at clojure.java.jdbc.internal$with_connection_STAR_.invoke(internal.clj:186) ~[na:na]at puppetlabs.puppetdb.jdbc$with_transacted_connection_fn$fn__6270.invoke(jdbc.clj:231) ~[na:na]at puppetlabs.puppetdb.jdbc$eval6248$retry_sql_STAR___6249$fn__6250$fn__6251.invoke(jdbc.clj:203) ~[na:na]at puppetlabs.puppetdb.jdbc$eval6248$retry_sql_STAR___6249$fn__6250.invoke(jdbc.clj:202) ~[na:na]at puppetlabs.puppetdb.jdbc$eval6248$retry_sql_STAR___6249.invoke(jdbc.clj:194) ~[na:na]at puppetlabs.puppetdb.jdbc$with_transacted_connection_fn.invoke(jdbc.clj:230) ~[na:na]at puppetlabs.puppetdb.command$eval30122$fn__30125.invoke(command.clj:223) ~[na:na]at clojure.lang.MultiFn.invoke(MultiFn.java:233) ~[puppetdb.jar:na]at puppetlabs.puppetdb.command$reify__30213$service_fnk__21198__auto___positional$reify__30222$fn__30224.invoke(command.clj:310) ~[na:na]at puppetlabs.puppetdb.mq_listener$reify__31024$service_fnk__21198__auto___positional$reify__31034.process_message(mq_listener.clj:398) ~[na:na]at puppetlabs.puppetdb.mq_listener$reify__31024$service_fnk__21198__auto___positional$reify__31034$process_msg__31036.invoke(mq_listener.clj:366) ~[na:na]at puppetlabs.puppetdb.mq_listener$wrap_with_discard$fn__30861$fn__30865.invoke(mq_listener.clj:219) ~[na:na]at puppetlabs.puppetdb.mq_listener.proxy$java.lang.Object$Callable$7da976d4.call(Unknown Source) ~[na:na]at com.yammer.metrics.core.Timer.time(Timer.java:91) ~[puppetdb.jar:na]at puppetlabs.puppetdb.mq_listener$wrap_with_discard$fn__30861.invoke(mq_listener.clj:218) ~[na:na]at puppetlabs.puppetdb.mq_listener$wrap_with_exception_handling$fn__30848$fn__30850.invoke(mq_listener.clj:172) ~[na:na]at puppetlabs.puppetdb.mq_listener.proxy$java.lang.Object$Callable$7da976d4.call(Unknown Source) ~[na:na]at com.yammer.metrics.core.Timer.time(Timer.java:91) ~[puppetdb.jar:na]at
Jira (PUP-4516) Agent does not stop with Ctrl-C
Title: Message Title Daniel Dreier commented on PUP-4516 Re: Agent does not stop with Ctrl-C I heard several complaints about this at the PDX Puppet user group meeting, with people generally assuming that this was an intentional change. Eric Sorenson are you the product owner responsible for the agent? Can you help get engineering time devoted to this? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5065) Puppet module tool should accept multiple modules to install
Title: Message Title Daniel Dreier created an issue Puppet / PUP-5065 Puppet module tool should accept multiple modules to install Issue Type: Improvement Assignee: Kylo Ginsberg Components: Client Created: 2015/08/22 7:27 PM Priority: Minor Reporter: Daniel Dreier The puppet module tool would be more convenient to use if it could install multiple modules at once, like yum or apt can. For example, I'd like to run: puppet module install jfryman-nginx ploperations-puppetlabs_apt ploperations-unicorn puppetlabs-inifile puppetlabs-puppetdb The behavior I'd expect would be essentially identical to what I'd get from:
Jira (PUP-5046) Puppet agent should not trap sig int
Title: Message Title Daniel Dreier commented on PUP-5046 Re: Puppet agent should not trap sig int thanks Kylo Ginsberg - it does indeed look like a dupe of PUP-4516. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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-5046) Puppet agent should not trap sig int
Title: Message Title Daniel Dreier created an issue Puppet / PUP-5046 Puppet agent should not trap sig int Issue Type: Bug Assignee: Kylo Ginsberg Components: Client Created: 2015/08/17 4:49 PM Priority: Normal Reporter: Daniel Dreier I recently upgraded from 3.3 to 3.8.1 and discovered that the puppet agent appears to trap CTRL-C now. The previous behavior was that a single ctrl-c would be caught and a second would immediately exit. The use case here is that I'll run puppet agent and then realize I forgot to specify an environment, --debug, or some other flag and then I don't have a good way to break out of the run. The workaround I'm using is to ctrl-z and then kill -9 the process but that seems unnecessarily harsh and awkward. I have not tested whether this also happens in the 4.x client. Add Comment
Jira (PUP-5046) Puppet agent should not trap sig int
Title: Message Title Daniel Dreier commented on PUP-5046 Re: Puppet agent should not trap sig int not sure if this qualifies as a bug, feature request, etc. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-424) Hiera github page links to redmine
Title: Message Title Daniel Dreier created an issue Hiera / HI-424 Hiera github page links to redmine Issue Type: Task Assignee: Unassigned Created: 2015/08/13 11:27 PM Priority: Normal Reporter: Daniel Dreier https://github.com/puppetlabs/hiera still links to http://projects.puppetlabs.com/projects/hiera/, which is on the long-deprecated redmine site. I'm not sure where it should link to or I would've just fixed it myself. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PDB-1292) puppetdb api docs should include concrete examples
Title: Message Title Daniel Dreier commented on PDB-1292 Re: puppetdb api docs should include concrete examples really glad to see this work through the system - thanks everybody. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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-4643) Add continue/next/break for iteration control
Title: Message Title Daniel Dreier created an issue Puppet / PUP-4643 Add continue/next/break for iteration control Issue Type: New Feature Assignee: Unassigned Created: 2015/05/21 5:55 PM Priority: Normal Reporter: Daniel Dreier It would be very convenient if we had the standard continue/next/break functions to control iterative functions like each. I imagine this has been discussed but wanted to put in my vote to add this feature. Eric Zounes I believe you were interested in this as well. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1526) Provide test packages to ops for sync logging feedback
Title: Message Title Daniel Dreier updated an issue PuppetDB / PDB-1526 Provide test packages to ops for sync logging feedback Change By: Daniel Dreier Basedonourchataboutgettingfeedbackfromopsaboutsynclogs,we'llneedpackagesandinstructionsforsettinguppuppetdbwithsyncandloggingtoplaywithandprovidefeedbackagainst. Thisisbasedonaconversationwith[~rob.browning]and[~russell.mull] Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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-1526) Provide test packages to ops for sync logging feedback
Title: Message Title Daniel Dreier assigned an issue to Unassigned PuppetDB / PDB-1526 Provide test packages to ops for sync logging feedback Change By: Daniel Dreier Assignee: DanielDreier Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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-1526) Provide test packages to ops for sync logging feedback
Title: Message Title Daniel Dreier created an issue PuppetDB / PDB-1526 Provide test packages to ops for sync logging feedback Issue Type: Task Assignee: Daniel Dreier Created: 2015/05/14 3:51 PM Priority: Normal Reporter: Daniel Dreier Based on our chat about getting feedback from ops about sync logs, we'll need packages and instructions for setting up puppetdb with sync and logging to play with and provide feedback against. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4368) Allow loading file_serving terminii from modules
Title: Message Title Daniel Dreier commented on PUP-4368 Re: Allow loading file_serving terminii from modules This would be very useful. This issue was linked from a discussion at https://github.com/puppetlabs/puppetlabs-aws/pull/128#issuecomment-93743358 and the [puppet-riak](https://github.com/basho-labs/puppet-riak) module would also benefit from a native way to download Basho's unpackaged patch updates. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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-4182) add a flag to get JSON output from puppet resource
Title: Message Title Daniel Dreier created an issue Puppet / PUP-4182 add a flag to get JSON output from puppet resource Issue Type: New Feature Assignee: Unassigned Created: 2015/03/11 9:00 AM Priority: Normal Reporter: Daniel Dreier As I discussed with Henrik Lindberg, I'd like an option to get JSON (and perhaps YAML) output from the puppet resource command. I can see two use cases: 1) For YAML, ability to go directly from existing puppet resources to YAML entries I can put into hiera to feed into create_resource 2) for JSON, as an extension point to use puppet in the context of shell scripts, python fabric scripts, etc. For example, using the puppetlabs-aws module, you could loop over the output of a puppet resource command listing all ec2_instances, use jq in bash (or python json parsing, etc) to select instances that lack appropriate tags, modify the JSON to add the appropriate tags, then feed that back into puppet apply to update the resources. Ideally, I'd like some ability to pipe JSON into a puppet resource to set parameters, as well, but that's less important because I can use puppet functions in a puppet apply. Add Comment
Jira (PDB-1129) puppetdb anonymize should use stronger hash function
Title: Message Title Daniel Dreier commented on PDB-1129 Re: puppetdb anonymize should use stronger hash function Thanks, I appreciate the clarification. I had just noticed that some of our password fields were consistently being transformed into the same strings on multiple nodes, based on looking at anonymized catalogs: nesmivxvny.updwtobauiqzmot.tey.json:sendgridpassword : VaoO2RU5sh10SmOSTNCn4Nz2BE7jJN, nfqvamgghr.kiscjhljfpykkrc.alr.json:sendgridpassword : VaoO2RU5sh10SmOSTNCn4Nz2BE7jJN, nsicingnnd.kcxtlxjdcaeaotw.crf.json:sendgridpassword : VaoO2RU5sh10SmOSTNCn4Nz2BE7jJN, nyviworens.sfqijlzbejkvaft.bwt.json:sendgridpassword : VaoO2RU5sh10SmOSTNCn4Nz2BE7jJN, nzcgyapaut.mdsqzgmgprbzdim.ile.json:sendgridpassword : VaoO2RU5sh10SmOSTNCn4Nz2BE7jJN, obshccyrld.yxjdmkjaezaopny.ruc.json:sendgridpassword : VaoO2RU5sh10SmOSTNCn4Nz2BE7jJN, ocdsdhkysd.tlidopfakhduadc.swl.json:sendgridpassword : VaoO2RU5sh10SmOSTNCn4Nz2BE7jJN, ocvsflhnop.sfimtslwvmsiuoq.xae.json:sendgridpassword : VaoO2RU5sh10SmOSTNCn4Nz2BE7jJN,
Jira (PDB-1129) puppetdb anonymize should use stronger hash function
Title: Message Title Daniel Dreier created an issue PuppetDB / PDB-1129 puppetdb anonymize should use stronger hash function Issue Type: Improvement Assignee: Unassigned Created: 2015/01/21 9:55 PM Labels: security Priority: Normal Reporter: Daniel Dreier Based on my reading of https://github.com/puppetlabs/puppetdb/blob/master/src/puppetlabs/puppetdb/cli/anonymize.clj, it looks to me like the hashing function used to anonymize data is sha1. Given that sha1 is gradually being phased out in other contexts (google, mozilla), and we do expect people to hash secrets with it, it seems like we should adopt a more secure hashing algorithm, like sha256 or bcrypt. That said, I'm not a clojure developer, so I may have misread the code. Add Comment
Jira (PUP-3043) 100% CPU usage
Title: Message Title
Daniel Dreier commented on an issue
Re: 100% CPU usage
This is still the case in 3.6.2, despite being originally reported four years ago, as demonstrated with the following test case:
file { '/tmp/foo':
owner = root,
group = root,
recurse = true,
ensure = directory,
checksum = undef
}
The first time you run it, it'll run very quickly. Run
for filename in {1..5} ; do touch /tmp/foo/$filename ; done
Then re-run the puppet test case. On a fast i7 CPU with an SSD, it was still running after 15 minutes when I killed it.
Add Comment
Puppet / PUP-3043
100% CPU usage
Hi, I've been experimenting with Puppet for a few days now, and overall I'm pretty impressed on how easy Puppet makes it to manage configurations. However, one thing has been ruining my enthusiasm thoroughly, and that is the massive CPU consumption of Puppet. At first I used puppet to source in and manage a few hundred megabytes of data, so I presu...
This message was sent by Atlassian JIRA
Jira (PUP-3043) 100% CPU usage
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-3043 100% CPU usage Change By: Daniel Dreier Affects Version/s: 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3043) 100% CPU usage
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-3043
100% CPU usage
Change By:
Daniel Dreier
Hi,I'vebeenexperimentingwithPuppetforafewdaysnow,andoverallI'mprettyimpressedonhoweasyPuppetmakesittomanageconfigurations.However,onethinghasbeen runing ruining myenthusiasmthoroughly,andthatisthemassiveCPUconsumptionofPuppet.AtfirstIusedpuppettosourceinandmanageafewhundredmegabytesofdata,soIpresumedPuppetjustwasn'tmadetoprovidesuchlargeamountsofdata.SoIsetupmyownaptrepositoryandcreatedsomecustompackagestoasanalternativewaytotransferdata.Ialsolearnedaboutthechecksumfileproperty,andthatthedefaultvalueofmd5cancausealotofCPUconsumption.SoIturnedchecksummingof(checksum=undef).Butnowpuppetisstillhappilyeatingaway100%CPUfortensofminutesatatime,withnoapparentthingshappening.(puppetd-tv--trace--debug,butnothingappearingintheconsolewhilePuppetiscookingtheCPU.)Ibelievethefollowingresourceistoblame: {code} file{/some/data/dir:owner=$username,group=$username,recurse=true,ensure=directory,checksum=undef} {code} Ijustwantthisresourcetomakesurethatallfilesinthedirectoryareownedbyuserandgroup$username./some/data/dircontains300Min6000+files.Thisresourceexecutesswiftly,butafterthelastfilehasbeenchown'd,thepuppethogstheCPUwith100%usage,lastingforlooong.(Looongbeing:30+minutes,andmehittingCTRL-Cbeingimpatientandfrustratedwithseeingnothinghappen.)Sometopoutput: {code} 9570root250228m151m3664R9929.714:31.27puppetd {code} Idon'treallyunderstandwhyI'mgettingthis.IsPuppetunabletohandlethisrequest?Whatishappening?I'mabitdisappointedtorunintosuchanissuewhilejustdoingsometrivialtests...IfIcan'tsolvethisIcan'tseehowPuppetcanbeusableforme(andtherearen'tthatmanyalternatives..).Idon'tknowRuby,andI'mnotreallyfanofthedebug-before-useapproach...Someinformationaboutmysetup:puppetdenpuppetmasterdare0.25.4BothrunningonXenDom-Uinstances {code} uname-a:Linuxhostname2.6.18.8#2SMPWedMay2715:54:07CEST2009x86_64GNU/LinuxUbuntuintrepid8.10dpkg--list|grepruby:iiruby4.2Aninterpreterofobject-orientedscriptingiiruby1.81.8.7.72-1Interpreterofobject-orientedscriptinglan {code} Notreallyanyloggingtoshow,sincenothingislogged...I'mawarethisisn'tmuchtogoon,butI'lltrytoprovideyouwithanythingyoumayneedifyoujustaskforit.
Add Comment
Jira (PUP-2930) puppet module list --render-as yaml returns excessive information
Title: Message Title
Daniel Dreier created an issue
Puppet / PUP-2930
puppet module list --render-as yaml returns excessive information
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Unassigned
Created:
11/Jul/14 10:06 PM
Environment:
Debian 7 x86_64
Priority:
Minor
Reporter:
Daniel Dreier
I'm not 100% sure whether this should be a bug or improvement request, but it appears that rendering the module list as yaml displays vastly more information than either the default or the json rendering.
Compare:
root@debian7:/# puppet module list
/etc/puppet/modules
└── puppetlabs-stdlib (v4.2.2)
root@debian7:/# puppet module list --render-as json
{environment:production,modules_by_path:{/etc/puppet/modules:[Module stdlib(/etc/puppet/modules/stdlib)]}}
root@debian7:/# puppet module list --render-as yaml
---
!ruby/sym environment: production
!ruby/sym modules_by_path:
/etc/puppet/modules:
- !ruby/object:Puppet::Module
name: stdlib
path: /etc/puppet/modules/stdlib
environment: production
metadata_file: /etc/puppet/modules/stdlib/metadata.json
metadata:
name: puppetlabs-stdlib
version: 4.2.2
author: puppetlabs
summary: Puppet Module Standard Library
Jira (PUP-283) Improve agent error reporting
Title: Message Title Daniel Dreier commented on an issue Re: Improve agent error reporting I made a trivial pull request to improve documentation on this command, but I think the issue can probably be closed at this point. Please re-open if you feel like further work is needed. Add Comment Puppet / PUP-283 Improve agent error reporting When a Puppet run fails for whatever reason (catalog compilation failure/timeout, etc..), it would be nice to have this cause of failure be available as a field in the submitted report. If this was available then one would be able to introspect on it to see the reason for a failed Puppet run, without having to parse the logs field and perform some regex ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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-2087) Puppet does not implicitly convert string to integer
Title: Message Title
Daniel Dreier commented on an issue
Re: Puppet does not implicitly convert string to integer
This issue is from 2012 and appears not to apply to current versions of puppet.
There are two separate parts to this issue. First, there's the question of whether quoted strings in variables are converted to numbers for arithmetic operators. Here are the tests I can on the latest puppet master (3.6.2):
$quoted_number = '5'
$multiplication_result_quoted = $quoted_number * 2
notice(${quoted_number} * 2 = ${multiplication_result_quoted})
$unquoted_number = 5
$multiplication_result_unquoted = $unquoted_number * 2
notice(${quoted_number} * 2 = ${multiplication_result_unquoted})
$division_result_quoted = $quoted_number / 2
notice(${quoted_number} / 2 = ${division_result_quoted})
$division_result_unquoted = $unquoted_number / 2
notice(${quoted_number} / 2 = ${division_result_unquoted})
$addition_result_quoted = $quoted_number + 2
notice(${quoted_number} + 2 = ${addition_result_quoted})
$addition_result_unquoted = $unquoted_number + 2
notice(${quoted_number} + 2 = ${addition_result_unquoted})
$subtraction_result_quoted = $quoted_number - 2
notice(${quoted_number} - 2 = ${addition_result_quoted})
$subtraction_result_unquoted = $unquoted_number - 2
notice(${quoted_number} - 2 = ${addition_result_unquoted})
$modulo_result_quoted = $quoted_number % 2
notice(${quoted_number} % 2 = ${modulo_result_quoted})
$modulo_result_unquoted = $unquoted_number % 2
notice(${quoted_number} % 2 = ${modulo_result_unquoted})
The result I got was the following, as expected:
[vagrant@poss-head-centos vagrant]$ puppet apply test.pp
Notice: Scope(Class[main]): 5 * 2 = 10
Notice: Scope(Class[main]): 5 * 2 = 10
Notice: Scope(Class[main]): 5 / 2 = 2
Notice: Scope(Class[main]): 5 / 2 = 2
Notice: Scope(Class[main]): 5 + 2 = 7
Notice: Scope(Class[main]): 5 + 2 = 7
Notice: Scope(Class[main]): 5 - 2 = 7
Notice: Scope(Class[main]): 5 - 2 = 7
Notice: Scope(Class[main]): 5 % 2 = 1
Notice: Scope(Class[main]): 5 % 2 = 1
Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.04 seconds
Notice: Finished catalog run in 0.11 seconds
However, the linked serverfault post contains a somewhat different test case:
$ip_array = split($ipaddress, '.')
$odd_ip = $ip_array[3] % 2
if $odd_ip == 1 {
notice(is odd)
}
That code does indeed cause an error, but the cause of the error is that the . in the split is not escaped, so puppet is actually correct in asserting that $odd_ip is not a number. It work as expected with the period escaped properly:
$ip_array = split($ipaddress, '[.]')
$odd_ip = $ip_array[3] % 2
if $odd_ip == 1 {
notice(is odd)
}
Jira (PUP-2786) `puppet cert list ca` returns an error on a working puppet installation
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-2786 `puppet cert list ca` returns an error on a working puppet installation Change By: Daniel Dreier Affects Version/s: 3.6.2 Affects Version/s: 2.7.23 Affects Version/s: 3.4.3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-2341 puppet parser validate - no output when everything's ok Change By: Daniel Dreier 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-2341) puppet parser validate - no output when everything's ok
Title: Message Title
Daniel Dreier commented on an issue
Re: puppet parser validate - no output when everything's ok
Recategorized from bug to improvement because no output on success is the expected behavior of most *nix tools. If this is implemented, I think it would be best to add to a --verbose flag, or at least a --quiet flag to suppress it, because it would create a lot of unnecessary noise as default behavior.
For example, my rake tests involve something along the lines of find -name '*.pp' -exec puppet validate {} \; – meaning that an OK message on output would be repeated dozens or hundreds of times on a larger project.
Add Comment
Puppet / PUP-2341
puppet parser validate - no output when everything's ok
Running `puppet parser validate init.pp` returns nothing on the command line when there are no errors. Please consider adding a message like OK or No Parse Error that indicates to the user that the file(s) passed parser validation. This comes up for discussion at almost every fundamentals class I teach, where someone asks So I see no output, is t...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2341) puppet parser validate - no output when everything's ok
Title: Message Title Daniel Dreier commented on an issue Re: puppet parser validate - no output when everything's ok On reflection, it looks like my use case would readily be satisfied by simply passing validate a large list of files. I'd still like a --quiet option for use in scripts, and purely from an aesthetic perspective I like the traditional no output on success, but I can definitely see why it has the potential to be confusing. Add Comment Puppet / PUP-2341 puppet parser validate - no output when everything's ok Running `puppet parser validate init.pp` returns nothing on the command line when there are no errors. Please consider adding a message like OK or No Parse Error that indicates to the user that the file(s) passed parser validation. This comes up for discussion at almost every fundamentals class I teach, where someone asks So I see no output, is 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
Jira (PUP-1394) NFS on Fedora 20 requires both path and device
Title: Message Title
Daniel Dreier commented on an issue
Re: NFS on Fedora 20 requires both path and device
I just tried to reproduce this on Fedora 20 x86_64 with puppet 3.6.2 on ruby 2.0.0p353 . I'm using the following manifest:
mount { '/mnt/foo':
ensure = 'mounted',
device = 'localhost:/export',
fstype = 'nfs',
options = 'rw,intr,soft,context=system_u:object_r:var_log_t:s0',
atboot = true,
}
I created a /etc/export containing:
/export *(rw,sync,no_root_squash,no_all_squash)
I created /exports/foo and put a test file in it, then started NFS
systemctl start rpcbind.service
systemctl start nfs-server.service
systemctl start nfs-lock.service
systemctl start nfs-idmap.service
systemctl restart nfs-server.service
When I ran the manifest above, I got the following /etc/fstab entry created:
localhost:/export /mnt/foo nfs rw,intr,soft,context=system_u:object_r:var_log_t:s0 0 0
It mounted to /mnt/foo as expected, both using puppet and by hand. SELinux is set to enforcing.
Can you share more details about how you're able to reproduce the issue you're running into? Do the settings I described cause the issue to happen for you?
Add Comment
Puppet / PUP-1394
Jira (PUP-1428) No such file or directory error with ssh_authorized_keys
Title: Message Title
Daniel Dreier commented on an issue
Re: No such file or directory error with ssh_authorized_keys
This was originally reported against 2.7.14. About two years ago, the original reporter figured out what the matter was: I was mounting my tmp folder to another volume and that folder was not writable. I did not know that puppet writes to /tmp. Should we display a warning if tmp cannot be written to? The error message, in its current form, is not easy to debug.
As of puppet 3.6.2, error messages for a read-only /tmp are more descriptive. For the following test manifest, and given a loopback filesystem mounted read-only to /tmp, we get the output below:
ssh_authorized_key { 'daniel':
key = 'testkey',
type = ssh-rsa,
user = 'daniel',
require = User['daniel'],
}
user { 'daniel':
ensure = 'present',
managehome = true,
}
[root@poss-head-centos ~]# puppet apply test.pp
Warning: Future reserved word: type. Either choose a different name or quote the string, if possible. In /root/test.pp:3. See http://links.puppetlabs.com/reserved-words-4
(at /puppetlabs/puppet/lib/puppet/parser/lexer.rb:615:in `warn_if_reserved')
Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.34 seconds
Error: Could not set 'present' on ensure: Read-only file system - /tmp/puppet20140619-9394-rzb8kx.lock at 11:/root/test.pp
Error: Could not set 'present' on ensure: Read-only file system - /tmp/puppet20140619-9394-rzb8kx.lock at 11:/root/test.pp
Wrapped exception:
Read-only file system - /tmp/puppet20140619-9394-rzb8kx.lock
Error: /Stage[main]/Main/User[daniel]/ensure: change from absent to present failed: Could not set 'present' on ensure: Read-only file system - /tmp/puppet20140619-9394-rzb8kx.lock at 11:/root/test.pp
Notice: /Stage[main]/Main/Ssh_authorized_key[daniel]: Dependency User[daniel] has failures: true
Warning: /Stage[main]/Main/Ssh_authorized_key[daniel]: Skipping because of failed dependencies
Notice: Finished catalog run in 0.09 seconds
Given the fact that the original issue was essentially misconfiguration exacerbated by a confusing error message, and the error message is much more descriptive now, I think this issue can safely be closed.
Add Comment
Jira (PUP-2801) 'puppetca' needs feature to remove (/revoke) a pending certificate signing request
Title: Message Title Daniel Dreier commented on an issue Re: 'puppetca' needs feature to remove (/revoke) a pending certificate signing request I think you're looking for the puppet ca destroy machinename command: [root@poss-head-centos ~]# puppet ca list centos-65-latest.boxnet (SHA256) 60:C0:F3:D6:A9:76:B9:B5:A6:16:68:A5:BF:92:97:20:3D:BC:AC:67:E8:5E:19:50:CE:08:4A:F7:26:38:11:22 [root@poss-head-centos ~]# puppet ca destroy centos-65-latest.boxnet Notice: Removing file Puppet::SSL::CertificateRequest centos-65-latest.boxnet at '/etc/puppet/ssl/ca/requests/centos-65-latest.boxnet.pem' Deleted for centos-65-latest.boxnet: Puppet::SSL::CertificateRequest [root@poss-head-centos ~]# puppet ca list [root@poss-head-centos ~]# The reason that revoking an unsigned CSR can't (and won't) work is because the revocation list is based on the serial number of the signed certificate. The serial number is issued by the CA as part of signing the certificate. You'd have to sign the CSR first and then revoke it in order to get the expected behavior. Perhaps better documentation is needed for this. puppet help ca describes the destroy command as undocumented action as of the latest master. Do you think that using the puppet ca destroy command works for your use case? Add Comment Puppet / PUP-2801 'puppetca' needs feature to remove (/revoke) a pending certificate signing request It is not possible to remove a pending certificate signing request with 'puppetca --revoke $fqdn': pre [root@X puppet]# puppetca --list rhel32bit.x.local [root@X puppet]# puppetca --revoke rhel32bit.x.local rhel32bit.x.local notice: Revoked certificate with serial
Jira (PUP-2754) Exit status is 0, even in the presence of errors, without --detailed-exitcodes
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-2754
Exit status is 0, even in the presence of errors, without --detailed-exitcodes
Change By:
Daniel Dreier
Whenanerrorisencounteredwhilerunningeither`puppetapply`or`puppetagent`,theprogramexitswithstatus0.If`--detailed-exitcodes`isusedwith`puppetagent`,thestatusisnonzeroasexpected.Iwouldexpectthatnon-detailedexitcodeswouldstillinclude1forthecaseofafailuretoapplythecatalog.Youcanrecreatethiswiththefollowingmanifest: pre {code} exec{'false':command='/bin/false',} /pre {code} Examplerun: pre {code} marmida@monolith:~$puppetapplyfail_manifest.pywarning:Couldnotretrievefactfqdnerr:/Stage[main]//Exec[false]/returns:changefromnotrunto0failed:/bin/falsereturned1insteadofoneof[0]at/home/marmida/fail_manifest.py:3notice:Finishedcatalogrunin0.14secondsmarmida@monolith:~$echo$?0marmida@monolith:~$puppetapplyfail_manifest.py--detailed-exitcodeswarning:Couldnotretrievefactfqdnerr:/Stage[main]//Exec[false]/returns:changefromnotrunto0failed:/bin/falsereturned1insteadofoneof[0]at/home/marmida/fail_manifest.py:3notice:Finishedcatalogrunin0.13secondsmarmida@monolith:~$echo$?4 /pre {code} Thesameproblemsoccurin`puppetagent`.Icouldn'tfindanotherissuespecifictotheexitstatus,butIdidnoticeitmentionedoncehere:http://projects.puppetlabs.com/issues/14458#note-6
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
Jira (PUP-2754) Exit status is 0, even in the presence of errors, without --detailed-exitcodes
Title: Message Title Daniel Dreier commented on an issue Re: Exit status is 0, even in the presence of errors, without --detailed-exitcodes I've reproduced this and got exactly the same results with the example code on the current master branch. It's so similar it's not worth posting my output. Summarizing prior discussion: About a year ago in issue 19033, Michael Armida reported the exact same issue on puppet 2.7.18, and explained that he uses fabric to run puppet. Jeff Mccune ultimately concluded that I’m convinced that Fabric’s assumption about the exit code of puppet agent and puppet apply is a sensible one. We accept this as a bug, Puppet should definitely return a non-zero exit status if a resource in the catalog fails to be applied to the system. Redmine issue 17017 was an umbrella bug linking to a large number of error code correctness and error handling issues. Issue 14458 / PUP-735, where a puppet apply that failed on account of a dependency cycle resulted in a zero exit code, included the ultimately-rejected PR 1854 in which Kylo Ginsberg suggested that the issue would be addressed in puppet 3.5. Add Comment Puppet / PUP-2754 Exit status is 0, even in the presence of errors, without --detailed-exitcodes When an error is encountered while running either `puppet apply` or `puppet agent`, the program exits with status 0. If `--detailed-exitcodes` is used with `puppet agent`, the status is nonzero as expected. I would expect that non-detailed exit codes would still include 1 for the case of a failure to apply the catalog. You can recreate this with th...
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title
Daniel Dreier commented on an issue
Re: Puppet silent about inability to acquire pidlock
Scratch that - my approach to fixing it won't work. Marking the issue open again.
Add Comment
Puppet / PUP-911
Puppet silent about inability to acquire pidlock
The {{--verbose}} flag does tell the user that something has happened, but without it there isn't any indication. I would expect the error to always show up (even without verbose) and a non-zero exit status. {noformat} root@debian-607-x64-vf503-nocm:~# puppet agent --verbose Error: Could not run: Could not create PID file: /var/run/puppet/agent.pid ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-2740) Puppet apply core dump on RedHat 6.5
Title: Message Title Daniel Dreier commented on an issue Re: Puppet apply core dump on RedHat 6.5 As I showed earlier, I was able to run puppet in a very minimal way with the exact same redhat version, ruby version, and puppet version that you ran it on. I appreciate your doing further background research. I read through foreman issue 4244 and I don't feel that this issue currently has enough information to clearly link the two. If you apply the hacky fix that was proposed for 4244, does it (temporarily) solve this issue? That fix was: Edit /usr/bin/puppet and add this line to the top: GC.disable = true Can you come up with a more limited puppet manifest that crashes puppet, so that you can post the test case here or on github, to help me reproduce it? I don't think the issue is likely to get resolved without a reproducible test case. Add Comment Puppet / PUP-2740 Puppet apply core dump on RedHat 6.5 puppet apply --modulepath=/etc/puppet/modules -e include dta::puppetmaster /usr/lib/ruby/site_ruby/1.8/puppet/parser/scope.rb:414: [BUG] Segmentation fault ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] Aborted (core dumped) This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title Daniel Dreier assigned an issue to Daniel Dreier Puppet / PUP-911 Puppet silent about inability to acquire pidlock Change By: Daniel Dreier Assignee: DanielDreier 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-911) Puppet silent about inability to acquire pidlock
Title: Message Title
Daniel Dreier commented on an issue
Re: Puppet silent about inability to acquire pidlock
It looks like the cause of this is that in daemon.rb, create_pidfile gets called after the daemon forks. As a result, the exit code you'll get is always 0 because the exception happened in the forked process and not the one that you're getting a return code from.
I'm working on a pull request; it looks like simply re-ordering the two works but I need to figure out how to test for this issue.
Add Comment
Puppet / PUP-911
Puppet silent about inability to acquire pidlock
The {{--verbose}} flag does tell the user that something has happened, but without it there isn't any indication. I would expect the error to always show up (even without verbose) and a non-zero exit status. {noformat} root@debian-607-x64-vf503-nocm:~# puppet agent --verbose Error: Could not run: Could not create PID file: /var/run/puppet/agent.pid ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title
Daniel Dreier commented on an issue
Re: Puppet silent about inability to acquire pidlock
I've submitted pull request 2774 to try and fix this. I wasn't able to find other tickets on similar topics but I'd be very curious if somebody can dig them up. In the meantime, the fix is to move one line up so we really might as well.
Add Comment
Puppet / PUP-911
Puppet silent about inability to acquire pidlock
The {{--verbose}} flag does tell the user that something has happened, but without it there isn't any indication. I would expect the error to always show up (even without verbose) and a non-zero exit status. {noformat} root@debian-607-x64-vf503-nocm:~# puppet agent --verbose Error: Could not run: Could not create PID file: /var/run/puppet/agent.pid ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-911 Puppet silent about inability to acquire pidlock Change By: Daniel Dreier Component/s: Client 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-911) Puppet silent about inability to acquire pidlock
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-911 Puppet silent about inability to acquire pidlock Change By: Daniel Dreier Priority: Normal Minor Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1090) client should not sleep for $splay_time when triggered by puppetrun
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1090 client should not sleep for $splay_time when triggered by puppetrun Change By: Daniel Dreier Labels: kick redmine 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-1090) client should not sleep for $splay_time when triggered by puppetrun
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1090 client should not sleep for $splay_time when triggered by puppetrun Change By: Daniel Dreier Assignee: CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1226) puppet breaking setuid bit on group change
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1226 puppet breaking setuid bit on group change Change By: Daniel Dreier Affects Version/s: 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1226) puppet breaking setuid bit on group change
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1226 puppet breaking setuid bit on group change Change By: Daniel Dreier Labels: file redmine 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-1226) puppet breaking setuid bit on group change
Title: Message Title
Daniel Dreier commented on an issue
Re: puppet breaking setuid bit on group change
I've reproduced this on Centos 6.5 with the current master puppet branch. When puppet changes the group, permissions are reset to 0555. If you run puppet a second time, permissions are changed to 6555 as expected.
Add Comment
Puppet / PUP-1226
puppet breaking setuid bit on group change
We have a puppet module that's trying to manage owner, group and setuid bit on /bin/nice: file { /bin/nice: owner = root, group = root, mode = 6555, } If the mode is correct, but group is wrong, puppet will fix the group and lose the setuid bit:# chgrp bin ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-2740) Puppet apply core dump on RedHat 6.5
Title: Message Title Daniel Dreier commented on an issue Re: Puppet apply core dump on RedHat 6.5 I can't reproduce this, most likely because I don't have your dta module. I started a RHEL 6.5 EC2 instance on a c3.large with ruby 1.8.7 and puppet 3.6.1: [root@ip-172-31-19-25 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.5 (Santiago) [root@ip-172-31-19-25 ~]# ruby --version ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] [root@ip-172-31-19-25 ~]# puppet --version 3.6.1 [root@ip-172-31-19-25 ~]# puppet apply --modulepath=/etc/puppet/modules -e include dta::puppetmaster Error: Could not find class dta::puppetmaster for ip-172-31-19-25.us-west-2.compute.internal on node ip-172-31-19-25.us-west-2.compute.internal Error: Could not find class dta::puppetmaster for ip-172-31-19-25.us-west-2.compute.internal on node ip-172-31-19-25.us-west-2.compute.internal [root@ip-172-31-19-25 ~]# Can you make that module available? I don't think anybody will be able to help investigate the issue without it, because there's no way to know what's actually trying to run that's causing a segfault. Add Comment Puppet / PUP-2740 Puppet apply core dump on RedHat 6.5 puppet apply --modulepath=/etc/puppet/modules -e include dta::puppetmaster /usr/lib/ruby/site_ruby/1.8/puppet/parser/scope.rb:414: [BUG] Segmentation fault ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] Aborted (core dumped)
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title
Daniel Dreier commented on an issue
Re: Puppet silent about inability to acquire pidlock
I've confirmed this behavior on puppet 3.6.2 on Centos 6.5.
[root@centos-65-latest ~]# service puppet stop
Stopping puppet agent: [ OK ]
[root@centos-65-latest ~]# service puppet start
Starting puppet agent: [ OK ]
[root@centos-65-latest ~]# puppet agent --verbose
Warning: Setting modulepath is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations
(at /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:1095:in `issue_deprecations')
Error: Could not run: Could not create PID file: /var/run/puppet/agent.pid
[root@centos-65-latest ~]# echo $?
0
[root@centos-65-latest ~]# puppet --version
3.6.2
Add Comment
Puppet / PUP-911
Puppet silent about inability to acquire pidlock
The {{--verbose}} flag does tell the user that something has happened, but without it there isn't any indication. I would expect the error to always show up (even without verbose) and a non-zero exit status. {noformat} root@debian-607-x64-vf503-nocm:~# puppet agent --verbose Error: Could not run: Could not create PID file: /var/run/puppet/agent.pid ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-911) Puppet silent about inability to acquire pidlock
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-911 Puppet silent about inability to acquire pidlock Change By: Daniel Dreier Affects Version/s: 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-684) Namevar over 1024 characters is not caught and results in invalid yaml with accompanying errors
Title: Message Title
Daniel Dreier commented on an issue
Re: Namevar over 1024 characters is not caught and results in invalid yaml with accompanying errors
I've been able to reproduce what looks like the same problem on master:
[root@poss-head-centos ~]# puppet --version 3.6.1 [root@poss-head-centos ~]# rm /var/lib/puppet/state/state.yaml rm: remove regular file `/var/lib/puppet/state/state.yaml'? y [root@poss-head-centos ~]# cat test_good.pp ssh_authorized_key { '': ensure = present, user = 'root', key = 'foo', }
[root@poss-head-centos ~]# puppet apply test_good.pp Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.09 seconds Notice: Finished catalog run in 0.10 seconds [root@poss-head-centos ~]# puppet apply test_good.pp Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.08 seconds Notice: Finished catalog run in 0.21 seconds [root@poss-head-centos ~]# puppet apply test_good^Cp [root@poss-head-centos ~]# cat test_bad.pp ssh_authorized_key { '': ensure = present, user = 'root', key = 'foo', }
[root@poss-head-centos ~]# puppet apply test_bad.pp Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.09 seconds Notice: Finished catalog run in 0.11 seconds [root@poss-head-centos ~]# puppet apply test_bad.pp Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.09 seconds Error: Checksumfile /var/lib/puppet/state/state.yaml is corrupt ((/var/lib/puppet/state/state.yaml): could not find expected ':' while scanning a simple key at line 63 column 3); replacing Notice: Finished catalog run in 0.10 seconds
Jira (PUP-684) Namevar over 1024 characters is not caught and results in invalid yaml with accompanying errors
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-684 Namevar over 1024 characters is not caught and results in invalid yaml with accompanying errors Change By: Daniel Dreier Affects Version/s: 3.6.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-1295) Yum provider purge target runs irrespective of package installation status
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1295 Yum provider purge target runs irrespective of package installation status Change By: Daniel Dreier Fix Version/s: 3.6.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-1295) Yum provider purge target runs irrespective of package installation status
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1295 Yum provider purge target runs irrespective of package installation status Change By: Daniel Dreier Fix Version/s: 3.6.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-1295) Yum provider purge target runs irrespective of package installation status
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1295 Yum provider purge target runs irrespective of package installation status Change By: Daniel Dreier Affects Version/s: 3.6.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-1295) Yum provider purge target runs irrespective of package installation status
Title: Message Title
Daniel Dreier commented on an issue
Re: Yum provider purge target runs irrespective of package installation status
I've confirmed this again on master / 3.6.1 on CentOS 6.5. yum remove is run each time. The yum remove should only run if the package is actually installed.
Add Comment
Puppet / PUP-1295
Yum provider purge target runs irrespective of package installation status
It seems the yum provider will try to purge an absent package: pre [root@test ~]# cat test.pp package { logwatch: ensure = purged; } [root@test ~]# /bin/rpm -q logwatch --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}' package logwatch is not installed [root@test ~]# puppet -d -v test.pp debug: 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
Jira (PUP-1206) Augeas lenses in modules are not loaded when using puppet apply
Title: Message Title Daniel Dreier commented on an issue Re: Augeas lenses in modules are not loaded when using puppet apply According to Charlie's comment in the redmine ticket, this is expected behavior but the documentation needs to be updated to make it more clear why. Add Comment Puppet / PUP-1206 Augeas lenses in modules are not loaded when using puppet apply When you have custom lenses in your modules lib/augeas/lenses, these are not loaded by augeas when doing a puppet apply run. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send 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-1206) Augeas lenses in modules are not loaded when using puppet apply
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1206 Augeas lenses in modules are not loaded when using puppet apply Change By: Daniel Dreier Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1271) puppet ca list --all fails with Error: The certificate retrieved from the master does not match the agent's private key.
Title: Message Title Daniel Dreier commented on an issue Re: puppet ca list --all fails with Error: The certificate retrieved from the master does not match the agent's private key. Eric Sorenson and Charlie Sharpsteen reproduced this issue 10 months ago on then-current puppet versions. Jason Barnett appears to have reproduced the issue on 2.7.20, though the error is somewhat different. I was able to reproduce this issue on 3.4.2 on CentOS 6.4 using the same steps as Charlie followed. Using two VMs from the Puppet labs centos 6 nocm vagrantbox, on the puppetmaster: [root@puppetmaster ~]# puppet ca list --all + puppetmaster.boxnet (SHA256) 28:7B:8B:FB:52:E3:13:DE:A1:BE:55:BE:9D:76:77:F3:3C:FA:53:A7:4B:50:BC:D9:C0:8D:50:A8:39:F1:E5:F8 On the agent: [root@puppetmaster ~]# puppet ca list --all + puppetmaster.boxnet (SHA256) 28:7B:8B:FB:52:E3:13:DE:A1:BE:55:BE:9D:76:77:F3:3C:FA:53:A7:4B:50:BC:D9:C0:8D:50:A8:39:F1:E5:F8 [root@puppetmaster ~]# # requested cert from client [root@puppetmaster ~]# puppet ca list --all agent.boxnet (SHA256) 11:26:02:E5:B1:E6:70:D5:24:C0:1A:8E:0D:06:30:A2:87:6B:58:5B:C0:B8:76:8A:83:4F:FF:5E:36:5F:FE:EF + puppetmaster.boxnet (SHA256) 28:7B:8B:FB:52:E3:13:DE:A1:BE:55:BE:9D:76:77:F3:3C:FA:53:A7:4B:50:BC:D9:C0:8D:50:A8:39:F1:E5:F8 [root@puppetmaster ~]# puppet cert agent.boxnet Error: Invalid method agent.boxnet to apply [root@puppetmaster ~]# puppet cert sign agent.boxnet Notice: Signed certificate request for agent.boxnet Notice: Removing file Puppet::SSL::CertificateRequest agent.boxnet at '/var/lib/puppet/ssl/ca/requests/agent.boxnet.pem' [root@puppetmaster ~]# puppet ca list --all Error: The certificate retrieved from the master does not match the agent's private key. Certificate fingerprint: 17:FC:E2:89:9A:71:E2:99:07:EE:A3:3D:CE:79:5A:1D:90:CA:14:17:E7:55:F0:61:B8:F7:94:B0:5F:F6:5F:E1 To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certficate. On the master: puppet cert clean puppetmaster.boxnet On the agent: rm -f /var/lib/puppet/ssl/certs/puppetmaster.boxnet.pem puppet agent -t Error: Try 'puppet help ca list' for usage Back on the puppetmaster: [root@puppetmaster ~]# puppet ca list --all agent.boxnet (SHA256) 11:26:02:E5:B1:E6:70:D5:24:C0:1A:8E:0D:06:30:A2:87:6B:58:5B:C0:B8:76:8A:83:4F:FF:5E:36:5F:FE:EF + puppetmaster.boxnet (SHA256) 28:7B:8B:FB:52:E3:13:DE:A1:BE:55:BE:9D:76:77:F3:3C:FA:53:A7:4B:50:BC:D9:C0:8D:50:A8:39:F1:E5:F8 [root@puppetmaster ~]# puppet cert sign agent.boxnet Notice: Signed certificate request for agent.boxnet Notice: Removing file Puppet::SSL::CertificateRequest agent.boxnet at '/var/lib/puppet/ssl/ca/requests/agent.boxnet.pem' [root@puppetmaster ~]# puppet ca list --all Error: The certificate retrieved from the master does not match the agent's private key. Certificate fingerprint: 17:FC:E2:89:9A:71:E2:99:07:EE:A3:3D:CE:79:5A:1D:90:CA:14:17:E7:55:F0:61:B8:F7:94:B0:5F:F6:5F:E1 To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certficate. On the master: puppet
Jira (PUP-1271) puppet ca list --all fails with Error: The certificate retrieved from the master does not match the agent's private key.
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1271 puppet ca list --all fails with Error: The certificate retrieved from the master does not match the agent's private key. Change By: Daniel Dreier Affects Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1267) puppet help only show error message
Title: Message Title Daniel Dreier commented on an issue Re: puppet help only show error message This issue was originally reported against an unknown version of debian. I've tried to reproduce this on Debian 7 and Centos 6.4 using puppet 3.3.2 and 3.4.2, and on Debian 7 using puppet 3.3.1 using the exact same package versions as the original issue report. I ran the following in each environment: puppet --version puppet help puppet help apply puppet man apply On Debian 7, I set up with: apt-get install puppet=3.3.1-1puppetlabs1 puppet-common=3.3.1-1puppetlabs1 facter=1.7.3-1puppetlabs1 hiera=1.2.1-1puppetlabs1 ruby-rgen=0.6.5-1puppetlabs1 [snip] dpkg -l | grep puppet root@debian-70rc1-x64-vbox4210-nocm:/vagrant/provision# dpkg -l | grep puppet ii facter 1.7.3-1puppetlabs1amd64Ruby module for collecting simple facts about a host operating system ii hiera 1.2.1-1puppetlabs1all A simple pluggable Hierarchical Database. ii puppet 3.3.1-1puppetlabs1all Centralized configuration management - agent startup and compatibility scripts ii puppet-common 3.3.1-1puppetlabs1all Centralized configuration management ii puppetlabs-release 1.0-7 all Package to install Puppet Labs gpg key and apt repo ii ruby-rgen 0.6.5-1puppetlabs1all A framework supporting Model Driven Software Development (MDSD) If this issue is still happening, more information is needed to reproduce the specific case where it's triggered. Add Comment Puppet / PUP-1267 puppet help only show error message
Jira (PUP-1403) puppet service is missing on Ubuntu 12.04.3 LTS
Title: Message Title Daniel Dreier commented on an issue Re: puppet service is missing on Ubuntu 12.04.3 LTS I tried to reproduce this under Ubuntu 12.04 LTS. Here's what I did: apt-get install puppet=2.7.25-1puppetlabs1 puppet=common=2.7.25-1puppetlabs1 chkconfig puppet # gets expected result apt-get install puppet # updates to 3.4.2 chkconfig puppet # gets expected result again Is the /etc/init.d/puppet file present on your system? What process did you follow when you upgraded from 2.7.x to 3.4.x? To verify your install, you can run debsums --all puppet to have dpkg verify installed files against the md5 hashes expected. You may need to install debsums. Posting the output of that command would be helpful. Add Comment Puppet / PUP-1403 puppet service is missing on Ubuntu 12.04.3 LTS I've been running couple Centos 6.5 and Ubuntu 12.04.3 LTS in my test lab. Once Centos is puppetmaster. then i realized that Ubuntu puppet agent was a little bit outdated (version 2.7.x) then I've added puppetlab repos and updated the client. I realized that installed version was newer then on the server and other client. I've updated them as well. then... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1426) puppet cert list and clean commands should be mutually exclusive
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1426 puppet cert list and clean commands should be mutually exclusive Change By: Daniel Dreier Issue Type: NewFeature 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/groups/opt_out.
Jira (PUP-1426) puppet cert list and clean commands should be mutually exclusive
Title: Message Title Daniel Dreier commented on an issue Re: puppet cert list and clean commands should be mutually exclusive This is really two issues: 1) Decide if puppet cert clean list should silently disregard the second action or fail entirely without running anything, and 2) Feature request that the --all flag trigger a confirmation prompt before deleting anything. I've experimented, and confirmed that puppet cert command1 command2 will run command1 and silently ignore command2. puppet cert clean list --all does indeed remove all certs. In puppet apply the behavior is the same but a warning is given. root@server:/# puppet apply bootstrap.pp nodes.pp Warning: Only one file can be applied per run. Skipping nodes.pp Informally, I'd recommend using etckeeper or another similar tool to automatically keep the cert directory and the rest of /etc under revision control. It's bailed me out of similar situations a few times. I'm going to mark this as a feature request because it's consistent with the way the rest of puppet behaves. Add Comment Puppet / PUP-1426 puppet cert list and clean commands should be mutually exclusive When running the puppet cert command, you should not be able to pass both list and clean in the same command. Example: http://paste.debian.net/75956/ In this case, adding --all seems to have nuked the whole of the puppet cert directory and completely broken someone's installation. This should not be possible. Ideally, when using puppet cert cl...
Jira (PUP-1426) puppet cert list and clean commands should be mutually exclusive
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1426 puppet cert list and clean commands should be mutually exclusive Change By: Daniel Dreier Issue Type: Bug NewFeature Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1426) puppet cert list and clean commands should be mutually exclusive
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1426 puppet cert list and clean commands should be mutually exclusive Change By: Daniel Dreier Affects Version/s: 3.4.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/groups/opt_out.
Jira (PUP-1426) puppet cert list and clean commands should be mutually exclusive
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1426 puppet cert list and clean commands should be mutually exclusive Change By: Daniel Dreier Priority: Major Normal Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1426) puppet cert list and clean commands should be mutually exclusive
Title: Message Title Daniel Dreier assigned an issue to Daniel Dreier Puppet / PUP-1426 puppet cert list and clean commands should be mutually exclusive Change By: Daniel Dreier Assignee: DanielDreier Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1426) puppet cert list and clean commands should be mutually exclusive
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1426 puppet cert list and clean commands should be mutually exclusive Change By: Daniel Dreier Assignee: DanielDreier CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1426) puppet cert list and clean commands should be mutually exclusive
Title: Message Title Daniel Dreier commented on an issue Re: puppet cert list and clean commands should be mutually exclusive Charlie - marked needs information because the information needed is a decision about whether either of these two improvement requests will be considered. Please let me know if there's a better status to indicate that. Add Comment Puppet / PUP-1426 puppet cert list and clean commands should be mutually exclusive When running the puppet cert command, you should not be able to pass both list and clean in the same command. Example: http://paste.debian.net/75956/ In this case, adding --all seems to have nuked the whole of the puppet cert directory and completely broken someone's installation. This should not be possible. Ideally, when using puppet cert cl... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork. {noformat} #file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;} {noformat} Usingtheabovemanifestthefollowingdoesnotactasexpected.puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpectedmkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothingtouch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat} Usingtheabovemanifestthefollowingdoesnotactasexpected. {noformat} puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected {noformat}{noformat} mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing {noformat}{noformat} touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec {noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory, recurse=true,checksum=mtime, mode=644, notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null: alias=tar, refreshonly=true; }{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1239) file resource can't be used to monitor file changes recursively
Title: Message Title
Daniel Dreier updated an issue
Puppet / PUP-1239
file resource can't be used to monitor file changes recursively
Change By:
Daniel Dreier
foralongtimeihaveusedpuppettomonitoradirectoryrecursivelyforfilechangesbutsinceupgradingto2.6thatdoesn'tappeartowork.{noformat}#file_test.ppfile{/tmp/file_test:ensure=directory,recurse=true,checksum=mtime,mode=644,notify=Exec[tar];}exec{/bin/tar-cf-/tmp/file_test/dev/null:alias=tar,refreshonly=true;}{noformat}Usingtheabovemanifestthefollowingdoesnotactasexpected.{noformat}puppetapply--verbosefile_test.pp#creates/tmp/file_testandrunsexecasexpected{noformat}{noformat}mkdir/tmp/file_test/{1,2,3,4,5,6}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexecpuppetapply--verbosefile_test.pp#doesnothing,shoulddonothing{noformat}{noformat}touch/tmp/file_test/{1,2,3,4,5,6}/{10,11,12,15}puppetapply--verbosefile_test.pp#doesnothing,shouldrunexec{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
