Jira (PUP-3989) output of puppet module generate does not include a .fixtures.yml file causing tests to fail
Title: Message Title
Geoff Williams updated an issue
Puppet / PUP-3989
output of puppet module generate does not include a .fixtures.yml file causing tests to fail
Change By:
Geoff Williams
h2. BackgroundUsing the command {{puppet module generate ...}} doesn't create a module with a functional RSpec testing infrastructureh2. Test caseGenerate a module and observe the tests don't run out of the box:{noformat}[root@localhost ~]# puppet module generate test-testWe need to create a metadata.json file for this module. Please answer thefollowing questions; if the question is not applicable to this module, feel freeto leave it blank.Puppet uses Semantic Versioning (semver.org) to version modules.What version is this module? [0.1.0]--> Who wrote this module? [test]--> What license does this module code fall under? [Apache 2.0]--> How would you describe this module in a single sentence?--> Where is this module's source code repository?--> Where can others go to learn more about this module?--> Where can others go to file issues about this module?--> { "name": "test-test", "version": "0.1.0", "author": "test", "summary": null, "license": "Apache 2.0", "source": "", "project_page": null, "issues_url": null, "dependencies": [{"name":"puppetlabs-stdlib","version_requirement":">= 1.0.0"} ]}About to generate this metadata; continue? [n/Y]--> yNotice: Generating module at /root/test-test...Notice: Populating templates...Finished; module generated in test-test.test-test/teststest-test/tests/init.pptest-test/Rakefiletest-test/spectest-test/spec/classestest-test/spec/classes/init_spec.rbtest-test/spec/spec_helper.rbtest-test/Gemfiletest-test/manifeststest-test/manifests/init.pptest-test/metadata.jsontest-test/README.md[root@localhost ~]# cd test-test/[root@localhost test-test]# bundle installDon't run Bundler as root. Bundler can ask for sudo if it is needed, andinstalling your bundle as root will break this application for all non-rootusers on this machine.Fetching gem metadata from https://rubygems.org/..Fetching version metadata from https://rubygems.org/..Resolving dependencies...Using rake 10.4.2Using CFPropertyList 2.2.8Using diff-lcs 1.2.5Using facter 2.4.0Using json_pure 1.8.2Using hiera 1.3.4Using metaclass 0.0.4Using mocha 1.1.0Using puppet 3.7.4Using puppet-lint 1.1.0Using puppet-syntax 1.4.1Using rspec-core 2.99.2Using rspec-expectations 2.99.2Using rspec-mocks 2.99.3Using rspec 2.99.0Using rspec-puppet 2.0.0Using puppetlabs_spec_helper 0.8.2Using bundler 1.7.13Your bundle is complete!Use `bundle show [gemname]` to see where a bundled gem is installed.[root@localhost test-test]# bundle exec rake spec/usr/bin/ruby -S rspec spec/classes/init_spec.rb --colorFFailures: 1) test with defaults for all parameters should contain Class[test] Failure/Error: it { should contain_class('test') } Puppet::Error: Could not find class test for localhost.lan.asio on node localhost.lan.asio # /usr/share/ruby/benchmark.rb:296:in `realtime' # ./spec/classes/init_spec.rb:5:in `block (3 levels) in 'Finished in 0.04774 seconds1 example, 1 failureFailed examples:rspec ./spec/classes/init_spec.rb:5 # test with defaults for all parameters should contain Clas
Jira (PUP-3989) output of puppet module generate does not include a .fixtures.yml file causing tests to fail
Title: Message Title Geoff Williams created an issue Puppet / PUP-3989 output of puppet module generate does not include a .fixtures.yml file causing tests to fail Issue Type: Bug Affects Versions: PUP 3.7.4 Assignee: Unassigned Components: Platform Created: 2015/02/09 10:09 PM Environment: CentOS Linux release 7.0.1406 (Core) Priority: Normal Reporter: Geoff Williams Background Using the command puppet module generate ... doesn't create a module with a functional RSpec testing infrastructure Test case Generate a module and observe the tests don't run out of the box:
Jira (PDB-1136) communicate v4 API changes to stakeholders ahead of release
Title: Message Title Steve Axthelm updated an issue PuppetDB / PDB-1136 communicate v4 API changes to stakeholders ahead of release Change By: Steve Axthelm Since we're dropping v2 and v3 for the next release, and v4 is undergoing some changes, there is no API version in PDB 2.2.2 that matches reality in 3.0. We need to make sure other teams using PDB are aware of the changes occurring to v4 in the next release, before the release occurs. We should send out an email once we have a complete list of changes.An incomplete list is:- dashes in command and API endpoint fieldnames converted to underscores (PDB-698) - reports endpoint now supplies resource events (PDB-1072 ?) - top level extract (PDB-1043) - catalogs now queryable (PDB-1028)- make the /v4/catalogs endpoint use "certname" key instead of "name" (PDB-1099) Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1136) communicate v4 API changes to stakeholders ahead of release
Title: Message Title Steve Axthelm commented on PDB-1136 Re: communicate v4 API changes to stakeholders ahead of release Wyatt Alt can you confirm that I got the correct issue numbers in the description? TIA, -S Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3930) Applying catalogs spends an inordinate amount of time checking for failed dependencies.
Title: Message Title Nelson Elhage commented on PUP-3930 Re: Applying catalogs spends an inordinate amount of time checking for failed dependencies. PR: https://github.com/puppetlabs/puppet/pull/3591 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3167) node namespaces override class namespaces if they happen to match
Title: Message Title Henrik Lindberg commented on PUP-3167 Re: node namespaces override class namespaces if they happen to match merged to master at ae08c3e Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3167) node namespaces override class namespaces if they happen to match
Title: Message Title Henrik Lindberg commented on PUP-3167 Re: node namespaces override class namespaces if they happen to match The description of the difficulty is accurate - in more detail, parts of the code pass around a string as "the name", other places pass around a Resource (in its various flavors) with only type (:node), and title (the node name). the various ways nodes (and other things) are looked up makes logic flip between these various uses of names. The real problem needs to be fixed a different way after having better understood what is causing the problem (all the information should be there for the logic to make the right decision). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3167) node namespaces override class namespaces if they happen to match
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-3167
node namespaces override class namespaces if they happen to match
Change By:
Henrik Lindberg
if a node happens to match the name of a class, it will override its namespace with the node's namespace (which I didn't even know existed). I marked this as major b/c it potentially breaks any modules that rely on fully qualified namespace lookup (like apache)The issue is probably better articulated with the following simple example: {code} class foo { $bar = 'one'}node /foo/ { $bar = 'two' include foo notice("${::foo::bar}")} {code}
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Henrik Lindberg commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging On hiera master at (https://github.com/puppetlabs/hiera/commit/4d8351bd3e8a82b8e473c8b724c70878f620de5c) it is under code. Hiera 2.0.0 is not yet released though due to possible change of paths before release... Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title Henrik Lindberg commented on PUP-3626 Re: cannot export file from puppet client via puppetdb to another puppet client ping Nicholas Fagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3886) Add yumrepo resource spec integration tests
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3886 Add yumrepo resource spec integration tests Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title
Kylo Ginsberg updated an issue
Puppet / PUP-3626
cannot export file from puppet client via puppetdb to another puppet client
Change By:
Kylo Ginsberg
I have two hosts, 'puppet' which is also known as 'host1' and another node which resolves to 'host2'.Both hosts are run puppet apply via the command line with great success against apache2/rails/puppetmaster.The following node definition works very well. the manifest is on disk on puppet/node1. When run via puppet agent on node2, the manifest copies/syncs the content of node2:/tmp/text into node2:/tmp/text2. {code}node 'node2'{file{"/tmp/text2":source => "/tmp/text",}}{code} Extending this idea with puppetdb over both nodes; {code}node 'node1'{File <<| tag == "thisisatag2" |>>}node 'node2'{@@file{"/tmp/text3":owner => "root",group => "root",source => "/tmp/text",tag => "thisisatag2",}}{code} From my reading and use of puppetdb/exported resources I expect that that the file node1:/tmp/text3 will have the _same_ source file/content/bytes as the first example, that is the content of node2:/tmp/text. In other words, the File resource is treated as an exported resource and stored in puppetdb rather than written directly to disk.Once puppet agent is run on node2, then puppet agent is run on node1, the node1:/tmp/text3 should be written to disk with the same content as node2:/tmp/text.In this scenario, I receive the trace/barf from a puppet agent run on node1 [1]. I expect that this does not work because puppet master (running on node1) compiles the manifest for a file and there is an implicit scope issue maybe (I've been wrong before). indeed in all the code I've seen in this use case the normal path is to use template(), puppet:///modules/${module_name}/filename, content => "abs string"' or something equally easy for puppet master to address locally. {code} [1] {code} Error: /Stage[main]/Main/Node[node1]/File[/tmp/text3]: Could not evaluate: Could not retrieve information from environment production source(s) file:/tmp/text/usr/share/ruby/vendor_ruby/puppet/util/errors.rb:104:in `fail'/usr/share/ruby/vendor_ruby/puppet/type/file/source.rb:187:in `metadata'/usr/share/ruby/vendor_ruby/puppet/type/file/source.rb:111:in `copy_source_values'/usr/share/ruby/vendor_ruby/puppet/type/file.rb:711:in `retrieve'/usr/share/ruby/vendor_ruby/puppet/type.rb:1076:in `retrieve_resource'/usr/share/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:236:in `from_resource'/usr/share/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:19:in `evaluate'/usr/share/ruby/vendor_ruby/puppet/transaction.rb:204:in `apply'/usr/share/ruby/vendor_ruby/puppet/transaction.rb:217:in `eval_resource'/usr/share/ruby/vendor_ruby/puppet/transaction.rb:147:in `call'/usr/share/ruby/vendor_ruby/puppet/transaction.rb:147:in `block (2 levels) in evaluate'/usr/share/ruby/vendor_ruby/puppet/util.rb:327:in `block in thinmark'/usr/share/ruby/benchmark.rb:296:in `realtime'/usr/share/ruby/vendor_ruby/puppet/util.rb:326:in `thinmark'/usr/share/ruby/vendor_ruby/puppet/transaction.rb:147:in `block in evaluate'/usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in `traverse'/usr/share/ruby/vendor_r
Jira (PUP-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-3626
cannot export file from puppet client via puppetdb to another puppet client
Change By:
Henrik Lindberg
I have two hosts, 'puppet' which is also known as 'host1' and another node which resolves to 'host2'.Both hosts are run puppet apply via the command line with great success against apache2/rails/puppetmaster.The following node definition works very well. the manifest is on disk on puppet/node1. When run via puppet agent on node2, the manifest copies/syncs the content of node2:/tmp/text into node2:/tmp/text2. {code} node 'node2'{file{"/tmp/text2":source => "/tmp/text",}} {code} Extending this idea with puppetdb over both nodes; {code} node 'node1'{File <<| tag == "thisisatag2" |>>}node 'node2'{@@file{"/tmp/text3":owner => "root",group => "root",source => "/tmp/text",tag => "thisisatag2",}} {code} From my reading and use of puppetdb/exported resources I expect that that the file node1:/tmp/text3 will have the _same_ source file/content/bytes as the first example, that is the content of node2:/tmp/text. In other words, the File resource is treated as an exported resource and stored in puppetdb rather than written directly to disk.Once puppet agent is run on node2, then puppet agent is run on node1, the node1:/tmp/text3 should be written to disk with the same content as node2:/tmp/text.In this scenario, I receive the trace/barf from a puppet agent run on node1 [1]. I expect that this does not work because puppet master (running on node1) compiles the manifest for a file and there is an implicit scope issue maybe (I've been wrong before). indeed in all the code I've seen in this use case the normal path is to use template(), puppet:///modules/${module_name}/filename, content => "abs string"' or something equally easy for puppet master to address locally. {code} [1]Error: /Stage[main]/Main/Node[node1]/File[/tmp/text3]: Could not evaluate: Could not retrieve information from environment production source(s) file:/tmp/text/usr/share/ruby/vendor_ruby/puppet/util/errors.rb:104:in `fail'/usr/share/ruby/vendor_ruby/puppet/type/file/source.rb:187:in `metadata'/usr/share/ruby/vendor_ruby/puppet/type/file/source.rb:111:in `copy_source_values'/usr/share/ruby/vendor_ruby/puppet/type/file.rb:711:in `retrieve'/usr/share/ruby/vendor_ruby/puppet/type.rb:1076:in `retrieve_resource'/usr/share/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:236:in `from_resource'/usr/share/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:19:in `evaluate'/usr/share/ruby/vendor_ruby/puppet/transaction.rb:204:in `apply'/usr/share/ruby/vendor_ruby/puppet/transaction.rb:217:in `eval_resource'/usr/share/ruby/vendor_ruby/puppet/transaction.rb:147:in `call'/usr/share/ruby/vendor_ruby/puppet/transaction.rb:147:in `block (2 levels) in evaluate'/usr/share/ruby/vendor_ruby/puppet/util.rb:327:in `block in thinmark'/usr/share/ruby/benchmark.rb:296:in `realtime'/usr/share/ruby/vendor_ruby/puppet/util.rb:326:in `thinmark'/usr/share/ruby/vendor_ruby/puppet/transaction.rb:147:in `block in evaluate'/usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in `traverse'/usr/share/ruby/vendor_ruby/
Jira (PUP-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-3626 cannot export file from puppet client via puppetdb to another puppet client Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3274) Remove old parser/evaluator
Title: Message Title Henrik Lindberg commented on PUP-3274 Re: Remove old parser/evaluator Added link to PUP-3987 which is the backport of one of the commits in this ticket. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3987) Change Closure.call to not take scope
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3987 Change Closure.call to not take scope Change By: Henrik Lindberg Sprint: Language 2015-02-18 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Eric Sorenson commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging Ah, yep, under code/ is correct – In the current version it landed in /etc/puppetlabs/agent/hiera.yaml Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3167) node namespaces override class namespaces if they happen to match
Title: Message Title Hailee Kenney commented on PUP-3167 Re: node namespaces override class namespaces if they happen to match So we were ultimately unable to fix the issue with non-regex node names potentially conflicting with class names using this method. This is due to the fact that the puppet code base does not consistently make the distinction between the resource representing the node and the node itself. This means that it will try to use both the munged resource name (which we tried to change to `_nodefoo`) and the node name itself interchangeably. In order for this method of prepending a string on the front of the resource name to work, puppet would have to stop using the two names as if they are equivalent. This method works for regex node names (which will now have resources named `node_regexp_foo`) because they are already treated differently. (Henrik Lindberg may be able to explain this better than I can) Ultimately we will need a more complex fix to prevent non-regex node names and classes from stepping one each other. I will file a ticket for this. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Christopher Price commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging When we chatted about this stuff in person a week or two ago, `hiera.yaml` definitely came out on the list of things we "want to sync to all masters". Assuming that's still the case, it needs to live in the code directory, or else we will need to change some other part of the Grand Plan. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3988) remove logic for "single feature" hostname in 4.0 validator
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-3988 remove logic for "single feature" hostname in 4.0 validator Issue Type: Improvement Assignee: Unassigned Created: 2015/02/09 5:09 PM Fix Versions: PUP 4.1.0 Priority: Normal Reporter: Henrik Lindberg The validator for 4.0 still has special handling of "single" vs "multiple" hostnames for nodes. This is no longer needed since node inheritance has been discontinued. The validation path for "single name" was only used to validate the inherits / parent of a node and can now be simplified. This is an internal maintenance change. It may have a minute performance benefit but should essentially be done since the logic is dead code. Add Comment
Jira (PUP-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title Rob Mattson updated an issue Puppet / PUP-3626 cannot export file from puppet client via puppetdb to another puppet client +DOCS, this issue could be documentation setting the wrong expectation and described behavior in this bug is expected. Change By: Rob Mattson Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3626) cannot export file from puppet client via puppetdb to another puppet client
Title: Message Title Rob Mattson updated an issue Puppet / PUP-3626 cannot export file from puppet client via puppetdb to another puppet client Change By: Rob Mattson Labels: docs_reviewed puppet-agent puppetdb Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3987) Change Closure.call to not take scope
Title: Message Title Henrik Lindberg commented on PUP-3987 Re: Change Closure.call to not take scope For review - this removes an unused parameter to make 3x API for code blocks / lambdas behave the same way on 3x. as on master. Basically if tests pass, the change is good as we are the only ones that have functions calling lambdas and they are changed in the PR. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3987) Change Closure.call to not take scope
Title: Message Title Henrik Lindberg commented on PUP-3987 Re: Change Closure.call to not take scope Merged to stable in PR 3588 https://github.com/puppetlabs/puppet/pull/3588 at 856c7ce. Note that the commit is mis-labeled with PUP-3274 instead of this ticket (3987). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3987) Change Closure.call to not take scope
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-3987 Change Closure.call to not take scope Issue Type: Bug Assignee: Unassigned Components: DSL Created: 2015/02/09 4:47 PM Fix Versions: PUP 3.7.5 Priority: Normal Reporter: Henrik Lindberg In Puppet 4.0.0 the Closure.call method does not longer take scope as a parameter (it was unused). This change should have also been made to stable as the API should be the same for 3.7.x with future parser and Puppet 4.0.0. This ticket is about backporting the change from PUP-3274 to stable. Add Comment
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Eric Sorenson commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging A couple of comments here after poking around in an actual AIO-installed setup for a bit at Contrib Summit with Dominic Cleal Stefan Goethals Julien Pivotto Justin Stoller. The code/ directory shouldn't live under agent/, as none of its contents are used by an agent. They are either used by a master or by puppet apply; my suggestion would be to move that up a directory to live directly under /etc/puppetlabs. Similarly, the hiera.yaml config location lands in a weird/wrong place, but it's less obvious where it should go, other than perhaps /etc/puppetlabs/hiera/ since it's technically a separate project and set of configuration. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3961) investigate tests for hiera functions
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3961 investigate tests for hiera functions Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3961) investigate tests for hiera functions
Title: Message Title Eric Thompson commented on PUP-3961 Re: investigate tests for hiera functions existing acceptance: 03-lookup_data_with_a_scope.rb looks up a single value from hiera commandline and includes a scope.yaml file 04-lookup_data_with_array_search.rb looks up an array from the hiera commandline and checks proper order on return Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3986) Expand predefined OID's for Puppet's extension attributes
Title: Message Title Jeremy Barlow updated an issue Puppet / PUP-3986 Expand predefined OID's for Puppet's extension attributes Change By: Jeremy Barlow Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title stack72 commented on FACT-718 Re: Allow for disabling certain facts within Facter Thanks for getting in touch about this. By solving this issue, we would avoid situations like this: https://t.co/9oEwsMuMKG By collecting all these facts (that I am personally not interested in), my puppetdb is working harder than it should be. This is a great article on why I started looking into this topic https://t.co/DahIH9VeX6 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Kylo Ginsberg commented on FACT-718 Re: Allow for disabling certain facts within Facter This needs some design/requirements work, but marking as "Ready for Engineering" so it shows up on our scrum boards Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Facter / FACT-718 Allow for disabling certain facts within Facter Change By: Kylo Ginsberg Assignee: Eric Sorenson Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3986) Expand predefined OID's for Puppet's extension attributes
Title: Message Title Chris Barker commented on PUP-3986 Re: Expand predefined OID's for Puppet's extension attributes Updated the oids.rb file and PR is here: https://github.com/puppetlabs/puppet/pull/3589 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3986) Expand predefined OID's for Puppet's extension attributes
Title: Message Title Chris Barker created an issue Puppet / PUP-3986 Expand predefined OID's for Puppet's extension attributes Issue Type: New Feature Assignee: Unassigned Created: 2015/02/09 3:44 PM Priority: Normal Reporter: Chris Barker Currently there are four predefined attributes for OID's we can reference in the Puppet DSL, adding some more standard names would make their adoption easier. Referencing Cloudability's whitepapers on tagging nodes for resource allocation and tracking (https://support.cloudability.com/hc/en-us/article_attachments/200622623/_White_Paper__AWS_Cost_Allocation_Using_Tags_And_Linked_Accounts__1_.pdf) these are the suggested additional names: pp_cost_center pp_product pp_project pp_application pp_service pp_employee pp_created_by pp_environment pp_role pp_software_version pp_department pp_cluster pp_provisioner Add Comment
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Peter Huene commented on FACT-718 Re: Allow for disabling certain facts within Facter This wasn't on the radar for Facter 3 at least. We should look into the best way of filtering out undesirable facts that just clutter things up. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Rob Reynolds commented on FACT-718 Re: Allow for disabling certain facts within Facter Peter Huene Paul just pointed this out... is this on the radar at all? cc stack72 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3985) With `storeconfigs = false` there are no warnings or errors about exported resources
Title: Message Title Zachary Stern created an issue Puppet / PUP-3985 With `storeconfigs = false` there are no warnings or errors about exported resources Issue Type: Bug Assignee: Unassigned Created: 2015/02/09 2:59 PM Priority: Normal Reporter: Zachary Stern If you set storeconfigs = false on the master, exported resources will not function, but there are no warnings or errors about this anywhere that I can see, even when compiling a manifest that exports resources. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3981) Missing PMT Acceptance Test for Building Module with a Modulefile
Title: Message Title Ryan Gard assigned an issue to Ryan Gard Puppet / PUP-3981 Missing PMT Acceptance Test for Building Module with a Modulefile Change By: Ryan Gard Resolution: Fixed Assignee: Ryan Gard Status: Ready for Merge Closed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3981) Missing PMT Acceptance Test for Building Module with a Modulefile
Title: Message Title Anderson Mills commented on PUP-3981 Re: Missing PMT Acceptance Test for Building Module with a Modulefile Merged in 49076ec. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3959) Acceptance test failure in external_ca_support/jetty_external_root_ca.rb
Title: Message Title Jeff McCune commented on PUP-3959 Re: Acceptance test failure in external_ca_support/jetty_external_root_ca.rb I've also verified the test passes successfully when $(puppet master --configprint confdir)/environments/production/modules exists. As a result it's likely no additional changes are necessary beyond the packaging fixes. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3274) Remove old parser/evaluator
Title: Message Title Thomas Hallgren commented on PUP-3274 Re: Remove old parser/evaluator This would be great to have in 3.7.5 too since it actually changes the way blocks are called from functions. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3984) Allow Beaker the use of custom Vagrantfiles in beaker-rspec
Title: Message Title Matthew Callaway commented on PUP-3984 Re: Allow Beaker the use of custom Vagrantfiles in beaker-rspec https://github.com/puppetlabs/beaker/pull/675 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3984) Allow Beaker the use of custom Vagrantfiles in beaker-rspec
Title: Message Title Matthew Callaway created an issue Puppet / PUP-3984 Allow Beaker the use of custom Vagrantfiles in beaker-rspec Issue Type: New Feature Assignee: Unassigned Components: Modules Created: 2015/02/09 1:15 PM Priority: Normal Reporter: Matthew Callaway beaker-rspec restricts the use of Vagrant by building a Vagrantfile based on a limited set of options. If one can specify their own Vagrantfiles, then beaker-rspec gets to use the full power of Vagrant. This means immediate support for other hypervisors like Openstack and vSphere. I'll attach a github pull request to this issue after its creation. Add Comment
Jira (PUP-3959) Acceptance test failure in external_ca_support/jetty_external_root_ca.rb
Title: Message Title Jeff McCune commented on PUP-3959 Re: Acceptance test failure in external_ca_support/jetty_external_root_ca.rb This is blocked by PUP-2037. For the test to pass, the puppet package needs to create a production environment directory so that the puppet master process does not return the following error message to the agent. Info: Retrieving pluginfacts Error: /File[/tmp/jetty_external_root_ca.6BuzpZ/etc/agent/var/facts.d]: Could not evaluate: Could not retrieve information from environment production source(s) puppet:///pluginfacts Info: Retrieving plugin Error: /File[/tmp/jetty_external_root_ca.6BuzpZ/etc/agent/var/lib]: Could not evaluate: Could not retrieve information from environment production source(s) puppet:///plugins Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3959) Acceptance test failure in external_ca_support/jetty_external_root_ca.rb
Title: Message Title Jeff McCune assigned an issue to Unassigned Puppet / PUP-3959 Acceptance test failure in external_ca_support/jetty_external_root_ca.rb Change By: Jeff McCune Assignee: Jeff McCune Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-797) Virtual fact on Linux does not work
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-797 Virtual fact on Linux does not work Change By: Kylo Ginsberg Fix Version/s: FACT 2.4.1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3959) Acceptance test failure in external_ca_support/jetty_external_root_ca.rb
Title: Message Title Jeff McCune commented on PUP-3959 Re: Acceptance test failure in external_ca_support/jetty_external_root_ca.rb This failure is legit and the test is making a valid assertion that the agent run completes with no errors or failures. The root cause of the failure is that the Puppet AIO packages are being installed in a way that does not produce a valid production environment. The solution to this problem is to fix the AIO packages such that the production environment behaves well, without errors or failures, in the default "out of the box" case. Here's what I did to resolve the issue and get the test to pass on the system under test: sudo mkdir -p $(puppet master --configprint environmentpath)/production/modules/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2037) Switch rpm/deb package manifest dir to default directory environment.
Title: Message Title Matthaus Owens commented on PUP-2037 Re: Switch rpm/deb package manifest dir to default directory environment. Looks like this is causing failures for puppet-server. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2037) Switch rpm/deb package manifest dir to default directory environment.
Title: Message Title Matthaus Owens commented on PUP-2037 Re: Switch rpm/deb package manifest dir to default directory environment. This should happen for AIO before puppet 4. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3981) Missing PMT Acceptance Test for Building Module with a Modulefile
Title: Message Title Ryan Gard assigned an issue to Anderson Mills Puppet / PUP-3981 Missing PMT Acceptance Test for Building Module with a Modulefile Change By: Ryan Gard Assignee: Ryan Gard Anderson Mills Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3982) Ensure puppet service supports conditional restart
Title: Message Title Branan Purvine-Riley updated an issue Puppet / PUP-3982 Ensure puppet service supports conditional restart Change By: Branan Purvine-Riley Summary: Ensure agent components support puppet service supports conditional restart Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3983) Ensure agent components support conditional restart
Title: Message Title Matthaus Owens created an issue Puppet / PUP-3983 Ensure agent components support conditional restart Issue Type: Task Assignee: Branan Purvine-Riley Created: 2015/02/09 11:08 AM Priority: Normal Reporter: Matthaus Owens To ensure clean upgrades, calling conditional restart/try-restart/condrestart in the post will be a better experience. Currently, only puppet and mcollective have services that will need to updated. Debian and redhat support this behavior, I don't know about OSX, solaris, or AIX for this. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3982) Ensure agent components support conditional restart
Title: Message Title Branan Purvine-Riley updated an issue Puppet / PUP-3982 Ensure agent components support conditional restart Change By: Branan Purvine-Riley Sprint: Client 2015-02-18 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3982) Ensure agent components support conditional restart
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-3982 Ensure agent components support conditional restart Change By: Matthaus Owens Sprint: RE 2015-02-11 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3982) Ensure agent components support conditional restart
Title: Message Title Matthaus Owens moved an issue Puppet / PUP-3982 Ensure agent components support conditional restart Change By: Matthaus Owens Scrum Team: Client Platform Workflow: Release Engineering Platform Workflow Key: RE PUP - 3277 3982 Project: Release Engineering Puppet Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3560) Add support for properly signed trusted facts
Title: Message Title Erik Dasher commented on PUP-3560 Re: Add support for properly signed trusted facts Closing out based on conversation in standup today. Review not needed unless ticket links to acceptance criteria. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3254) Remove all Modulefile functionality in PMT except warnings about ignoring
Title: Message Title Ryan Gard commented on PUP-3254 Re: Remove all Modulefile functionality in PMT except warnings about ignoring Functional review passed on master branch at 306b3a701983777e045d601cedcf6e5a5b7ce9ac. All PMT acceptance tests pass and manual verification Modulefile presence during module building validated. The only issue found was that there was not an automated test for ignoring the Modulefile if present. (Being tracked in PUP-3981) Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3981) Missing PMT Acceptance Test for Building Module with a Modulefile
Title: Message Title Ryan Gard updated an issue Puppet / PUP-3981 Missing PMT Acceptance Test for Building Module with a Modulefile Change By: Ryan Gard Priority: Normal Critical Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3254) Remove all Modulefile functionality in PMT except warnings about ignoring
Title: Message Title Ryan Gard assigned an issue to Unassigned Puppet / PUP-3254 Remove all Modulefile functionality in PMT except warnings about ignoring Change By: Ryan Gard Assignee: Ryan Gard Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3254) Remove all Modulefile functionality in PMT except warnings about ignoring
Title: Message Title Ryan Gard updated an issue Puppet / PUP-3254 Remove all Modulefile functionality in PMT except warnings about ignoring Change By: Ryan Gard QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1141) Update changelog/release notes
Title: Message Title Rob Browning commented on PDB-1141 Re: Update changelog/release notes Current version of the changes are here: https://github.com/rbrw/puppetdb/tree/ticket/stable/update-for-2.3.0-release Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1142) Update documentation indexes for new major release
Title: Message Title Rob Browning commented on PDB-1142 Re: Update documentation indexes for new major release The preliminary changes are here https://github.com/rbrw/puppet-docs/tree/ticket/master/pdb-1142-update-for-2.3.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3981) Missing PMT Acceptance Test for Building Module with a Modulefile
Title: Message Title Ryan Gard created an issue Puppet / PUP-3981 Missing PMT Acceptance Test for Building Module with a Modulefile Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Ryan Gard Components: PMT Created: 2015/02/09 10:03 AM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Ryan Gard The PUP-3254 ticket removes support for Modulefile support in the PMT and will warn the user if one is provided. There is currently no acceptance test that verifies that a user will receive a warning message if a Modulefile is present during module building.
Jira (PUP-3254) Remove all Modulefile functionality in PMT except warnings about ignoring
Title: Message Title Anderson Mills assigned an issue to Ryan Gard Puppet / PUP-3254 Remove all Modulefile functionality in PMT except warnings about ignoring Change By: Anderson Mills Assignee: Ryan Gard Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3959) Acceptance test failure in external_ca_support/jetty_external_root_ca.rb
Title: Message Title Jeff McCune assigned an issue to Jeff McCune Puppet / PUP-3959 Acceptance test failure in external_ca_support/jetty_external_root_ca.rb Change By: Jeff McCune Assignee: Jeff McCune Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-311) hiera 2.0.0 2015-01-28 Release
Title: Message Title Melissa Stone commented on HI-311 Re: hiera 2.0.0 2015-01-28 Release Just so everyone knows, I'll be on PTO Feb 13-17th, and unable to do any releases during that time. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1139) PuppetDB 2.3.0 Release
Title: Message Title Melissa Stone commented on PDB-1139 Re: PuppetDB 2.3.0 Release Just so everyone knows, I'll be on PTO Feb 13-17th, and unable to do any releases during that time. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3821) Use of cfacter on Windows causes error
Title: Message Title Josh Cooper assigned an issue to Peter Huene Puppet / PUP-3821 Use of cfacter on Windows causes error Change By: Josh Cooper Assignee: Michael Smith Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3980) Unrecognized resource name if dependency is specified with "->"
Title: Message Title
Alfonso A created an issue
Puppet / PUP-3980
Unrecognized resource name if dependency is specified with "->"
Issue Type:
Bug
Affects Versions:
PUP 3.7.2
Assignee:
Unassigned
Components:
Language, QA
Created:
2015/02/09 8:22 AM
Environment:
Debian Jessie.
Labels:
github puppet_apply
Priority:
Normal
Reporter:
Alfonso A
A block like this: [...code] -> service { ['service1', 'service2']: ensure => stopped, }
wont work if is preceded by the Chaining Arrows ("->", "~>")
Jira (PUP-3978) Missing values for optional parameters places block at wrong position
Title: Message Title Henrik Lindberg commented on PUP-3978 Re: Missing values for optional parameters places block at wrong position We chatted about the arg_count and last_captures_rest way of defining required, optional and splatted parameters and that we really would like to have indivdual methods to deal with these - e.g. param, optional_param, and splatted_param since that is clearer. This can however be introduced during the 4x series and we can then deprecate the current way of specifying these options while maintaining compatibility. We should fix these at the earliest opportunity - e.g. 4.1.0 and 3.7.6 (unless we actually do actually find some extra time before the 4.0.0 release). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1144) Is there a bug targeted at the release for every commit?
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-1144 Is there a bug targeted at the release for every commit? Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1145) Is there a commit for every bug targeted at the release?
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-1145 Is there a commit for every bug targeted at the release? Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1141) Update changelog/release notes
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-1141 Update changelog/release notes Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1142) Update documentation indexes for new major release
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-1142 Update documentation indexes for new major release Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3978) Missing values for optional parameters places block at wrong position
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-3978 Missing values for optional parameters places block at wrong position Change By: Thomas Hallgren Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1061) PR (1175): Allow tilde in resource name, like in puppet - saimonn
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-1061 PR (1175): Allow tilde in resource name, like in puppet - saimonn Change By: Rob Browning Fix Version/s: PDB 2.3.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-999) PR (1133): (maint) fix broken package tests - wkalt
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-999 PR (1133): (maint) fix broken package tests - wkalt Change By: Rob Browning Fix Version/s: PDB 2.3.0 Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1031) ERROR: update or delete on table "fact_paths" violates foreign key constraint "fact_values_path_id_fk" on table "fact_values"
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-1031 ERROR: update or delete on table "fact_paths" violates foreign key constraint "fact_values_path_id_fk" on table "fact_values" Change By: Rob Browning Fix Version/s: PDB 2.3.0 Fix Version/s: PDB 2.3.x Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3978) Missing values for optional parameters places block at wrong position
Title: Message Title Henrik Lindberg commented on PUP-3978 Re: Missing values for optional parameters places block at wrong position Looks great - a couple of small things: attr_accessor for :closure should be attr_reader as we do not want it to be settable except from the constructor call_function must be changed to accept a Proc instead of being given a puppet block as an argument We should create the PuppetProc in the evaluator (at the origin of the call chain) to avoid having to wrap/unwrap if one puppet function calls another It is currently possible to pass a block to a 3x function via call_function since it is a regular argument. Don't think we need to support that. In case someone has a 3x function written for future parser, they should migrate it to the 4x API. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3978) Missing values for optional parameters places block at wrong position
Title: Message Title Thomas Hallgren commented on PUP-3978 Re: Missing values for optional parameters places block at wrong position I now have a PuppetProc based solution that seems to work very well. It's a little different from what you suggested Henrik Lindberg in that user never needs to know about nor call on PuppetProc. Using yield should be the preferred method but it is always possible to instead declare the last argument as &block. This is indifferent to the caller will also yield the same result when calling block_given?. Access to the block enables it to be passed on or examined (check its arity for instance). Advanced usage may also include checking the closure property of the block if we decide to make that part of the public API. Using yield semantics and &Proc.new to get the block is of course still possible but a Proc.new will always result in a proc that has arity == -1. Here's the current implementation of PuppetProc class Puppet::Pops::Evaluator::PuppetProc < Proc def self.new(closure, &block) proc = super(&block) proc.closure = closure proc end attr_accessor :closure
