Jira (PUP-3727) Notify: provide a way to log only the message itself at 'notice' level
Title: Message Title Nacho Barrientos created an issue Puppet / PUP-3727 Notify: provide a way to log only the message itself at 'notice' level Issue Type: Improvement Assignee: Unassigned Created: 2014/12/03 12:40 AM Priority: Minor Reporter: Nacho Barrientos Hi, I've already asked in the users' mailing list but judging from the number of responses I got it seems that what I want to do is not possible so please consider this a very low priority feature request. Of course, feel free to shut this as won't fix if there's indeed a way to do it When using the Notify resource type, is there any way to hide the log message that is produced by the definition itself and only keep the actual message string on the output generated by Puppet agent? In this example: Notice: hello Notice: /Stage[main]/Foo::Bar/Notify[baz]/message: defined 'message' as 'hello' The idea would be to tell Puppet somehow to only print the following: Notice: hello We've tried passing "audit => []" as an attribute to the resource declaration but it didn't produce any effect log-wise. Also we changed the loglevel to 'debug' at resource level and it hid both. We're (still) using Puppet 3.4.3 so maybe there's something available to cover this use case in newer versions. Thanks in advance
Jira (PDB-1046) PR (155): Show scheme (http/https) in puppetdb connection errors - sathieu
Title: Message Title gepetto-bot commented on PDB-1046 Re: PR (155): Show scheme (http/https) in puppetdb connection errors - sathieu sathieu commented: @kbarber : Oh sorry about that. I've fixed it and it now passes Travis. 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-1046) PR (155): Show scheme (http/https) in puppetdb connection errors - sathieu
Title: Message Title gepetto-bot commented on PDB-1046 Re: PR (155): Show scheme (http/https) in puppetdb connection errors - sathieu Pull request Show scheme (http/https) in puppetdb connection errors has been closed. 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-3728) Cron type uses incorrect month when month name is provided
Title: Message Title Ed Hargin created an issue Puppet / PUP-3728 Cron type uses incorrect month when month name is provided Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2014/12/03 4:59 AM Environment: RHEL 6.2 cronie-anacron-1.4.4-7.el6.x86_64 cronie-1.4.4-7.el6.x86_64 Priority: Normal Reporter: Ed Hargin {{ cron { 'demo cron job': command => 'echo test', user => 'root', hour => '1', minute => '0', month => 'December', monthday => ['3-15'], } }} This should create a cronjob like this: 0 1 3-15 12 * echo test Instead it creates a cronjob like this: 0 1 3-15 11 * echo test Note that this creates a cronjob for the 11th month, November, rather than the 12th. Cron counts months from 1-12, rather than 0-11. Each month appears to be month number minus 1. If you give it "January"
Jira (PUP-3728) Cron type uses incorrect month when month name is provided
Title: Message Title Ed Hargin updated an issue Puppet / PUP-3728 Cron type uses incorrect month when month name is provided Change By: Ed Hargin {{ cron { 'demo cron job':command => 'echo test',user => 'root',hour => '1',minute => '0',month=> 'December',monthday => ['3-15'],} }}This should create a cronjob like this:{{0 1 3-15 12 * echo test}}Instead it creates a cronjob like this:{{0 1 3-15 11 * echo test}}Note that this creates a cronjob for the 11th month, November, rather than the 12th. Cron counts months from 1-12, rather than 0-11.Each month appears to be month number minus 1.If you give it "January" as a month, you get an invalid cron entry, which is not created. 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-3728) Cron type uses incorrect month when month name is provided
Title: Message Title Ed Hargin updated an issue Puppet / PUP-3728 Cron type uses incorrect month when month name is provided Change By: Ed Hargin { { code:puppet} cron { 'demo cron job':command => 'echo test',user => 'root',hour => '1',minute => '0',month=> 'December',monthday => ['3-15'],} {code } } This should create a cronjob like this:{{0 1 3-15 12 * echo test}}Instead it creates a cronjob like this:{{0 1 3-15 11 * echo test}}Note that this creates a cronjob for the 11th month, November, rather than the 12th. Cron counts months from 1-12, rather than 0-11.Each month appears to be month number minus 1.If you give it "January" as a month, you get an invalid cron entry, which is not created. 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-3728) Cron type uses incorrect month when month name is provided
Title: Message Title Ed Hargin updated an issue Puppet / PUP-3728 Cron type uses incorrect month when month name is provided Change By: Ed Hargin {code:puppet} cron { 'demo cron job':command => 'echo test',user => 'root',hour => '1',minute => '0',month=> 'December',monthday => ['3-15'],} {code}This should create a cronjob like this:{{0 1 3-15 12 * echo test}}Instead it creates a cronjob like this:{{0 1 3-15 11 * echo test}}Note that this creates a cronjob for the 11th month, November, rather than the 12th. Cron counts months from 1-12, rather than 0-11. Each month Puppet appears to be create cronjobs with a month number minus 1 fewer than it should .If you give it "January" as a month, you get an invalid cron entry , which is not cannot be created. 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-3728) Cron type uses incorrect month when month name is provided
Title: Message Title Ed Hargin commented on PUP-3728 Re: Cron type uses incorrect month when month name is provided It should be noted that specifying the month as a number, e.g. December being 12, works as expected. 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-1048) puppetdb module creates inconsistent routes.yaml
Title: Message Title Kenneth Barber commented on PDB-1048 Re: puppetdb module creates inconsistent routes.yaml Its caused by the to_yaml call, I've seen it before, and its to do with Ruby's ordering specifically. YAML doesn't have ordering either, unless you use the OMAP type, which is tricky and doesn't translate to a format the Puppet master accepts. What version of Ruby is this specifically? 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-3729) Puppet package incorrectly starts service on install
Title: Message Title James Shubin created an issue Puppet / PUP-3729 Puppet package incorrectly starts service on install Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Unassigned Components: Puppet Server Created: 2014/12/03 5:46 AM Priority: Blocker Reporter: James Shubin The yum.puppetlabs rpm's contain the following: [root@puppet ~]# rpm -q --scripts puppet ... postinstall scriptlet (using /bin/sh): /bin/systemctl daemon-reload >/dev/null 2>&1 || : if [ "$1" -ge 1 ]; then The pidfile changed from 0.25.x to 2.6.x, handle upgrades without leaving the old process running. oldpid="/var/run/puppet/puppetd.pid" newpid="/var/run/puppet/agent.pid" if [ -s "$oldpid" -a ! -s "$newpid" ]; then (kill $(< "$oldpid") && rm -f "$oldpid" && \ /bin/systemctl start puppet.service) >/dev/null 2>&1 || : fi fi ... [root@puppet ~]# rpm -qi puppet Name : puppet Version : 3.7.3 Release : 1.el7
Jira (PUP-3729) Puppet package incorrectly starts service on install
Title: Message Title James Shubin commented on PUP-3729 Re: Puppet package incorrectly starts service on install FYI: The EPEL package does not do this. CC: vkaig...@redhat.com please. 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-1042) PR (1163): Fixes needed for running tests against puppet's master branch - senior
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1042 PR (1163): Fixes needed for running tests against puppet's master branch - senior Change By: Ryan Senior Story Points: 0 5 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-1049) Plan for AIO repackaging work
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1049 Plan for AIO repackaging work Change By: Kenneth Barber Sprint: PuppetDB 2014-12-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-1049) Plan for AIO repackaging work
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1049 Plan for AIO repackaging work Issue Type: Task Assignee: Unassigned Created: 2014/12/03 6:37 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Kenneth Barber This is all about planning for the AIO changes put forward by release: https://docs.google.com/a/puppetlabs.com/document/d/1rXVdBPxw64UXoShJ68SQUJpFbkfgGp2p5GRBkb6b6to/edit?disco=ANH_tp0 The goal of this ticket is to work out a plan, in particular how we are going to deal with a Puppet 4 & Puppet 3 world if we choose to be compatible with both, or making a decision about dropping Puppet 3 support if its too hard (worst case). The outcome should be a decision on how we move forward so release can go ahead, and creation of any tickets for us that we may need to work on to make this plan happen. /cc Moses Mendoza Matthaus Owens Add Comment
Jira (PDB-1048) puppetdb module creates inconsistent routes.yaml
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1048 puppetdb module creates inconsistent routes.yaml Change By: Kenneth Barber Story Points: 3 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-1037) Research i18n impacts to PuppetDB
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1037 Research i18n impacts to PuppetDB Change By: Kenneth Barber This task involves testing PuppetDB storage and querying only (not error messages or other things for now) to make sure of a few things:* PDB-480 is about the titles getting utf-8 characters being changed back to ascii, we need to confirm this* We need to confirm PE-1774, it looks like queries are getting UTF-8 issues and we should confirm this, and make sure we have UTF-8 based tests to either shake this up, or ensure we don't regress. This might require tests in a few different places.Any other functional tests that might come up in relation to storage should be done as well, although the work to fix them doesn't have to be done in this ticket. 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-1050) PuppetDB i18n Phase 1
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1050 PuppetDB i18n Phase 1 Issue Type: Epic Assignee: Unassigned Created: 2014/12/03 7:07 AM Priority: Normal Reporter: Kenneth Barber 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-1050) PuppetDB i18n Phase 1
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1050 PuppetDB i18n Phase 1 Change By: Kenneth Barber Epic Name: PuppetDB PDB i18n Phase 1 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: PuppetDB 2014-12- 17 31 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-698) Use underscores instead of dashes in responses
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-698 Use underscores instead of dashes in responses Change By: Kenneth Barber Sprint: PuppetDB 2014-12- 17 31 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-948) Java 8 Support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-948 Java 8 Support Change By: Kenneth Barber Sprint: PuppetDB 2014-12- 17 31 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-189) Retire JKS methodology
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-189 Retire JKS methodology Change By: Kenneth Barber Sprint: PuppetDB 2014-12- 17 31 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-1043) top-level extract should support short-hand query syntax, or at least throw a reasonable error
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1043 top-level extract should support short-hand query syntax, or at least throw a reasonable error Change By: Kenneth Barber Summary: top-level extract should support short-hand query syntax , or at least throw a reasonable error 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-1032) Ezbake: Get pe-puppetdb building with ezbake
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1032 Ezbake: Get pe-puppetdb building with ezbake Change By: Kenneth Barber Sprint: PuppetDB 2014-12- 17 31 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-1043) top-level extract should support short-hand query syntax, or at least throw a reasonable error
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1043 top-level extract should support short-hand query syntax, or at least throw a reasonable error Change By: Kenneth Barber Story Points: 3 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-1032) Ezbake: Get pe-puppetdb building with ezbake
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1032 Ezbake: Get pe-puppetdb building with ezbake Change By: Kenneth Barber Story Points: 5 2 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-695) Retire v2 & v3 API
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-695 Retire v2 & v3 API Change By: Kenneth Barber Story Points: 2 5 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-1033) Ezbake: fix downstream, make sure they can build our packages in an ezbake world
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1033 Ezbake: fix downstream, make sure they can build our packages in an ezbake world Change By: Kenneth Barber Story Points: 5 2 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-1043) top-level extract should support short-hand query syntax, or at least throw a reasonable error
Title: Message Title Andrii Nikitiuk commented on PDB-1043 Re: top-level extract should support short-hand query syntax, or at least throw a reasonable error I implemented a validation for the examples described here locally. May I assign this ticket to myself? 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-841) Retire (or at least consider retiring) the storeconfigs export tool
Title: Message Title Kenneth Barber commented on PDB-841 Re: Retire (or at least consider retiring) the storeconfigs export tool This might be fixed with PDB-1042. 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-1033) Ezbake: fix downstream, make sure they can build our packages in an ezbake world
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1033 Ezbake: fix downstream, make sure they can build our packages in an ezbake world Change By: Kenneth Barber Sprint: PuppetDB 2014-12- 17 31 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-991) Dujour needs updating to latest, but latest package is broken
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-991 Dujour needs updating to latest, but latest package is broken Change By: Kenneth Barber Story Points: 3 1 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-695) Retire v2 & v3 API
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-695 Retire v2 & v3 API Change By: Kenneth Barber Sprint: PuppetDB 2014-12- 17 31 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-775) Retire pre 9.2 postgresql databases
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-775 Retire pre 9.2 postgresql databases Change By: Kenneth Barber Sprint: PuppetDB 2014-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-800) Move /metric endpoint to prepare for modularization
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-800 Move /metric endpoint to prepare for modularization Change By: Kenneth Barber Sprint: PuppetDB 2014-12- 17 31 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-775) Retire pre 9.2 postgresql databases
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-775 Retire pre 9.2 postgresql databases Change By: Kenneth Barber Sprint: PuppetDB 2014-12- 31 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-644) Retire node-ttl-days
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-644 Retire node-ttl-days Change By: Kenneth Barber Sprint: PuppetDB 2015 2014 - 01 12 - 14 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-1043) top-level extract should support short-hand query syntax, or at least throw a reasonable error
Title: Message Title Kenneth Barber commented on PDB-1043 Re: top-level extract should support short-hand query syntax, or at least throw a reasonable error Sure go ahead . 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-1043) top-level extract should support short-hand query syntax, or at least throw a reasonable error
Title: Message Title Andrii Nikitiuk assigned an issue to Andrii Nikitiuk PuppetDB / PDB-1043 top-level extract should support short-hand query syntax, or at least throw a reasonable error Change By: Andrii Nikitiuk Assignee: Andrii Nikitiuk 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-1024) Add support for classes with hyphens in the name
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1024 Add support for classes with hyphens in the name Change By: Steve Barlow Sprint: PuppetDB 2014-11-19, PuppetDB 2014-12-03 , PuppetDB 2014-12-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-1009) Setup Travis PR tests for puppetdb-sync
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1009 Setup Travis PR tests for puppetdb-sync Change By: Steve Barlow Sprint: PuppetDB 2014-12-03 , PuppetDB 2014-12-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-1028) make catalogs queryable
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1028 make catalogs queryable Change By: Steve Barlow Sprint: PuppetDB 2014-11-19, PuppetDB 2014-12-03 , PuppetDB 2014-12-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-722) PuppetDB response hanging on select-nodes subquery
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-722 PuppetDB response hanging on select-nodes subquery Change By: Steve Barlow Sprint: PuppetDB 2014-12-03 , PuppetDB 2014-12-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-863) Fix JMX & MQ endpoints to use new puppetlabs.puppetdb namespace
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-863 Fix JMX & MQ endpoints to use new puppetlabs.puppetdb namespace Change By: Steve Barlow Sprint: PuppetDB 2014-12-03 , PuppetDB 2014-12-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-1034) Ezbake: switch source based tests to use ezbake somehow and retire that old code
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1034 Ezbake: switch source based tests to use ezbake somehow and retire that old code Change By: Steve Barlow Sprint: PuppetDB 2014-12-03 , PuppetDB 2014-12-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-950) PuppetDB returns 500 error as HTML when query contains invalid regex
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-950 PuppetDB returns 500 error as HTML when query contains invalid regex Change By: Steve Barlow Sprint: PuppetDB 2014-11-19, PuppetDB 2014-12-03 , PuppetDB 2014-12-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-1042) PR (1163): Fixes needed for running tests against puppet's master branch - senior
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1042 PR (1163): Fixes needed for running tests against puppet's master branch - senior Change By: Steve Barlow Sprint: PuppetDB 2014-12-03 , PuppetDB 2014-12-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-885) PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-885 PR (1087): Add VPC support for acceptance test hosts for PuppetDB - kbarber Change By: Steve Barlow Sprint: PuppetDB 2014-09-24, PuppetDB 2014-10-08, PuppetDB 2014-10-22, PuppetDB 2014-11-05, PuppetDB 2014-11-19, PuppetDB 2014-12-03 , PuppetDB 2014-12-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 (PUP-3644) move all legacy and v2.0 endpoints to v3
Title: Message Title Christopher Price commented on PUP-3644 Re: move all legacy and v2.0 endpoints to v3 Eric Sorenson any thoughts? Henrik's point is valid, and I'd be fine either way. 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-3526) re-structure CA REST API
Title: Message Title Christopher Price commented on PUP-3526 Re: re-structure CA REST API 'puppet-ca' is a good suggestion. I'll make that the default. 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-3644) move all legacy and v2.0 endpoints to v3
Title: Message Title Christopher Price commented on PUP-3644 Re: move all legacy and v2.0 endpoints to v3 Patrick Carlisle I'm assuming that this won't affect you guys too much either way? Not a big deal to change the classifier to use a new URL namespace? 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-1009) Setup Travis PR tests for puppetdb-sync
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1009 Setup Travis PR tests for puppetdb-sync Change By: Steve Barlow Sprint: PuppetDB 2014-12-03, PuppetDB 2014-12- 17 31 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-1049) Plan for AIO repackaging work
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1049 Plan for AIO repackaging work Change By: Steve Barlow Sprint: PuppetDB 2014-12- 17 31 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-3471) Windows Puppet x86 Installer Expands Environment Variables in Path
Title: Message Title Chun Du commented on PUP-3471 Re: Windows Puppet x86 Installer Expands Environment Variables in Path +1 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-3728) Cron type uses incorrect month when month name is provided
Title: Message Title Charlie Sharpsteen commented on PUP-3728 Re: Cron type uses incorrect month when month name is provided This behavior stems from the use of an array of strings against which the alphabetic value is matched to generate a numeric index: def alpha %w{january february march april may june july august september october november december} end The problem is that this method assumes 0 based indexing in the output range. The easiest fix is probably to add a "null" value to the beginning of the array so that the months indices are shifted up by one value. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PDB-1024) Add support for classes with hyphens in the name
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1024 Add support for classes with hyphens in the name Change By: Kenneth Barber Fix Version/s: PDB 2.2.x 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-991) Dujour needs updating to latest, but latest package is broken
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-991 Dujour needs updating to latest, but latest package is broken Change By: Kenneth Barber Affects Version/s: PDB 2.2.2 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-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 Kenneth Barber 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: Kenneth Barber Fix Version/s: PDB 2.2.x 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-3729) Puppet package incorrectly starts service on install
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3729 Puppet package incorrectly starts service on install Change By: Charlie Sharpsteen The yum.puppetlabs rpm's contain the following: {noformat} [root@puppet ~]# rpm -q --scripts puppet...postinstall scriptlet (using /bin/sh):/bin/systemctl daemon-reload >/dev/null 2>&1 || :if [ "$1" -ge 1 ]; then # The pidfile changed from 0.25.x to 2.6.x, handle upgrades without leaving # the old process running. oldpid="/var/run/puppet/puppetd.pid" newpid="/var/run/puppet/agent.pid" if [ -s "$oldpid" -a ! -s "$newpid" ]; then(kill $(< "$oldpid") && rm -f "$oldpid" && \ /bin/systemctl start puppet.service) >/dev/null 2>&1 || : fifi...[root@puppet ~]# rpm -qi puppet Name: puppetVersion : 3.7.3Release : 1.el7 {noformat} Starting the service automatically on install is causing lots of issues. It should not because you have not had a chance to set config files first for example. This is a common packaging guideline. One kitten was killed accidentally due to this.Reported by @br0zilly (GitHub) 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.co
Jira (PUP-3471) Windows Puppet x86 Installer Expands Environment Variables in Path
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3471 Windows Puppet x86 Installer Expands Environment Variables in Path Change By: Rob Reynolds Component/s: PE 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-3469) fix zpool tests on solaris10
Title: Message Title Michael Smith commented on PUP-3469 Re: fix zpool tests on solaris10 Does this also block PUP-3057? 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-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-2927 Facter logs should be surfaced during Puppet runs Change By: Michael Smith Assignee: Michael Smith 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-3469) fix zpool tests on solaris10
Title: Message Title Eric Thompson commented on PUP-3469 Re: fix zpool tests on solaris10 Michael Smith good question. no, it shouldn't. these tests were previously skipped on sol10 for one of the PRs against PUP-3057 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-3630) Odd behavior with noop
Title: Message Title Charlie Sharpsteen commented on PUP-3630 Re: Odd behavior with noop A minimum re-production case for this behavior consists of a defined type and a class which declares a noop resource of that time type: # atype.pp define noop_test::atype( $content_string = 'some content', ) { file{"/tmp/$title": ensure => file, content => $content_string, } }
Jira (PUP-3630) The compiler does not process metaparameters for resources declared outside of Class[main]
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3630 The compiler does not process metaparameters for resources declared outside of Class[main] Change By: Charlie Sharpsteen Summary: Odd behavior with noop The compiler does not process metaparameters for resources declared outside of Class[main] 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-3644) move all legacy and v2.0 endpoints to v3
Title: Message Title Patrick Carlisle commented on PUP-3644 Re: move all legacy and v2.0 endpoints to v3 Pretty easy. I'm not sure if we have to care about backwards compatibility. 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-3630) The compiler does not process metaparameters for resources declared outside of Class[main]
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3630 The compiler does not process metaparameters for resources declared outside of Class[main] Change By: Charlie Sharpsteen Affects Version/s: PUP 3.7.3 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-3630) The compiler does not process metaparameters for resources declared outside of Class[main]
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3630 The compiler does not process metaparameters for resources declared outside of Class[main] Change By: Charlie Sharpsteen Component/s: DSL 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-3630) The compiler does not process metaparameters for resources declared outside of Class[main]
Title: Message Title Charlie Sharpsteen commented on PUP-3630 Re: The compiler does not process metaparameters for resources declared outside of Class[main] Eric Sorenson, Henrik Lindberg: The fix for this one seems fairly simple, but has a far-ranging impact. Walking containment graphs rooted at stages and applying metaparameters enables what seems to be the correct behavior for defined types. However, this will also affect metaparameters declared on parameterized classes, which is something we have rejected in the past. With the change in compiler behavior, the following metaparameters would become inheritable for all classes and defined types: Puppet::Type.metaparams.select do |name| !Puppet::Parser::Resource.relationship_parameter?(name) end => [:noop, :schedule, :audit, :loglevel, :alias, :tag, :stage] Currently, these metaparameters are inherited by all resources and defined types declared under Class[main] Add Comment
Jira (PUP-3282) Remove support for method access of variables in ERB templates
Title: Message Title Hailee Kenney commented on PUP-3282 Re: Remove support for method access of variables in ERB templates Merged into master in be414eb 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-1971) puppet apply --debug does not provide stdout and stderr log of puppet exec
Title: Message Title Michael Smith commented on PUP-1971 Re: puppet apply --debug does not provide stdout and stderr log of puppet exec The exec type has an option `logoutput` that will display output: https://docs.puppetlabs.com/references/latest/type.html#exec-attribute-logoutput When I run ` exec { test: command => "/bin/echo hello; exit 0", logoutput => true } Notice: Compiled catalog for michaels-macbook-pro.local in environment production in 0.34 seconds Notice: /Stage[main]/Main/Exec[test]/returns: hello Notice: /Stage[main]/Main/Exec[test]/returns: executed successfully Notice: Applied catalog in 0.03 seconds ` 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-3680) The parameter order on the hash type is inconsistent
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-3680 The parameter order on the hash type is inconsistent Change By: Hailee Kenney Assignee: Hailee Kenney 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-1042) PR (1163): Fixes needed for running tests against puppet's master branch - senior
Title: Message Title gepetto-bot commented on PDB-1042 Re: PR (1163): Fixes needed for running tests against puppet's master branch - senior pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/261/ 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-3630) The compiler does not process metaparameters for resources declared outside of Class[main]
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3630 The compiler does not process metaparameters for resources declared outside of Class[main] Change By: Charlie Sharpsteen Assignee: Henrik Lindberg 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-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Michael Smith commented on PUP-2927 Re: Facter logs should be surfaced during Puppet runs Tried various combinations of custom facts Facter.add('test') do setcode do 'foo' end end Facter.add('err') do setcode do raise "Because I can" end end
Jira (PUP-2927) Facter logs should be surfaced during Puppet runs
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet / PUP-2927 Facter logs should be surfaced during Puppet runs Change By: Michael Smith Assignee: Michael Smith 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-1042) PR (1163): Fixes needed for running tests against puppet's master branch - senior
Title: Message Title gepetto-bot commented on PDB-1042 Re: PR (1163): Fixes needed for running tests against puppet's master branch - senior pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/262/ 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-3730) Changing a variable in a custom fact, after the fact changes the earlier set fact
Title: Message Title redmine.exporter created an issue Puppet / PUP-3730 Changing a variable in a custom fact, after the fact changes the earlier set fact Issue Type: Bug Assignee: Unassigned Created: 2014/12/03 12:11 PM Labels: redmine Priority: Normal Reporter: redmine.exporter Okay, I think I've totally earned my keep on this one. I was hitting an unbelievable condition while hacking on https://github.com/purpleidea/puppet-gluster cough, plug, and after a lot of head scratching I narrowed it down. I've come up with a demonstration test case/example. Look at the following fact: XXX: demonstrate a surprising bug in puppet/facter require 'facter' value = 'hello' Facter.add('foo') do setcode { value } end thing = {} thing['a'] = 'puppet' thing['b'] = 'works' thing.keys.each do |x| value = thing[x] Facter.add('foo_'+x) do setcode { value # bork # Facter::Util::Resolution.exec("/bin/echo -n '"+value+"'") # bork! # thing[x] # works as expected } end end value = 'BROKEN' # shouldn't matter The issue is that if you use a variable
Jira (PUP-3731) Accessing arguments in exported resource collection override for override.
Title: Message Title redmine.exporter created an issue Puppet / PUP-3731 Accessing arguments in exported resource collection override for override. Issue Type: New Feature Assignee: Unassigned Created: 2014/12/03 12:14 PM Labels: redmine Priority: Normal Reporter: redmine.exporter Sorry I don't know how to name the subject any better... I came up with something which would be particularly useful for advanced puppet users, which I don't think exists at the moment. If it does, please let me know, if not, then consider this a feature request! Given: @@foo::bar { 'some_name': value => 'hello', thing => 'world', tag => 'mytag', } and (on a different machine): I'd like to be able to access the properties of the element being created, for use in it's override block... Here is a very contrived example, I've made up a fake syntax of round brackets: $(thing) to show where i am using a variable from the object. This could be sort of like regexp conditional capture variables, but named... Foo::Bar <<| tag == 'mytag' |>> { value => "override", thing => $(value) ? { # $(value) should be one of the arguments 'world' => 'Earth', 'baz' => "$(name)", # here we're using the name this define has... 'yeah' => "$(tag)", # or maybe we want a property like tag default => "$(thing)-whatever", # here's another example, but this time with $thing }
Jira (PUP-3732) type validation should rot run for `puppet resource`
Title: Message Title Hunter Haugen created an issue Puppet / PUP-3732 type validation should rot run for `puppet resource` Issue Type: Bug Assignee: Unassigned Created: 2014/12/03 12:41 PM Priority: Normal Reporter: Hunter Haugen tl;dr: puppet resource creates resource types without attributes, which causes the type's global validate block to fail. It should initialize the type with values from the provider so that it can be validated. Puppet types can have per-parameter or per-property validate blocks, but can also have a global validate block. Oddly, when running puppet resource the per-attribute validates are not called (as no attributes are passed), but the global validate is. Validation is usually done on the resource coming from the catalog, which is self in the context of the global validate. When using puppet resource there is no true catalog per-say, but if no arguments are passed then the resource types @parameter hash is not initialized and thus validation will fail. If the @parameter hash was merged with the values from self.provider's @property_hash then the global validation block would still be validating any values that were passed on the command-line, or just the values returned by self.instances if there are no arguments. This *should* still work for normal catalog application, as a resource returned by self.instances and thus passing global validation is already configured correctly.
Jira (PUP-2628) Ability to add a member to a group, instead of specifying the complete list
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-2628 Ability to add a member to a group, instead of specifying the complete list Change By: Eric Thompson Assignee: Eric Thompson 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-3730) Changing a variable in a custom fact, after the fact changes the earlier set fact
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3730 Changing a variable in a custom fact, after the fact changes the earlier set fact Change By: Josh Cooper Okay, I think I've totally earned my keep on this one. I was hitting an unbelievable condition while hacking on https://github.com/purpleidea/puppet-gluster *cough, plug*, and after a lot of head scratching I narrowed it down. I've come up with a demonstration test case/example. Look at the following fact: {code:ruby} # XXX: demonstrate a surprising bug in puppet/facterrequire 'facter'value = 'hello'Facter.add('foo') do setcode {value }endthing = {}thing['a'] = 'puppet'thing['b'] = 'works'thing.keys.each do |x| value = thing[x] Facter.add('foo_'+x) dosetcode { value # bork # Facter::Util::Resolution.exec("/bin/echo -n '"+value+"'") # bork! # thing[x] # works as expected} endendvalue = 'BROKEN' # shouldn't matter {code} The issue is that if you use a variable in the setcode block, that variable *cannot* be changed without changing the earlier set value! In other words, you would expect: {noformat} $ facter -p | grep foofoo => hellofoo_a => puppetfoo_b => works {noformat} but you actually get: {noformat} $ facter -p | grep foofoo => BROKENfoo_a => BROKENfoo_b => BROKEN {noformat} FWIW: {noformat} $ puppet --version3.2.4$ facter --version1.7.2 {noformat} The workaround is to not reuse variables, and if you're creating facts in a loop, you have to do it in two steps, firstly create a dictionary of the fact names/values you want as a result, and then loop through that setting the facts.The big issue is that this is highly unexpected in ruby code, and at best is not a documented gotcha. You can uncomment the various parts of my example to try different variations.If this was an awesome catch, I guess I'd like some cool twitter followers @purpleidea or something :PCheers,James Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (FACT-764) Changing a variable in a custom fact, after the fact changes the earlier set fact
Title: Message Title Josh Cooper commented on FACT-764 Re: Changing a variable in a custom fact, after the fact changes the earlier set fact Moved to facter project 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 (FACT-764) Changing a variable in a custom fact, after the fact changes the earlier set fact
Title: Message Title Josh Cooper moved an issue Facter / FACT-764 Changing a variable in a custom fact, after the fact changes the earlier set fact Change By: Josh Cooper Key: PUP FACT - 3730 764 Project: Puppet Facter 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-1042) PR (1163): Fixes needed for running tests against puppet's master branch - senior
Title: Message Title gepetto-bot commented on PDB-1042 Re: PR (1163): Fixes needed for running tests against puppet's master branch - senior senior commented: @hlindberg BTW I had to remove the puppet feature stuff as it isn't working for me. I think it's a load order sort of issue, it was breaking our acceptance tests, moving that method from a feature to just a plain utility method fixed the issue. 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-3733) "Not for Distribution" distracting
Title: Message Title Verne Lindner created an issue Puppet / PUP-3733 "Not for Distribution" distracting Issue Type: Improvement Assignee: Unassigned Created: 2014/12/03 1:26 PM Priority: Normal Reporter: Verne Lindner As a trainee in the Puppet Fundamentals class, I want to be able to read the training manual, without being distracted by the legend "NOT FOR DISTRIBUTION" on every page, in order to be able to more easily focus on the content itself. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PUP-3521) puppet incorrectly swallows some errors
Title: Message Title Rajasree Talla updated an issue Puppet / PUP-3521 puppet incorrectly swallows some errors Change By: Rajasree Talla Sprint: SERVER 2014-11-19, SERVER 2014-12-03 , SERVER 2014-12-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 (PUP-3520) Move the Puppet extension OIDs definitions
Title: Message Title Rajasree Talla updated an issue Puppet / PUP-3520 Move the Puppet extension OIDs definitions Change By: Rajasree Talla Sprint: SERVER 2014-11-19, SERVER 2014-12-03 , SERVER 2014-12-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 (PUP-3560) Add support for properly signed trusted facts
Title: Message Title Rajasree Talla updated an issue Puppet / PUP-3560 Add support for properly signed trusted facts Change By: Rajasree Talla Sprint: SERVER 2014-11-19, SERVER 2014-12-03 , SERVER 2014-12-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-1042) PR (1163): Fixes needed for running tests against puppet's master branch - senior
Title: Message Title gepetto-bot commented on PDB-1042 Re: PR (1163): Fixes needed for running tests against puppet's master branch - senior pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/263/ 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-3282) Remove support for method access of variables in ERB templates
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-3282 Remove support for method access of variables in ERB templates Change By: Hailee Kenney Assignee: Hailee Kenney 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-3734) Provide MSI Property to configure `masterport` setting
Title: Message Title Rob Reynolds created an issue Puppet / PUP-3734 Provide MSI Property to configure `masterport` setting Issue Type: Improvement Assignee: Aaron Armstrong Components: PE, RE Created: 2014/12/03 1:47 PM Fix Versions: PUP 4.x Labels: windows Priority: Normal Reporter: Rob Reynolds Currently the MSI that installs the PE agent for Windows lacks an MSI property to configure the masterport setting during the install process. This makes life difficult for those who have their master running on an alternate port, as it requires them to do additional configuration of their agent after the agent has been installed. It would be very helpful to those who must run their master on an alternate port, if we provided an MSI property that allowed you to configure this.
Jira (PUP-3734) Provide MSI Property to configure `masterport` setting
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-3734 Provide MSI Property to configure `masterport` setting Change By: Rob Reynolds Assignee: Aaron Armstrong 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-2628) Ability to add a member to a group, instead of specifying the complete list
Title: Message Title Eric Thompson commented on PUP-2628 Re: Ability to add a member to a group, instead of specifying the complete list doesn't seem to work, but i'm probably doing it wrong... win2012r2-r64 at SHA: with: Administrator@hrhpevl49f3bmi8 ~ $ env PATH="$( [ -d "/cygdrive/c/Program Files (x86)/Puppet Labs/Puppet/bin" ] & & echo "/cygdrive/c/Program Files (x86)" || echo "/cygdrive/c/Program Files" )/P uppet Labs/Puppet/bin:/opt/puppet-git-repos/hiera/bin:${PATH}" RUBYLIB="`cygpath-w /opt/puppet-git-repos/hiera/lib`;`cygpath -w /opt/puppet-git-repos/hiera-pup pet/lib`;${RUBYLIB}" cmd.exe /c puppet apply -e 'group{ "Power Users": members= >"sshd"}' Notice: Compiled catalog for hrhpevl49f3bmi8.delivery.puppetlabs.net in environm ent production in 0.64 seconds Notice: /Stage[main]/Main/Group[Power Users]/members: members changed '' to 'HRH PEVL49F3BMI8\sshd' Notice: Applied catalog in 0.03 seconds Administrator@hrhpevl49f3bmi8 ~ $ env PATH="$( [ -d "/cygdrive/c/Program Files (x86)/Puppet Labs/Puppet/bin" ] & & echo "/cygdrive/c/Program Files (x86)" || echo "/cygdrive/c/Program Files" )/P uppet Labs/Pupp
Jira (PUP-2628) Ability to add a member to a group, instead of specifying the complete list
Title: Message Title Josh Cooper commented on PUP-2628 Re: Ability to add a member to a group, instead of specifying the complete list > do I have to turn off auth_membership? Yep, currently puppet will assume you've specified the complete list. We do want to switch that behavior, but that's PUP-3719, still to be implemented. 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-2628) Ability to add a member to a group, instead of specifying the complete list
Title: Message Title Eric Thompson commented on PUP-2628 Re: Ability to add a member to a group, instead of specifying the complete list thanks, Josh. edited my comment above. resolving... 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-3549) Debian init script status and stop actions are unsafe
Title: Message Title Peter Huene updated an issue Puppet / PUP-3549 Debian init script status and stop actions are unsafe Change By: Peter Huene Component/s: Community 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-2628) Ability to add a member to a group, instead of specifying the complete list
Title: Message Title Eric Thompson updated an issue Puppet / PUP-2628 Ability to add a member to a group, instead of specifying the complete list Change By: Eric Thompson QA Contact: Narmadha Perumal Eric Thompson QA Status: Reviewed 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-2628) Ability to add a member to a group, instead of specifying the complete list
Title: Message Title Eric Thompson commented on PUP-2628 Re: Ability to add a member to a group, instead of specifying the complete list specs in windows_adsi_spec.rb appear to mock the provider. are there other specs that i missed? looks to me that we should add some acceptance for group providers, for managing users. opinions? 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-3282) Remove support for method access of variables in ERB templates
Title: Message Title Josh Cooper commented on PUP-3282 Re: Remove support for method access of variables in ERB templates Acceptance test updated in a239da88 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.