Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Josh Cooper commented on PUP-8562 Re: File performance nearly twice as slow after update # git bisect bad 7c29116766e33e119b67421912379cf302dc6c22 is the first bad commit commit 7c29116766e33e119b67421912379cf302dc6c22 Author: Jennifer SolmanDate: Mon Dec 11 15:42:27 2017 -0800 (PUP-8177) prevent agent from requesting locales on older server :04 04 c1c866745916524c5a8ee4fa162a5321920dd985 e4b33cf83d1547f29fbc02a5eae824d1b4406fc3 M lib :04 04 884717c67a1a4bebb33dacac36f06d89e7352351 8bb3a0f0d95eec408f4f671691a59471367a8571 M spec It looks like we're pushing the server version into the context for every http response, but never popping. And the context has an array of things to ignore. Any cache miss causes us to traverse the ignores array causing the linear slow down.
Jira (PUP-8520) Puppet Platform 5.5.0 Release - 2018-03-20
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8520 Puppet Platform 5.5.0 Release - 2018-03-20 Change By: Geoff Nichols Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Josh Cooper commented on PUP-8562 Re: File performance nearly twice as slow after update 5.3.4 and 5.3.5 show many more stats of /etc/localtime than 5.3.3 using 200 file resources with remote puppet:///modules/... sources. # puppet --version 5.3.5 # strace -c puppet agent -t Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Caching catalog for ajdsosztd6m0cqa.delivery.puppetlabs.net Info: Applying configuration version '1521778299' Notice: Applied catalog in 20.97 seconds % time seconds usecs/call callserrors syscall -- --- --- - - 36.160.020571 0203692 24913 stat 30.010.017074122014
Jira (BOLT-409) Fix inventory docs
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-409 Fix inventory docs Change By: Michael Smith Assignee: Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8552) Make dnf default for fedora, and systemd default for ubuntu/debian
Title: Message Title Kris Bosland assigned an issue to Kris Bosland Puppet / PUP-8552 Make dnf default for fedora, and systemd default for ubuntu/debian Change By: Kris Bosland Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-409) Fix inventory docs
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-409 Fix inventory docs Change By: Alex Dreyer - the final example is wrong. ssh config should be a top level config key not part of transport.{noformat}nodes: - name: host1.example.comconfig: transports:ssh: user: me run-as: root{noformat} - We should also add a warning: Values set at the top level of the inventory file will only apply to targets contained in that file. To set config for targets outside the inventory use the config file. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (BOLT-409) Fix inventory docs
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-409 Fix inventory docs Issue Type: Bug Assignee: Unassigned Created: 2018/03/22 5:01 PM Priority: Normal Reporter: Alex Dreyer the final example is wrong. ssh config should be a top level config key not part of transport. nodes: - name: host1.example.com config: transports: ssh: user: me
Jira (PUP-8591) [SPIKE] Investigate removing webrick
Title: Message Title Lizzi Lindboe created an issue Puppet / PUP-8591 [SPIKE] Investigate removing webrick Issue Type: Task Assignee: Unassigned Created: 2018/03/22 4:49 PM Priority: Normal Reporter: Lizzi Lindboe We want to investigate removing the Ruby CA/catalog serving from Puppet so that we only have one implementation of a Puppet master/CA and thus avoid some terrible conflict cases. In order to feel more confident about the difficulty of this change, try ripping some things out and testing it out to see what breaks. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-394) Update puppet task spec to include multiple task implementations
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-394 Update puppet task spec to include multiple task implementations Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8535) Backport ruby warning rake task
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8535 Backport ruby warning rake task Change By: Eric Delaney Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8535) Backport ruby warning rake task
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8535 Backport ruby warning rake task Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8562 File performance nearly twice as slow after update Change By: Josh Cooper Attachment: fileevaltimes.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8562 File performance nearly twice as slow after update Change By: Josh Cooper Attachment: fileresourceevaltimes.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8562 File performance nearly twice as slow after update Change By: Josh Cooper Attachment: fileresourceevaltimes.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-404) Build packages (Bolt 0.18.0)
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-404 Build packages (Bolt 0.18.0) Change By: Michael Smith Fix Version/s: BOLT 0.18.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-403) Tag new version (Bolt 0.18.0)
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-403 Tag new version (Bolt 0.18.0) Change By: Michael Smith Fix Version/s: BOLT 0.18.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-405) Docs for bolt release (Bolt 0.18.0)
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-405 Docs for bolt release (Bolt 0.18.0) Change By: Michael Smith Fix Version/s: BOLT 0.18.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-401) Reconcile git commits, JIRA tickets, and versions (Bolt 0.18.0)
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-401 Reconcile git commits, JIRA tickets, and versions (Bolt 0.18.0) Change By: Michael Smith Fix Version/s: BOLT 0.18.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-402) Do Jenkins gem release (Bolt 0.18.0)
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-402 Do Jenkins gem release (Bolt 0.18.0) Change By: Michael Smith Fix Version/s: BOLT 0.18.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8590) puppet device --apply does not support pcore
Title: Message Title Rick Sherman created an issue Puppet / PUP-8590 puppet device --apply does not support pcore Issue Type: Bug Assignee: Unassigned Created: 2018/03/22 3:49 PM Priority: Normal Reporter: Rick Sherman When trying to use pcore types the apply functionality in `puppet device` errors. Error: Unsupported data type: 'Symbol' on node csr1kv-local-1 /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/scope.rb:832:in `deep_freeze' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/scope.rb:825:in `block in deep_freeze' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/scope.rb:825:in `each' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/scope.rb:825:in `deep_freeze' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parser/scope.rb:808:in `set_facts'
Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Josh Cooper commented on PUP-8562 Re: File performance nearly twice as slow after update Working with Sebastian we found the following catalog application times by puppet version: Version Time (seconds) 5.2.0 59.48 5.3.3 68.65 5.3.4 broken 5.3.5 177.12 5.4.0 163,63 5.5.0 185.17 That rules out PUP-7451 and PUP-7308. Also, the aren't using http/https file resources. In looking at the last run reports, the increase is spread out across all of the file resources being managed (as opposed to any one file). For example, the longest file resource in 5.2.0 is 0.175718651 seconds, but there are over 280 files over that time in 5.3.5, with the largest one being 0.899495322 seconds. The file evaluation distribution looks to be linear, which makes me think the issue is related to PUP-8096. As the size of the persistent transaction store depends on the number of resources being managed.
Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Melissa Stone assigned an issue to Josh Cooper Puppet / PUP-8562 File performance nearly twice as slow after update Change By: Melissa Stone Assignee: Melissa Stone Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1628) Set of breaking changes staged for facter 4
Title: Message Title Branan Riley commented on FACT-1628 Re: Set of breaking changes staged for facter 4 I've re-populated this with the set of tickets I believe would be good to target here. Along with FACT-747 for Solaris, we should also look in to using the same method on AIX, the BSDs, and possibly Windows. Additionally, we have a couple tickets around how the default-route-based primary interface detection can fail. It might be nice to come up with a fallback method for when the default route looks like nonsense. One suggested method was using whatever IP the hostname resolves to (as long as its not loopback). I'll need to go through the networking tickets to finish scoping that work. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8589) Puppet apply or agent should list hiera keys, values and their paths
Title: Message Title Naeem created an issue Puppet / PUP-8589 Puppet apply or agent should list hiera keys, values and their paths Issue Type: New Feature Assignee: Unassigned Created: 2018/03/22 2:09 PM Priority: Normal Reporter: Naeem When running puppet apply or puppet agent in noop mode, the output should list all the hiera keys listed in the module along with their values and also the hiera data path(s) they were found in. In our scenario, we have a central hiera repository and the component modules do not have all the hiera data inside the module. We can run puppet apply/agent with --debug flag and it shows the hiera keys/values in the output alongwith the paths but the output is too verbose and not easily readable. The ask here is to have another flag with puppet apply/agent (let's call it --demgstify) to only lookup hiera keys required to run the module and list them along with their values and paths. This will greatly help us troubleshooting puppet runs. Add Comment
Jira (BOLT-380) Support ed25519 out-of-the-box
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-380 Support ed25519 out-of-the-box Change By: Michael Smith net-ssh requires several extra libraries for ed25519 support. Without them, users see ``` {code} 2018-02-26T13:59:32.131096 WARN Net::SSH: ignoring unimplemented key:unsupported key type `ssh-ed25519'net-ssh requires the following gems for ed25519 support: * rbnacl (>= 3.2, < 5.0) * rbnacl-libsodium, if your system doesn't have libsodium installed. * bcrypt_pbkdf (>= 1.0, < 2.0)See https://github.com/net-ssh/net-ssh/issues/478 for more informationGem::MissingSpecError : "Could not find 'rbnacl' (< 5.0, >= 3.2.0) among 86 total gem(s) ``` {code}Add them in packaging. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to
Jira (PUP-8561) Augeas unable to handle escaped quotes within quotes
Title: Message Title David Lutterkort assigned an issue to David Lutterkort Puppet / PUP-8561 Augeas unable to handle escaped quotes within quotes Change By: David Lutterkort Assignee: David Lutterkort Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1491) Failed to get IP Address
Title: Message Title Branan Riley commented on FACT-1491 Re: Failed to get IP Address That label more-or-less means "We know this is a valid issue, but we're unlikely to get to it ourselves". I found several more tickets yesterday that had similar symptoms, so I'm now of the opinion that we do need to better support this situation as an actual product effort. The default route is a much better heuristic for "primary interface" than what we had before (the first one alphabetically), but it does fail in some situations. We need to add a fallback of some sort there. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1491) Failed to get IP Address
Title: Message Title Branan Riley updated an issue Facter / FACT-1491 Failed to get IP Address Change By: Branan Riley Labels: help_wanted linux networking triaged Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1810) 60 second timeout in facter when connecting to 169.254.169.254 for ec2 metadata
Title: Message Title Branan Riley commented on FACT-1810 Re: 60 second timeout in facter when connecting to 169.254.169.254 for ec2 metadata If 2.5.2 hasn't made it out, then it's likely that it never will. Facter 2 was officially EOL'd along with Puppet 3 quite some time ago. We've done a couple of releases since then, but only when we absolutely had to due to the lack of Facter 3 gem builds. Installing Facter as a gem has effectively been in a horrible state of limbo for over a year now, so in that respect nothing has changed. We're trying to move Facter 3 gems out of prerelease as quickly as possible, and that is going to be the recommended upgrade path. We're focusing our efforts there instead of continuing to leave Facter 2 on life support. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1593) facter 2.x should disable proxy when fetching metadata from 169.254.169.254
Title: Message Title Branan Riley commented on FACT-1593 Re: facter 2.x should disable proxy when fetching metadata from 169.254.169.254 If you're installing from rubygems, then Puppet 4.5.3 should pick up a Facter 3 gem once there's a non-prerelease version later this summer. It's dependencies allow for Facter 3, we just haven't had those gems published yet. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8561) Augeas unable to handle escaped quotes within quotes
Title: Message Title David Lutterkort commented on PUP-8561 Re: Augeas unable to handle escaped quotes within quotes I just posted a PR for this. Let me know if that doesn't seem to fix it for you. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8588) Support multiple implementations when loading tasks
Title: Message Title Nick Lewis updated an issue Puppet / PUP-8588 Support multiple implementations when loading tasks Change By: Nick Lewis Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8588) Support multiple implementations when loading tasks
Title: Message Title Nick Lewis created an issue Puppet / PUP-8588 Support multiple implementations when loading tasks Issue Type: New Feature Assignee: Unassigned Created: 2018/03/22 11:31 AM Priority: Normal Reporter: Nick Lewis Currently, tasks are defined to only have one implementation file. In order to support cross-platform tasks, we need to have the ability to load multiple implementations for a task and dynamically determine which one to use on a given target. The proposal for this is to allow multiple implementation files with names matching the task, but with different extensions. This includes a new metadata key implementation which specifies the supported implementations and which features are required on the target. The TaskInstantiator needs to be updated to support this new metadata field and pass it along to Bolt. Add Comment
Jira (PUP-8588) Support multiple implementations when loading tasks
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet / PUP-8588 Support multiple implementations when loading tasks Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-404) Build packages (Bolt 0.18.0)
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-404 Build packages (Bolt 0.18.0) Change By: Michael Smith Assignee: Lucy Wyman Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-403) Tag new version (Bolt 0.18.0)
Title: Message Title Michael Smith commented on BOLT-403 Re: Tag new version (Bolt 0.18.0) Test build of packages passed acceptance with Debian 9 controller. That seems like sufficient validation based on work we've done since 0.17.2. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8587) Rich Data support (Binary and others) in Puppet 6.y
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8587 Rich Data support (Binary and others) in Puppet 6.y Change By: Kenn Hussey Priority: Normal Critical Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8187) `puppet master compile` fails to save the catalog with arbitrary binary data in file resources
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8187 `puppet master compile` fails to save the catalog with arbitrary binary data in file resources Linking this to the epic "6.y Rich Data" to make it visible as we do the work for 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8562 File performance nearly twice as slow after update Change By: Melissa Stone Sprint: Platform Core Grooming KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8562 File performance nearly twice as slow after update Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3600) Create support for binary content on the File type
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3600 Create support for binary content on the File type Change By: Henrik Lindberg Sub-team: Language Fix Version/s: PUP 5.y Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8587) Rich Data support (Binary and others) in Puppet 6.y
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8587 Rich Data support (Binary and others) in Puppet 6.y Change By: Henrik Lindberg Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8587) Rich Data support (Binary and others) in Puppet 6.y
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8587 Rich Data support (Binary and others) in Puppet 6.y Issue Type: Epic Assignee: Unassigned Created: 2018/03/22 10:34 AM Priority: Normal Reporter: Henrik Lindberg This is an epic for support of Rich Data in the Catalog for the purpose of supporting primarily the Binary data type and new features for late binding values. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8484) Update ruby 1.9.3 code paths
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8484 Update ruby 1.9.3 code paths Change By: Josh Cooper Search puppet's code base for all of the places where we branch based on {{RUBY_VERSION}}. 1. Remove code paths for < 2.2. Trying to {{require 'puppet'}} should generate a {{LoadError}} if ruby < 23. Update {{Puppet::OLDEST_RECOMMENDED_RUBY_VERSION}} to whatever minimum makes sense. 4. Remove conditional logic for Puppet[:sourceaddress] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8561) Augeas unable to handle escaped quotes within quotes
Title: Message Title David Lutterkort commented on PUP-8561 Re: Augeas unable to handle escaped quotes within quotes This is indeed a bug: what is happening is that the augeas provider lib/puppet/provider/augeas/augeas.rb dutifully recognizes escaped quote characters as part of the string, but then forgets to remove the quoting backslashes so that \" in the string gets written out as " (around line 124) I'll try to come up with a fix shortly. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3862) replace facts failing for some nodes
Title: Message Title Rajasree Talla updated an issue PuppetDB / PDB-3862 replace facts failing for some nodes Change By: Rajasree Talla Labels: customer0 irving-ss Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3862) replace facts failing for some nodes
Title: Message Title Rajasree Talla updated an issue PuppetDB / PDB-3862 replace facts failing for some nodes Change By: Rajasree Talla Affects Version/s: PE Irving Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3862) replace facts failing for some nodes
Title: Message Title Rajasree Talla commented on PDB-3862 Re: replace facts failing for some nodes pining Jeff Yarnell Russell Mull Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3862) replace facts failing for some nodes
Title: Message Title Rajasree Talla assigned an issue to Jeff Yarnell PuppetDB / PDB-3862 replace facts failing for some nodes Change By: Rajasree Talla Assignee: Jeff Yarnell Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-402) Do Jenkins gem release (Bolt 0.18.0)
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-402 Do Jenkins gem release (Bolt 0.18.0) Change By: Michael Smith Assignee: Lucy Wyman Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-360) Store facts for targets in inventory
Title: Message Title Michael Smith commented on BOLT-360 Re: Store facts for targets in inventory Present in Bolt 0.18.0, but we plan to withhold talking about it until BOLT-359 and BOLT-361 are also shipped. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-401) Reconcile git commits, JIRA tickets, and versions (Bolt 0.18.0)
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-401 Reconcile git commits, JIRA tickets, and versions (Bolt 0.18.0) Change By: Michael Smith Assignee: Lucy Wyman Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-400) Bolt 0.18.0 2018-03-21 Release
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-400 Bolt 0.18.0 2018-03-21 Release Change By: Michael Smith Fix Version/s: BOLT 0.18.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-407) Using TargetSpec in plan parameters breaks `bolt plan show`
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-407 Using TargetSpec in plan parameters breaks `bolt plan show` Change By: Michael Smith Affects Version/s: BOLT 0.16.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8586) Feature related debug messages are confusing and generate too much spam
Title: Message Title Josh Cooper created an issue Puppet / PUP-8586 Feature related debug messages are confusing and generate too much spam Issue Type: Task Assignee: Unassigned Created: 2018/03/22 10:13 AM Priority: Normal Reporter: Josh Cooper During an agent run, if a feature is not available, notably msgpack, we print a scary looking message: Debug: Dynamically-bound server lookup failed, falling back to server setting Debug: Dynamically-bound port lookup failed; falling back to masterport setting Debug: Failed to load library 'msgpack' for feature 'msgpack': cannot load such file -- msgpack Debug: Puppet::Network::Format[msgpack]: feature msgpack is missing Debug: file_metadata supports formats: json pson yaml The "Failed to load library" sounds
Jira (BOLT-400) Bolt 0.18.0 2018-03-21 Release
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-400 Bolt 0.18.0 2018-03-21 Release Change By: Michael Smith Assignee: Lucy Wyman Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8586) Feature related debug messages are confusing and generate too much spam
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8586 Feature related debug messages are confusing and generate too much spam Change By: Josh Cooper Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-365) Missing period in "E.g." in usage text
Title: Message Title David Kramer assigned an issue to Michael Smith Puppet Task Runner / BOLT-365 Missing period in "E.g." in usage text Change By: David Kramer Assignee: Kate Lopresti Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-400) Bolt 0.18.0 2018-03-21 Release
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-400 Bolt 0.18.0 2018-03-21 Release Change By: Michael Smith Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-405) Docs for bolt release (Bolt 0.18.0)
Title: Message Title Kate Lopresti commented on BOLT-405 Re: Docs for bolt release (Bolt 0.18.0) Docs are ready to merge. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-408) Include a batch plan in Bolt
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-408 Include a batch plan in Bolt Issue Type: Story Assignee: Unassigned Created: 2018/03/22 9:41 AM Priority: Normal Reporter: Michael Smith Create a batch plan - for running N nodes at a time - to include as part of the out-of-the-box experience with Bolt (similar to aggregate and canary). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-394) Update puppet task spec to include multiple task implementations
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-394 Update puppet task spec to include multiple task implementations Change By: Michael Smith https://github.com/puppetlabs/puppet-specifications/tree/master/tasks Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-393) Example for setting up PCP with bolt and how to use
Title: Message Title Michael Smith commented on BOLT-393 Re: Example for setting up PCP with bolt and how to use I'm not quite clear how this is adding anything useful on https://puppet.com/docs/bolt/0.x/bolt_configure_orchestrator.html. The only new part I see is providing a plan that does things that could only be done over PCP. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8585) puppet device --resource should fail if non-existent target is given
Title: Message Title Rick Sherman created an issue Puppet / PUP-8585 puppet device --resource should fail if non-existent target is given Issue Type: Bug Assignee: Unassigned Created: 2018/03/22 9:15 AM Priority: Normal Reporter: Rick Sherman Puppet Version: Puppet Server Version: OS Name/Version: Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful. Add Comment
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title Charlie Sharpsteen commented on PDB-3879 Re: node-purge-ttl setting not working in 2017.3 Ah, I misread this the first time — thought the problem was that the node was not getting purged from search results, when the issue is that the node is getting purged from search results too quickly. I believe this is actually expected behavior. PE 2017.2 shipped PuppetDB 4.4 and 2017.3 shipped PuppetDB 5.1. One of the changes that happened between the 4.4 and 5.1 major version break was that the /pdb/query/v4 endpoint no longer returns results from expired or deactivated nodes by default: https://puppet.com/docs/puppetdb/5.2/release_notes.html#section-6 Daniel Mcilhagga Does the query work as expected if node_state = "inactive" is used instead of expired is not null or deactivated is not null ? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title Charlie Sharpsteen assigned an issue to Daniel Mcilhagga PuppetDB / PDB-3879 node-purge-ttl setting not working in 2017.3 Change By: Charlie Sharpsteen Assignee: Daniel Mcilhagga Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8584) puppet device does not continue executing subsequent devices on CSR
Title: Message Title Rick Sherman created an issue Puppet / PUP-8584 puppet device does not continue executing subsequent devices on CSR Issue Type: Bug Assignee: Unassigned Created: 2018/03/22 8:59 AM Priority: Normal Reporter: Rick Sherman When executing `puppet device` against multiple targets processing will stop if a CSR request or --waitforcert 0 is used. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-2635) implicit subquery relationship between facts and resources via certname
Title: Message Title Daniel Parks commented on PDB-2635 Re: implicit subquery relationship between facts and resources via certname I filed a ticket to cover creating all possible implicit subqueries: PDB-3880. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3880) Add all implicit subqueries
Title: Message Title Daniel Parks created an issue PuppetDB / PDB-3880 Add all implicit subqueries Issue Type: Improvement Assignee: Unassigned Created: 2018/03/22 8:57 AM Priority: Normal Reporter: Daniel Parks Please add implicit subqueries wherever possible. For example, all of the following should have implicit subqueries based on certname: inventory { resources { title ~ "rundeck" } } resources { title ~ "rundeck" and inventory { facts.stage = "prod" } } reports { resources { title ~ "rundeck" } and inventory { facts.stage = "prod" } } resources { title ~ "rundeck" and resources { title = "Nginx" } } I use subqueries all the time, and probably >90% of the time I want a subquery based on certname. I also am never quite sure where they're enabled, so I end up always writing out certname in whatever[certname]. See also PDB-2635 filed by Wyatt Alt.
Jira (PUP-8564) puppet device - add support for custom facts
Title: Message Title Davin Hanlon updated an issue Puppet / PUP-8564 puppet device - add support for custom facts Change By: Davin Hanlon Currently `puppet device` delegates the collection of facts to the module being used.This prevents custom facts from being used.Investigate if it is possible to integrate custom facts into `puppet device` Specifically USAA want to be able to get the IP address of their IOS devices as a fact. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1810) 60 second timeout in facter when connecting to 169.254.169.254 for ec2 metadata
Title: Message Title Jan Willem commented on FACT-1810 Re: 60 second timeout in facter when connecting to 169.254.169.254 for ec2 metadata Version 2.5.2 isn't released yet. When I run gem search facter, the newest version is 2.5.1. Rubygems is still using 2.5.1: https://rubygems.org/search?utf8=%E2%9C%93=facter I can understand the phasing out of version 2, but shouldn't version 3 then be available on rubygems? Version 3.11 has just been prereleased on rubygems (https://groups.google.com/forum/#!topic/puppet-users/4tyQjrwJoD0), so are we being hijacked between installing a prerelease version and using the current, broken version? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1974) Theme: Sensitive Data in Catalogs
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-1974 Theme: Sensitive Data in Catalogs Change By: Kenn Hussey Priority: Normal Critical Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6893) Remove Ruby 1.9.3 support
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6893 Remove Ruby 1.9.3 support Change By: Kenn Hussey Priority: Normal Critical Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1830) Use libwhereami as the data source for the "virtual" and "is_virtual" facts
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1830 Use libwhereami as the data source for the "virtual" and "is_virtual" facts Change By: Kenn Hussey Due Date: 2018/06/20 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1830) Use libwhereami as the data source for the "virtual" and "is_virtual" facts
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1830 Use libwhereami as the data source for the "virtual" and "is_virtual" facts Change By: Kenn Hussey Fix Version/s: FACT 4.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4380) Split non-core puppet functionality into modules
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Kenn Hussey Due Date: 2018/ 09 05 / 19 16 Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7877) Future Work for Intermediate CA Improvements
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7877 Future Work for Intermediate CA Improvements Change By: Kenn Hussey Due Date: 2018/ 05 06 / 16 20 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7877) Future Work for Intermediate CA Improvements
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7877 Future Work for Intermediate CA Improvements Change By: Kenn Hussey Priority: Normal Critical Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8503) Agent SSL CLI
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8503 Agent SSL CLI Change By: Kenn Hussey Due Date: 2018/05/16 Priority: Normal Critical Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3834) remove webrick/rack support from Puppet
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-3834 remove webrick/rack support from Puppet Change By: Kenn Hussey Priority: Normal Critical Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8240) ERB and EPP templates handle CRLF line endings inconsistently
Title: Message Title Henrik Lindberg commented on PUP-8240 Re: ERB and EPP templates handle CRLF line endings inconsistently I put up a PR making read the same as read with preserved line ending on windows - this to get a test run. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8290) Allow auto-conversion to Sensitive data type
Title: Message Title Henrik Lindberg commented on PUP-8290 Re: Allow auto-conversion to Sensitive data type Closing this as a Won't Do as PUP-7675 is now released in Puppet 5.5.0 (the ability to specify a convert_to in lookup_options. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8539) Hiera trusted fact lookup
Title: Message Title Henrik Lindberg commented on PUP-8539 Re: Hiera trusted fact lookup Hendrik Suggest verifying that a node with a cert with the extension `pp_role` when compiling a catalog for that node has the expected information available in `$trusted`. A simple manifest with something like: notify { "have extension '${trusted.extensions.pp_role}'": } Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8539) Hiera trusted fact lookup
Title: Message Title Henrik Lindberg commented on PUP-8539 Re: Hiera trusted fact lookup As verification that the input string is understood by puppet: irb 2.3.1 :001 > require 'puppet' => true 2.3.1 :002 > x = Puppet::Pops::Lookup::LookupKey.new("trusted.extensions.'pp_role'") => # Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8539) Hiera trusted fact lookup
Title: Message Title Henrik Lindberg commented on PUP-8539 Re: Hiera trusted fact lookup Hendrik Can you show how you did the "manual lookup" ? Did you specify a node? Have that node called in to your server so that facts/parameters are available (thus storing the cert extensions)? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8539) Hiera trusted fact lookup
Title: Message Title Hendrik commented on PUP-8539 Re: Hiera trusted fact lookup I don't really understand what you mean with "stem from". But trusted.extension.pp_role is extracted from the signed ssl certificate. Also I cannot try the '–compile' options because I've changed job. I don't work there anymore... Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8539) Hiera trusted fact lookup
Title: Message Title Thomas Hallgren commented on PUP-8539 Re: Hiera trusted fact lookup Where does "trusted.extension.pp_role" stem from? Does a lookup --compile yield the same result? Some initialization that may affect facts doesn't take place unless a proper compile is performed (ENC initialization is one example). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8500) puppet lookup cli should support adding facts as arguments, not just from a file.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8500 puppet lookup cli should support adding facts as arguments, not just from a file. Change By: Henrik Lindberg Component/s: Hiera & Lookup Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1491) Failed to get IP Address
Title: Message Title t commented on FACT-1491 Re: Failed to get IP Address I see Branan Riley ask for help. I'm the person who open this issue. I don't known if it's worth the time to solve this problem. This problem appeart only when using facter inside a vserver. But as I know vserver are at it end of life, vserver don't support systemd. We still using vserver because we got lot of service, but we currently migrate to something like lxc/systemd-nspawn, that's going to take time. < /td> Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3879) node-purge-ttl setting not working in 2017.3
Title: Message Title Daniel Mcilhagga assigned an issue to Unassigned PuppetDB / PDB-3879 node-purge-ttl setting not working in 2017.3 Change By: Daniel Mcilhagga Assignee: Daniel Mcilhagga Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8441) Error datatype should support to_json
Title: Message Title Thomas Hallgren commented on PUP-8441 Re: Error datatype should support to_json Has the `Bolt::Target` datat type been loaded at the time of the call? If it has, can you please provide a stack trace? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.