Jira (PUP-3699) Render facts as yaml by default
Title: Message Title Erik Daln commented on PUP-3699 Re: Render facts as yaml by default This problem is also solved by PUP-3706 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3717) Log output of service restart commands
Title: Message Title Chris Wilson created an issue Puppet / PUP-3717 Log output of service restart commands Issue Type: New Feature Assignee: Kylo Ginsberg Components: Client, DSL Created: 2014/11/27 4:23 AM Environment: puppet-2.6.18-3.el5 for example. According to docs, this feature is not present in 3.x either. Priority: Normal Reporter: Chris Wilson http://serverfault.com/questions/575495/can-i-get-the-exact-error-when-starting-apache-using-puppet Sometimes, apparently randomly, my Apache restarts fail with this error: Nov 22 05:55:35 censored puppet-agent[30180]: (/Stage[main]/Server::Apache::Service/Service[apache]) Failed to call refresh: Could not restart Service[apache]: Execution of '/sbin/service httpd restart' returned 1: at /etc/puppet/environments/production/modules/server/manifests/apache/service.pp:17 When this happens the old Apache process sits around alongside the new one, and the number of processes on the machine slowly builds up until it dies. How do I debug this? It would be really helpful to see the console output from the restart command. However it seems that only Exec resources have a `logoutput` parameter, not Service resources. This would be really useful to add.
Jira (PDB-1044) Using `in` and `extract` on hyphenated fields throws an error
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1044 Using `in` and `extract` on hyphenated fields throws an error Issue Type: Bug Affects Versions: 2.2.x Assignee: Unassigned Created: 2014/11/27 5:17 AM Priority: Normal Reporter: Kenneth Barber `in` and `extract` queries that include a hyphenated field name fail due to lack of conversion to hyphens. This exists in 2.2.x, and the new code in master shows this symptom, but it doesn't show it for non-sql extracts/projections. root@puppetdb1:~# curl -vv 'http://localhost:8080/v4/nodes?query=\[in,catalog-environment,\[extract,catalog-environment,\[select-nodes,\[=,certname,foo\]\]\]\]' * About to connect() to localhost port 8080 (#0)
Jira (PDB-1044) Using `in` and `extract` on hyphenated fields throws an error
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1044 Using `in` and `extract` on hyphenated fields throws an error Change By: Kenneth Barber Sprint: PuppetDB2014-12-03 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1044) Using `in` and `extract` on hyphenated fields throws an error
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1044 Using `in` and `extract` on hyphenated fields throws an error Change By: Kenneth Barber Sprint: PuppetDB2014-12- 03 17 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1044) Using `in` and `extract` on hyphenated fields throws an error
Title: Message Title Kenneth Barber commented on PDB-1044 Re: Using `in` and `extract` on hyphenated fields throws an error This exhibits the problem in the stable branch, but can be solved implicitly with PDB-698 (whereby we always use underscores) for the 3.x branch (master). Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3436) Optimize CPU intensitive compiler methods
Title: Message Title Henrik Lindberg commented on PUP-3436 Re: Optimize CPU intensitive compiler methods For review - compare the results of the benchmarks below stable vs. master, and master before the merge, and after: benchmark:many_modules benchmark:defined_types Benchmarks are executed like this bundle exec rake benchmark:many_modules Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3638) Remove the manifest handling code from the util/rdoc parsers.
Title: Message Title Henrik Lindberg commented on PUP-3638 Re: Remove the manifest handling code from the util/rdoc parsers. For review: it should still be possible to get documentation for custom types and facts (written in ruby) if attempting to get documentation for puppet manifests the doc generation should not misbehave (crash etc.) the help/doc for the doc app should not mislead the user into thinking that manifests can be documented Since the entire doc tool is slated for removal, and the quality of the tool was not exactly great from the start, the investment in reviewing and fixing found issues should concentrate on things that are blocking / critical that they get fixed. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3140) Illegal number error should include the faulty number
Title: Message Title Henrik Lindberg commented on PUP-3140 Re: Illegal number error should include the faulty number Reviewed: puppet apply -e 'notice 42g' Error: Could not parse for environment production: Illegal number '42g' Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3665) future parser collector override with Resource reference does not work
Title: Message Title Henrik Lindberg commented on PUP-3665 Re: future parser collector override with Resource reference does not work For review - there were two problems: Collecting exported resources without a query - this caused a hard error Collecting exported resources from the catalog - these were missing in the result To review this, a configuration with a functioning PuppetDB (from puppetdb master) is required. Manifests have to be set up such that one node (a) exports some resources (ar1, ar2, ar3), and another node (b) exports resources (br1, br2, br3). A query on (b) should be set up to find ar1, ar2, and br1, br2 (but not the others). This could be done via tagging. The purpose of this test is to ensure that: it collects from both its own catalog, and puppetdb it combines the result A second test should collect all to test that a missing query _expression_ collects all. As an alternative, since the above requires quite a bit of set-up, instead review that spec tests for puppetdb to assert that they cover the above functionality. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this
Jira (PUP-3635) Add a scanf function for string to numeric conversion (and more)
Title: Message Title Henrik Lindberg commented on PUP-3635 Re: Add a scanf function for string to numeric conversion (and more) For review - see the documentation for the scanf function Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2733) Puppet squats on the PuppetX::Puppetlabs and PuppetX::Puppet namespaces
Title: Message Title Henrik Lindberg commented on PUP-2733 Re: Puppet squats on the PuppetX::Puppetlabs and PuppetX::Puppet namespaces This is difficult to review without testing something that earlier had issues with the name squatting. Marking this as reviewed as we have other features that depend on this rename and they do work. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1019) Remove ZAML
Title: Message Title Henrik Lindberg commented on PUP-1019 Re: Remove ZAML Marking as resolved since this is impossible to review - it used to produce YAML, and it still produces YAML only using a different mechanism. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3204) Users and groups created mid-transaction are not found
Title: Message Title Sauce commented on PUP-3204 Re: Users and groups created mid-transaction are not found Any movement on this issue? I just ran head on into it. I have Puppet on Ubuntu 12.04 doing the following: -Register the system with an external directory (in this case Active Directory, via Winbind) -Obviously the previous step modifies nsswitch.conf and suddenly 1000's of users/groups become available -Puppet then tries to chown a directory using a user/group from the previous step. It fails here with error Could not find user. Because Puppet only reads nsswitch.conf upon launching. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1040) PR (153): Fix ssl_protocols - bastelfreak
Title: Message Title gepetto-bot commented on PDB-1040 Re: PR (153): Fix ssl_protocols - bastelfreak kbarber commented: @bastelfreak I'm not sure if the new commits were an attempt to squash these up, don't worry too much about that, we can do it on this side if its a hassle. The patch still does need ammendments to README.md at least however. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-722) PuppetDB response hanging on select-nodes subquery
Title: Message Title Andrii Nikitiuk commented on PDB-722 Re: PuppetDB response hanging on select-nodes subquery Created PR-1165 for the issue described in the comment above. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1040) PR (153): Fix ssl_protocols - bastelfreak
Title: Message Title gepetto-bot commented on PDB-1040 Re: PR (153): Fix ssl_protocols - bastelfreak bastelfreak commented: fixed the broken commits from yesterday, added a note to the README.md Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3718) defined function does not handle qualified variable names correctly
Title: Message Title Henrik Lindberg commented on PUP-3718 Re: defined function does not handle qualified variable names correctly This is especially bad for users that want to turn on strict_variables and do manual checking. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3718) defined function does not handle qualified variable names correctly
Title: Message Title
Henrik Lindberg created an issue
Puppet / PUP-3718
defined function does not handle qualified variable names correctly
Issue Type:
Bug
Assignee:
Unassigned
Components:
DSL
Created:
2014/11/27 4:18 PM
Fix Versions:
PUP 4.0.0
Priority:
Normal
Reporter:
Henrik Lindberg
The defined function can answer if a variable is defined. If the variable name contains '::' it always returns false even if variable is defined.
$x = 10
notice defined('$::x')
Jira (PUP-3718) defined function does not handle qualified variable names correctly
Title: Message Title Henrik Lindberg commented on PUP-3718 Re: defined function does not handle qualified variable names correctly Note that simple tests that use scopes and topscope must wire them to mock that there is a topscope named '' (empty string), or a complete integration test is needed (to get a complete and correct set-up). (And in case you wonder, yes, the scope implementation is magnificently horrific). Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3204) Users and groups created mid-transaction are not found
Title: Message Title sauce commented on PUP-3204 Re: Users and groups created mid-transaction are not found Here is my workaround: https://github.com/nixmore/chown_winbind_homedirs.sh Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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.
