Jira (PUP-4050) Acceptance suite and install.rb use incorrect paths on Windows for codedir
Title: Message Title Josh Cooper commented on PUP-4050 Re: Acceptance suite and install.rb use incorrect paths on Windows for codedir Merged in 169e994 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3043) 100% CPU usage
Title: Message Title Aaron Hicks commented on PUP-3043 Re: 100% CPU usage ...could it be when reporting is on, and the agent is compiling the report for submission? here's my agent's puppet.conf: ``` [main] logdir = /var/log/puppet vardir = /var/lib/puppet ssldir = /var/lib/puppet/ssl rundir = /var/run/puppet factpath = $vardir/lib/facter:$vardir/facts server = puppet The class puppet::hiera creates a minimal hiera config to suppress warnings. hiera_config = /etc/puppet/hiera.yaml These are set by the puppet base class when the puppet agent is running [agent] environment = production report = true pluginsync = true ``` Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3043) 100% CPU usage
Title: Message Title Aaron Hicks commented on PUP-3043 Re: 100% CPU usage I'm observing similar behavior in Puppet 3.7.4 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1635) "current thread not owner" after Puppet Agent receives USR1 signal
Title: Message Title John Duarte commented on PUP-1635 Re: "current thread not owner" after Puppet Agent receives USR1 signal Verified with puppet-agent-0.3.2.90.gc5e3bb3-1 on RHEL 7. Install Puppet server Add `puppet` alias to master in /etc/hosts Install and start puppetserver on master node curl -O http://builds.puppetlabs.lan/puppet-agent/c5e3bb3384ba87507711dd2a2d70102e185388e5/artifacts/el/7/products/x86_64/puppet-agent-0.3.2.90.gc5e3bb-1.el7.x86_64.rpm curl -O http://nightlies.puppetlabs.com/puppetserver/2.0.0.SNAPSHOT.2015.02.25T1428/repos/el/7/products/x86_64/puppetserver-2.0.0.SNAPSHOT.2015.02.25T1428-1.el7.noarch.rpm rpm -ivh puppet-agent-0.3.2.90.gc5e3bb3-1.el7.x86_64.rpm yum -y install java-1.7.0-openjdk yum -y install net-tools rpm -ivh puppetserver-2.0.0.SNAPSHOT.2015.02.25T1428-1.el7.noarch.rpm systemctl enable puppetserver systemctl restart puppetserver
Jira (PUP-3997) Audit and update puppet acceptance tests that assume the puppet user and group are present
Title: Message Title John Duarte commented on PUP-3997 Re: Audit and update puppet acceptance tests that assume the puppet user and group are present PR 3659 submitted for review. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3889) Fix puppet agent writing source to file when using non-md5 checksum type
Title: Message Title Felix Frank commented on PUP-3889 Re: Fix puppet agent writing source to file when using non-md5 checksum type Oh I see. Thanks for clearing this up. I guess it's fine - if you know how to read the tickets, it's reasonably simple to locate commits towards the subtasks. After all, there was no one branch to solve the encompassing task. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3889) Fix puppet agent writing source to file when using non-md5 checksum type
Title: Message Title Michael Smith commented on PUP-3889 Re: Fix puppet agent writing source to file when using non-md5 checksum type Maybe we should refine our contribution guidelines for subtasks to include the main task number as well. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3889) Fix puppet agent writing source to file when using non-md5 checksum type
Title: Message Title Michael Smith commented on PUP-3889 Re: Fix puppet agent writing source to file when using non-md5 checksum type This is a sub-task of PUP-1208 . That should be visible above the summary, and in the Subtasks section of PUP-1208 . Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3889) Fix puppet agent writing source to file when using non-md5 checksum type
Title: Message Title Felix Frank commented on PUP-3889 Re: Fix puppet agent writing source to file when using non-md5 checksum type Was this a duplicate of PUP-1208 ? I'm quite confused, for that one has been marked resolved as well, but I can find no commit that references it. There is also no reference to this ticket, either. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4047) consider 'non productive expression' to be warning
Title: Message Title James Sweeny commented on PUP-4047 Re: consider 'non productive _expression_' to be warning In cases like that, would it make more sense to warn that there's a space between the variable and the array operator? If you Google "non-productive (construct|_expression_)" the only results are puppet-related, so it's not a very user-friendly warning. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4047) consider 'non productive expression' to be warning
Title: Message Title Henrik Lindberg commented on PUP-4047 Re: consider 'non productive _expression_' to be warning Yes, you are right, one example is that space between an _expression_/variable and [] now is significant. $a [3] This leads to a non productive error for $a, since the logic above means, "produce the value of $a", then "produce an array with the value 3 in it". The non productive error helps users that have written code that way. It would otherwise go undetected. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3296) Remove handling and mention of :before and :after for parameters
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-3296
Remove handling and mention of :before and :after for parameters
Change By:
Nicholas Fagerlund
{{Puppet::Resource::ValueCollection}} and {{Puppet::Property}} both mention using {{:before}} and {{:after}} but that is hasn't been supported for years. We need to remove the mention of it and any code that is trying to handle it, even if only to error. There might be simplifications that can be done because of this (the comments seem to indicate this). For docs - this was probably only an internal affair as the removed capability was probably not mentioned in any user documentation from puppet labs.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3296) Remove handling and mention of :before and :after for parameters
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3296 Remove handling and mention of :before and :after for parameters Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3296) Remove handling and mention of :before and :after for parameters
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3296 Remove handling and mention of :before and :after for parameters Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4047) consider 'non productive expression' to be warning
Title: Message Title James Sweeny commented on PUP-4047 Re: consider 'non productive _expression_' to be warning Thanks for opening this Henrik Lindberg. In my opinion, we shouldn't even warn in cases like the example above, since there's absolutely nothing functionally wrong with the code from a user's perspective. If it's a style concern, I would rather this be in a linter than squawking during every compile (similar to having variables within single quotes). That said, there are probably other examples you can think of where this kind of warning/error would actually prevent something unexpected from happening, so it might just be something we have to get more specific about. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-346) Gemfile is outdated
Title: Message Title Matthaus Owens assigned an issue to Eric Sorenson Hiera / HI-346 Gemfile is outdated Change By: Matthaus Owens Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4052) puppet module generate uses invalid default license identifier
Title: Message Title Kylo Ginsberg commented on PUP-4052 Re: puppet module generate uses invalid default license identifier I believe this is a dup of PUP-3894 , so closing. Please reopen if that's not the case! Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4001) Packaging should create default module directories for puppet
Title: Message Title Melissa Stone commented on PUP-4001 Re: Packaging should create default module directories for puppet This was merged in at https://github.com/puppetlabs/puppet-agent/commit/272efd2ef821fe120da848a0b02f7e5d2888a5ce Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3986) Expand predefined OID's for Puppet's extension attributes
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-3986 Expand predefined OID's for Puppet's extension attributes Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-334) fix reference to deep merge gem
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-334 fix reference to deep merge gem Change By: Henrik Lindberg Sprint: Language 2015-03-18 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4052) puppet module generate uses invalid default license identifier
Title: Message Title Robin Bowes created an issue Puppet / PUP-4052 puppet module generate uses invalid default license identifier Issue Type: Bug Affects Versions: PUP 3.7.4 Assignee: Kylo Ginsberg Components: Client Created: 2015/02/26 3:54 PM Priority: Normal Reporter: Robin Bowes The default suggested license is "Apache 2.0". This is not a valid license identifier as per http://spdx.org/licenses/ I'm using garethr's module skeleton as the base for my module(s) and when I run "bundle exec rake test", this is the error I see: metadata-json-lint metadata.json Warning: License identifier Apache 2.0 is not in the SPDX list: http://spdx.org/licenses/
Jira (PUP-4047) consider 'non productive expression' to be warning
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4047 consider 'non productive _expression_' to be warning Change By: Henrik Lindberg Sprint: Language 2015-03-18 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3630) The compiler does not process metaparameter inheritance for resources declared outside of Class[main]
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-3630 The compiler does not process metaparameter inheritance for resources declared outside of Class[main] Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3986) Expand predefined OID's for Puppet's extension attributes
Title: Message Title Eric Thompson commented on PUP-3986 Re: Expand predefined OID's for Puppet's extension attributes stymied by my lack of knowledge on certificate passing, i can't get these into trusted data. i CAN get them to show up in the CSR on the master [root@mwt45b6l1dt19fi ssl]# openssl req -noout -text -in /etc/puppetlabs/puppet/ssl/certificate_requests/mwt45b6l1dt19fi.delivery.puppetlabs.net.pem Certificate Request: [blah] c1:ad:71 Exponent: 65537 (0x10001) Attributes: 1.3.6.1.4.1.34380.1.1.42 :fake OID name 1.3.6.1.4.1.34380.1.1.5 :my cost center name challengePassword:342thbjkt82094y0uthhor289jnqthpc2290 Signature Algorithm: sha256WithRSAEncryptio
Jira (PUP-3296) Remove handling and mention of :before and :after for parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3296 Remove handling and mention of :before and :after for parameters Change By: Henrik Lindberg Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3296) Remove handling and mention of :before and :after for parameters
Title: Message Title Henrik Lindberg commented on PUP-3296 Re: Remove handling and mention of :before and :after for parameters merged to master at: cfda9c9 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3296) Remove handling and mention of :before and :after for parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3296 Remove handling and mention of :before and :after for parameters Change By: Henrik Lindberg Fix Version/s: PUP 4.1.0 Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1806) Varargs support for the new function API
Title: Message Title Henrik Lindberg commented on PUP-1806 Re: Varargs support for the new function API merged to stable: c1135c5 and to master. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3986) Expand predefined OID's for Puppet's extension attributes
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3986 Expand predefined OID's for Puppet's extension attributes Change By: Eric Thompson Assignee: QA Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4051) Master unable to reliably reload puppet.conf
Title: Message Title Henrik Lindberg commented on PUP-4051 Re: Master unable to reliably reload puppet.conf We do not recommend using webrick for production nor any long running scenarios. It is not likely we will spend any more resources on webrick as the plan is to move to Puppet Server. Closing this as a won't fix. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1229) change reports to use schema and retire validation.clj
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1229 change reports to use schema and retire validation.clj Change By: Steve Barlow Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1258) PR (1281): (maint) Switch to different subnet-id for different availability zone - kbarber
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1258 PR (1281): (maint) Switch to different subnet-id for different availability zone - kbarber Change By: Steve Barlow Scrum Team: PuppetDB Scope Change Reason: PR Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1254) move latest_report to the certnames table
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1254 move latest_report to the certnames table Change By: Steve Barlow Scrum Team: PuppetDB Scope Change Reason: Code Cleanup Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1256) PR (1276): (maint) Add =-after? macro for import/export testing - ajroetker
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1256 PR (1276): (maint) Add =-after? macro for import/export testing - ajroetker Change By: Steve Barlow Scrum Team: PuppetDB Scope Change Reason: PR Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1243) We should accept null fields for noop for incoming commands
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1243 We should accept null fields for noop for incoming commands Change By: Steve Barlow Scope Change Reason: PR Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1248) Write Initial PuppetDB 3.0 Release Notes
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1248 Write Initial PuppetDB 3.0 Release Notes Change By: Steve Barlow Scope Change Reason: Russ joined team. Pulled in some tasks for him Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1249 PR (1270): (maint) benchmark improvements - wkalt Change By: Steve Barlow Scope Change Reason: PR Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4051) Master unable to reliably reload puppet.conf
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-4051 Master unable to reliably reload puppet.conf Change By: Henrik Lindberg Assignee: Andy Parker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1244) Status: (query) Add capability for latest-report? handling for reports
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1244 Status: (query) Add capability for latest-report? handling for reports Change By: Steve Barlow Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1257) PR (1280): (maint) Switch us to use c4.large instances for acceptance - kbarber
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1257 PR (1280): (maint) Switch us to use c4.large instances for acceptance - kbarber Change By: Steve Barlow Scope Change Reason: PR Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1242) PR (1264): Remove some unused legacy query code - kbarber
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1242 PR (1264): Remove some unused legacy query code - kbarber Change By: Steve Barlow Scope Change Reason: Some code cleanup and removal. Did not block any ticket but was trivial and did not want to leave in as tech debt. Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1239) PR (1258): Remove pinning against a git sha1 for beaker now ezbake helpers have been released - kbarber
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1239 PR (1258): Remove pinning against a git sha1 for beaker now ezbake helpers have been released - kbarber Change By: Steve Barlow Scope Change Reason: Staying in sync with EZBAKE update that happened during sprint Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1241) Resource event timestamps should be normalized
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1241 Resource event timestamps should be normalized Change By: Steve Barlow Scope Change Reason: Found when working on PDB-908 Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1240) PR (1261): Bump to latest ezbake plugin - kbarber
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1240 PR (1261): Bump to latest ezbake plugin - kbarber Change By: Steve Barlow Scope Change Reason: Staying in sync with EZBAKE update that happened during sprint Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1132) the events endpoint should not require a query
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1132 the events endpoint should not require a query Change By: Steve Barlow Scope Change Reason: Fixed an annoyance that slowed down development. Did not block any ticket, but slowed down several so it was fixed. Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1003) "You shall not pass!" error could be more informative
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1003 "You shall not pass!" error could be more informative Change By: Steve Barlow Scope Change Reason: Was included just after sprint planning. Intention was to have it in sprint. Misclick. Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4001) Packaging should create default module directories for puppet
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-4001 Packaging should create default module directories for puppet Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1515) When compiling a catalog, providers should be loaded from specified environment
Title: Message Title Henrik Lindberg commented on PUP-1515 Re: When compiling a catalog, providers should be loaded from specified environment Elyse Salberg The problem you are describing is most likely something else. This ticket is for a problem when the compiler validates a resource and picks a provider from the wrong environment. Sounds more related to similar problems with pluginsync. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1635) "current thread not owner" after Puppet Agent receives USR1 signal
Title: Message Title Kylo Ginsberg commented on PUP-1635 Re: "current thread not owner" after Puppet Agent receives USR1 signal This can be verified without using mco. 1) Start a puppet master (webrick or puppet-server, whatever is easiest for you). It can be a little easier if you turn on --verbose, because it will be obvious when the agent checks in. 2) Start an agent daemonized pointing at the puppet master (you'll see that it checks in with the master, this is SOP not part of this fix). 3) Send the agent a USR1 signal. Find the agent pid, and issue 'kill -USR1 '. In about 5 seconds (exact timing isn't a requirement), you should see the agent checking in with the master. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4034) Update MSI for AIO
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4034 Update MSI for AIO Change By: Steve Barlow Scope Change Reason: AIO Discovery Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4040) AIO pipelines fail transiently when git cloning puppet-win32-ruby
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4040 AIO pipelines fail transiently when git cloning puppet-win32-ruby Change By: Steve Barlow Scope Change Reason: AIO Discovery Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4006) Windows Unified Installer should track Cfacter version correctly
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4006 Windows Unified Installer should track Cfacter version correctly Change By: Steve Barlow Scope Change Reason: AIO Discovery Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4009 Add Cfacter 0.4.0 to Windows MSI Change By: Steve Barlow Scope Change Reason: AIO Discovery Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3845) Windows Unified Installer should track internal component versions
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3845 Windows Unified Installer should track internal component versions Change By: Steve Barlow Scope Change Reason: AIO Discovery Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3845) Windows Unified Installer should track internal component versions
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3845 Windows Unified Installer should track internal component versions Change By: Steve Barlow Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1256) PR (1276): (maint) Add =-after? macro for import/export testing - ajroetker
Title: Message Title gepetto-bot commented on PDB-1256 Re: PR (1276): (maint) Add =-after? macro for import/export testing - ajroetker senior commented: +1 from me too, will get it merged this evening Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1187) Logs & Metrics: (query) Provide end points for querying report logs, metrics for a specific report
Title: Message Title AJ Roetker assigned an issue to AJ Roetker PuppetDB / PDB-1187 Logs & Metrics: (query) Provide end points for querying report logs, metrics for a specific report Change By: AJ Roetker Assignee: AJ Roetker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4050) Acceptance suite and install.rb use incorrect paths on Windows for codedir
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4050 Acceptance suite and install.rb use incorrect paths on Windows for codedir Change By: Ethan Brown Summary: Acceptance suite uses and install.rb use incorrect paths on Windows for codedir Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1247) Get the TK max-threads fixes on stable
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-1247 Get the TK max-threads fixes on stable Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1099) make the /v4/catalogs endpoint use "certname" key instead of "name"
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-1099 make the /v4/catalogs endpoint use "certname" key instead of "name" Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4050) Acceptance suite uses incorrect paths on Windows for codedir
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4050 Acceptance suite uses incorrect paths on Windows for codedir Change By: Ethan Brown Summary: Install.rb Acceptance suite uses incorrect path paths on Windows for codedir Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4050) Acceptance suite uses incorrect paths on Windows for codedir
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-4050
Acceptance suite uses incorrect paths on Windows for codedir
Change By:
Ethan Brown
According to https://github.com/puppetlabs/puppet-specifications/blob/master/file_paths.md#puppet-agent-windows, {{:codedir}} is at {{C:\ProgramData\PuppetLabs\code}}. The install.rb in Puppet sets it to {{C:\ProgramData\PuppetLabs\puppet\code}}, which is incorrect. Additionally, the existing YAML files being used for acceptance that feature these paths should be modified:https://github.com/puppetlabs/puppet/blob/master/acceptance/config/nodes/win2012r2-rubyx64.yamlhttps://github.com/puppetlabs/puppet/blob/master/acceptance/config/nodes/win2012r2-rubyx86.yaml
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Ethan Brown commented on PUP-4050 Re: Install.rb uses incorrect path on Windows for codedir With the changes introduced by PUP-4034 / PUP-4037 to change default Windows path for :vardir, default values in the acceptance setup were incidentally broken. This wasn't noticed immediately, since acceptance for Windows packages has been recently disabled. This was an oversight and should have been addressed in https://github.com/puppetlabs/puppet/pull/3646, but was not. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1515) When compiling a catalog, providers should be loaded from specified environment
Title: Message Title Lindsey Smith assigned an issue to Lindsey Smith Puppet / PUP-1515 When compiling a catalog, providers should be loaded from specified environment Change By: Lindsey Smith Assignee: Charlie Sharpsteen Lindsey Smith Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Ethan Brown Scrum Team: Client Platform Windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Ethan Brown Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Ethan Brown Sprint: Client Windows 2015-03- 04 11 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Heidi Pio updated an issue Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Heidi Pio Scope Change Reason: Blocker work that needs to be completed asap Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Ethan Brown Scope Change Reason: Blocker work that needs to be completed asap Windows acceptance broken without these changes Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1247) Get the TK max-threads fixes on stable
Title: Message Title Russell Mull commented on PDB-1247 Re: Get the TK max-threads fixes on stable Upon further investigation, PDB-813 already included code to handle old-style cert-whitelist config. Since it applies pretty cleanly to stable, I'm going with a straight backport. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4051) Master unable to reliably reload puppet.conf
Title: Message Title
Rolf updated an issue
Puppet / PUP-4051
Master unable to reliably reload puppet.conf
Change By:
Rolf
The webrick puppet master watches its {{config}} file for changes. When the file changes, it then will reload the file, and try to apply a new settings catalog. However, depending on what the settings catalog will end up doing, this may throw an error, which results in the master process shutting down. You can reproduce this problem by simply starting While debugging an unrelated puppetdb issue, I changed debug_level on a vagrant testing recipe I use for testing roles with exported resources. I added log_level=debug and suddenly my nodes would start getting puppet master daemon, opening the {{/etc/puppet/puppet run failures . conf}} file, A restart was needed and inserting the line:{noformat}ssldir = /var/lib/ nodes would then get successful puppet /ssl2 runs. {noformat} This It should cause be noted that the master catalog would compile just fine. In particular, the failures were around hiera data from parent classes. I compiled the catalog to crash verify the hiera lookup was found appropriately . The problem stems from the fact PUP-2834 was closed as wont-fix but I think minimally that the master has dropped privileges as part puppet config auto reload should be disabled on webrick instances. This kind of daemonizing erroneous behavior makes trouble shooting all but impossible . Therefore there are certain changes to the system that it simply can't perform.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4051) Master unable to reliably reload puppet.conf
Title: Message Title Rolf created an issue Puppet / PUP-4051 Master unable to reliably reload puppet.conf Issue Type: Bug Assignee: Andy Parker Components: Server Created: 2015/02/26 12:53 PM Priority: Normal Reporter: Rolf The webrick puppet master watches its config file for changes. When the file changes, it then will reload the file, and try to apply a new settings catalog. However, depending on what the settings catalog will end up doing, this may throw an error, which results in the master process shutting down. You can reproduce this problem by simply starting a puppet master daemon, opening the /etc/puppet/puppet.conf file, and inserting the line: ssldir = /var/lib/puppet/ssl2 This should cause the master to crash. The problem stems from the fact that the master has dropped privileges as part of daemonizing. Therefore there are certain changes to the system that it simply can't perfo
Jira (PUP-1515) When compiling a catalog, providers should be loaded from specified environment
Title: Message Title Elyse Salberg commented on PUP-1515 Re: When compiling a catalog, providers should be loaded from specified environment Not to hijack this ticket, but I just ran into a situation where I update a module with a custom type/provider, and while I could see the updated type/provider in my environments, the agent could not utilize them until I restarted the pe-puppetserver process. If we're talking about loading providers from specified environments, could there be a situation of needing to kick the pe-puppetserver process in between, or was my situation different / unrelated? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Ethan Brown Labels: AIO Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Ethan Brown Component/s: Windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Michael Smith created an issue Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Issue Type: Bug Assignee: Unassigned Created: 2015/02/26 12:06 PM Priority: Normal Reporter: Michael Smith According to https://github.com/puppetlabs/puppet-specifications/blob/master/file_paths.md#puppet-agent-windows, :codedir is at C:\ProgramData\PuppetLabs\code. The install.rb in Puppet sets it to C:\ProgramData\PuppetLabs\puppet\code, which is incorrect. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4050) Install.rb uses incorrect path on Windows for codedir
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-4050 Install.rb uses incorrect path on Windows for codedir Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1467) DIE :undef, DIE!
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-1467
DIE :undef, DIE!
Change By:
Nicholas Fagerlund
I'm not sure if this should be flagged as a bug, a feature, or a refactor because this issue covers all three. :)Yesterday afternoon I discovered a template in a fairly popular module that did not work correctly on puppet 3.2.1 due to it's use of `:undef`. The fix was to replace `:undef` with `#nil?`.@@ -14,10 +14,10 @@ server { ssl_protocols <%= @ssl_protocols %>; ssl_ciphers <%= @ssl_ciphers %>; ssl_prefer_server_ciphers on;-<% if @auth_basic != :undef -%>+<% unless @auth_basic.nil? -%>auth_basic"<%= @auth_basic %>"; <% end -%>-<% if @auth_basic_user_file != :undef -%>+<% unless @auth_basic_user_file.nil? -%> auth_basic_user_file <%= @auth_basic_user_file %>; <% end -%>It appears that in at least some cases (perhaps limited to erb?) real `nil`s are leaking out instead of `:undef`. I've unable to pass an `:undef` into a template at all in testing in either 3.2.1 or 3.2.3. I don't know if this has ever worked or is a regression.{code}$ cat undef_test.ppnotify{'undeclared': message => inline_template('<%= @foo == :undef %> : <%= @foo.nil? %>')}$empty = ''notify{'empty': message => inline_template('<%= @empty == :undef %> : <%= @empty.nil? %>')}$undef = undefnotify{'undef': message => inline_template('<%= @undef == :undef %> : <%= @undef.nil? %>')}$false = falsenotify{'false': message => inline_template('<%= @false == :undef %> : <%= @false.nil? %>')}$ puppet --version3.2.3$ puppet apply undef_test.pp Notice: false : falseNotice: /Stage[main]//Notify[false]/message: defined 'message' as 'false : false'Notice: false : falseNotice: /Stage[main]//Notify[empty]/message: defined 'message' as 'false : false'Notice: false : trueNotice: /Stage[main]//Notify[undeclared]/message: defined 'message' as 'false : true'Notice: false : trueNotice: /Stage[main]//Notify[undef]/message: defined 'message' as 'false : true'Notice: Finished catalog run in 0.11 seconds{code}Upon digging into the puppet source, it appears that usage and testing for `:undef` is inconsistent in the core. Consider `Puppet::Parser::Scope#true?` that tests for `:undef` to be used as a boolean value. https://github.com/puppetlabs/puppet/blob/3.2.3/lib/puppet/parser/scope.rb#L113-L122 . Elsewhere in the same class `:undef` is being checked for directly https://github.com/puppetlabs/puppet/blob/3.2.3/lib/puppet/parser/scope.rb#L392The case against `:undef` * It violates the princible of 'least surprise' in that it duplicates a built in language feature * In at least some circumstances `nil` leaks out in place of `:undef` * Test coverage of `:undef` is insufficent * Usage of `:undef` appears inconsistent in the coreI'd agrue that in stead of trying to replicate/maintain externally visible inconsistent behavior that it would be better to just remove `:undef` completely and deal with the API change all at once, perhaps in a 3.3.0 release. UPDATEThe resolution of this is that Puppet 4.0.0 and 3x with future parser will :* Always use translate puppet {{ nil undef }}
Jira (PUP-4049) System module path should be a thing on Windows
Title: Message Title
Josh Cooper created an issue
Puppet / PUP-4049
System module path should be a thing on Windows
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/02/26 12:05 PM
Priority:
Normal
Reporter:
Josh Cooper
puppet's `basemodulepath` defaults to:
:basemodulepath => {
:default => "$codedir/modules#{File::PATH_SEPARATOR}/opt/puppetlabs/puppet/modules",
The system module path is hardcoded to be *nix specific. The default value should be updated to a place that makes sense on Windows, likely C:\ProgramData\PuppetLabs\puppet\modules.
https://github.com/puppetlabs/puppet-specifications/blob/master/file_paths.md will need to be updated too.
Jira (PDB-1184) Logs: Add logs storage and retrieval support
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1184 Logs: Add logs storage and retrieval support Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title gepetto-bot commented on PDB-1249 Re: PR (1270): (maint) benchmark improvements - wkalt 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/728/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4048) Custom/external fact can supply non-authoritative environment to Hiera
Title: Message Title Ranjit Viswakumar updated an issue Puppet / PUP-4048 Custom/external fact can supply non-authoritative environment to Hiera Change By: Ranjit Viswakumar Security: Internal Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1515) When compiling a catalog, providers should be loaded from specified environment
Title: Message Title Nicholas Fagerlund assigned an issue to Charlie Sharpsteen Puppet / PUP-1515 When compiling a catalog, providers should be loaded from specified environment Change By: Nicholas Fagerlund Assignee: Nicholas Fagerlund Charlie Sharpsteen Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1515) When compiling a catalog, providers should be loaded from specified environment
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-1515 When compiling a catalog, providers should be loaded from specified environment Change By: Nicholas Fagerlund Summary: types/ When compiling a catalog, providers should be loaded from specified environment Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1515) types/providers should be loaded from specified environment
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-1515
types/providers should be loaded from specified environment
Change By:
Nicholas Fagerlund
When compiling a catalog, types and providers are validated, but while Puppet will load types from the agent -requested 's environment (modulo , it only loads providers from the compiling master's default environment (production) during one phase of the compilation . We should ensure we autoload types and providers from This is a problem because the same environment method that creates the {{provider}} parameter is specified sometimes called due to code in the *provider,* not the type . one example: If you have a custom resource type /provider only exists in another a non-default environment , and you declare a resource that is broken specifies a value for the {{provider}} attribute , it should not produce this can cause an {{invalid parameter provider}} error in another .The expected behavior is that Puppet will autoload types and providers from the agent's environment. original description:In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're able to reproduce and fix the issue. Final resolution: When validating resources during catalog compilation, Puppet will load types and providers from the environment that the catalog is being compiled for. (Modulo that other bug that causes cross-environment contamination.)
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PDB-1268) Add validation for run interval and numhosts to benchmark
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-1268 Add validation for run interval and numhosts to benchmark Issue Type: Bug Assignee: Unassigned Created: 2015/02/26 11:50 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Ryan Senior Currently when you attempt to launch benchmark without a run interval or numhosts, you get an unintuitive NumberFormatException. We should just include a basic check for the param and write out a nice error message if the user doesn't include it. Add Comment
Jira (PDB-1267) KahaDB Recovery after PostgreSQL database disconnect
Title: Message Title Brian Wong created an issue PuppetDB / PDB-1267 KahaDB Recovery after PostgreSQL database disconnect Issue Type: Bug Affects Versions: PDB 2.2.2 Assignee: Unassigned Created: 2015/02/26 11:49 AM Environment: PostgreSQL 9.3.5, CentOS 7, and PuppetDB 2.2.2 Labels: kahadb postgresql Priority: Normal Reporter: Brian Wong Our database had some connectivity problems but was recovered within a few minutes. In the PuppetDB logs I saw: 2015-02-25 20:11:02,872 ERROR [c.j.b.h.AbstractConnectionHook] Failed to acquire connection Sleeping for 7000ms and trying again. Attempts left: 5. Exception: java.net.NoRouteToHostException: No route to host 2015-02-25 20:11:11,890 ERROR [c.j.b.h.AbstractConnectionHook] Failed to acquire connection Sleeping for 7000ms and trying again. Attempts left: 4. Exception: java.net.NoRouteToHostException: No route to host 2015-02-25 20:11:20,908 ERROR [c.j.b.h.AbstractConnectionHook] Failed to acquire connection Sleeping for 7000ms an
Jira (PUP-1515) types/providers should be loaded from specified environment
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Nicholas Fagerlund The autoloader currently loads When compiling a catalog, types and providers are validated, but while Puppet will load types from the agent-requested environment (modulo only loads providers from the default environment (production) during one phase of the compilation. We should ensure we autoload types and providers from the same environment that is specified.one example:If you have a custom type/provider in another environment that is broken, it should not produce an error in another environment. original description:In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're able to reproduce and fix the issue. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title gepetto-bot commented on PDB-1249 Re: PR (1270): (maint) benchmark improvements - wkalt 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/726/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3632) Update paths and defaults for the unified FS layout
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: Eric Thompson Priority: Normal Blocker Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1515) types/providers should be loaded from specified environment
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Eric Thompson If you have a custom type/provider in another environment that is broken, it should not produce an error in another environment. The autoloader currently loads types and providers from the default environment (production) during one phase of the compilation.We should ensure we autoload types and providers from the same environment that is specified. one example: If you have a custom type/provider in another environment that is broken, it should not produce an error in another environment. original description:In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're able to reproduce and fix the issue. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1249) PR (1270): (maint) benchmark improvements - wkalt
Title: Message Title gepetto-bot commented on PDB-1249 Re: PR (1270): (maint) benchmark improvements - wkalt wkalt commented: @senior has raised the issue that we don't ship the acceptance directory, so as written package users won't be able to use the -D flag. This shouldn't be merged until we figure out what to do there. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1515) types/providers should be loaded from specified environment
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Eric Thompson If you have a custom type/provider in another environment that is broken, it should not produce an error in another environment. The autoloader currently loads types and providers from the default environment (production) during one phase of the compilation.We should ensure we autoload types and providers from the same environment that is specified.original description: In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're able to reproduce and fix the issue. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3632) Update paths and defaults for the unified FS layout
Title: Message Title Eric Thompson assigned an issue to Michael Smith Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: Eric Thompson Assignee: Eric Thompson Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3632) Update paths and defaults for the unified FS layout
Title: Message Title Eric Thompson commented on PUP-3632 Re: Update paths and defaults for the unified FS layout Michael Smith this can probably be resolved if your experience with the acceptance test tells you it is appropriate. please ping me with the PR when you are done. thanks! Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1515) types/providers should be loaded from specified environment
Title: Message Title Eric Thompson assigned an issue to Nicholas Fagerlund Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Eric Thompson Assignee: Nicholas Fagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3632) Update paths and defaults for the unified FS layout
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: Eric Thompson QA Contact: Erik Dasher Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1515) types/providers should be loaded from specified environment
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Eric Thompson Summary: Invalid parameter provider for custom types/providers should be loaded from specified environment Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1190) Logs: (query) Anonymization for report logs
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1190 Logs: (query) Anonymization for report logs Change By: Kenneth Barber Sprint: PuppetDB 2015- 04 03 - 08 25 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
