Jira (PUP-8143) Some Solaris Init services are not functional with Puppet 5
Title: Message Title Maggie Dreyer commented on PUP-8143 Re: Some Solaris Init services are not functional with Puppet 5 I haven't been able to repro the failure myself, so I can't guarantee the change from none to child fixes it, but I did run the change through the tests we have around the contract behavior, and it didn't seem to cause any problems. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-174) bolt needs to be able to use an external SSH executable
Title: Message Title Nick Lewis commented on BOLT-174 Re: bolt needs to be able to use an external SSH executable Per a discussion in slack, it seems Net::SSH is also missing a fair number of modern crypto algorithms, making it impossible to use in some environments. Since it seems unlikely (judging by issue comments on net-ssh) that will change any time soon, the ability to use a known-good external ssh seems all the more valuable. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3761) Docs for JSONB fact storage
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3761 Docs for JSONB fact storage Change By: Rob Browning Make sure to include Include mention of the fact path gc "sloppiness" . Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3761) Docs for JSONB fact storage
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3761 Docs for JSONB fact storage Change By: Rob Browning Make sure to include mention of the fact path gc "sloppiness" Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7888) Pluginsync modules with deep directories fail on Windows
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-7888 Pluginsync modules with deep directories fail on Windows Change By: Owen Rodabaugh CS Priority: Minor Normal CS Impact: It appears that there is a workaround for this by turning "NTFS long path support." in Server 2016. Unfortunately the issue this is on the windows side so short of pulling not an option in resources to turn on this setting by default 2008 or 2012.In those older versions there doesn't seem to be much we can do other than try to limit path lengths in our modules is no workaround so this prevents functionality for users who have long paths . CS Severity: 2 3 - Annoyance Serious CS Business Value: 3 4 - $ Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8104) Include hiera-eyaml gem in puppetserver packages
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-8104 Include hiera-eyaml gem in puppetserver packages Change By: Owen Rodabaugh CS Priority: Major CS Impact: Some customers indicated they are seriously considering moving to Ansible because it has vault(the eyaml like solution for ansible) built in and supported. To have parity we need something like that and eyaml would seem to be the simplest way to get there. CS Severity: 4 - Major CS Business Value: 4 - $ CS Frequency: 3 - 25-50% of Customers Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-7822) Make the fact() function from stdlib part of core puppet so that the dot syntax is available in the DSL by default
Title: Message Title Henrik Lindberg commented on PUP-7822 Re: Make the fact() function from stdlib part of core puppet so that the dot syntax is available in the DSL by default I can live with value(), it is somewhat related to values() to get the values out of a hash. My opinion is: As a programmer reading and guessing what puppet code means, it is easier to guess what the imperative get does. To me value is confusing and ambiguous since everything is a value of some kind. I think I would want value_at to make it clear that it is an index/path that tells me where the value is. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-57) Download a file
Title: Message Title Peter Souter commented on BOLT-57 Re: Download a file If we are going to go for an scp like semantic, it would be good if we could do things like wild-card matching, as that would help out with https://tickets.puppetlabs.com/browse/BOLT-191 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-57) Download a file
Title: Message Title Cody Herriges commented on BOLT-57 Re: Download a file I don't take any issue with the idea of following the "cp" semantics, think it is a pretty solid idea. I am a bit uneasy about associating anything with the "r*" family of unix commands though, even is the underlying implementation doesn't use them. Means we're constantly having to remind people that this is actually SSH and more like "scp" than "rcp". What's the CLI equivalent of the suggested Puppet code? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8172) Puppet 4.10.6 exporting chained dep to puppetdb
Title: Message Title Henrik Lindberg commented on PUP-8172 Re: Puppet 4.10.6 exporting chained dep to puppetdb The reason this now fails is because the validation performed with respect to relationships. Earlier if a relationship was formed with something that did not exist puppet simply ignored the relationship and did nothing. This caused a lot of grief and debugging and we decided to add validation so that all formed relationships must be between things that exist. Here we are getting an instance of Host from PDB, it comes with a meta parameter that makes it depend on Service['lsf] and it fails at some point (either directly when trying to instantiate it, or at the end of the compilation when it is validating all of the resources. I don't know what the desired behaviour is in all situations - but here is my take: if a realized X depends on a realized Y then I would expect it to retain that dependency in the catalog where they are both realized If a realized X depends on a non existing Y, then I would expect it to ignore that dependency In all other cases, a dependency must be to an existing resource at the end of the compilation Faye Gibbins Do you by any chance have a stack trace (i.e. the logged error)? That helps with figuring out where exactly this particular problem is detected and how hard it would be to fix. Ping Josh Cooper - what do you think the behaviour should be? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3760) JSONB facts query support
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3760 JSONB facts query support Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3759) JSONB facts write path
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3759 JSONB facts write path Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3763) Store hash of fact paths per-factset
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3763 Store hash of fact paths per-factset Issue Type: Sub-task Assignee: Unassigned Created: 2017/11/14 10:39 AM Priority: Normal Reporter: Russell Mull Compute the hash of all fact paths when receiving a new hashset Add a column to factsets with this hash When receiving a new factset, compare the hash of its paths to the one in the db. If they're the same, skip the fact_paths update code. If they're different, update fact_paths and write a new hash. Add Comment
Jira (BOLT-57) Download a file
Title: Message Title
Henrik Lindberg commented on BOLT-57
Re: Download a file
To support multiple operations source and target could be arrays - such that:
an array in source or target must have the same kind - i.e. Array[Target] or Array[String].
if target is Array[Target] (i.e. to remotes):
a (non array) single source is copied to each remote host at the specified path per target
an array source - is an error (as there is no way to specify different filenames per different targets)
if source is Array[Target] (i.e. from remotes)
The target must be a (non array) directory and each copied file is stored in a directory / with the remote (leaf) filename
An array target is an error
Example - copy 'foo.txt' to two hosts:
$targets = [
Target('kermit.com', path => '/tmp/foo.txt'),
Target('gonzo.com', path => '/tmp/foo.txt')
]
Jira (PDB-3757) Convert select_facts to work with jsonb
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3757 Convert select_facts to work with jsonb Change By: Russell Mull Story Points: 1 Issue Type: Improvement Sub-task Parent: PDB-3723 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7635) Custom service provider is always selected as default
Title: Message Title
Daniel Urist commented on PUP-7635
Re: Custom service provider is always selected as default
One other note-- setting a default service provider in site.pp like this doesn't work either (i.e. my provider is reported as the default by facter):
Service { provider => 'debian' }
This sure looks like a bug to me
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3762) Use SHA for jsonb fact hash
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3762 Use SHA for jsonb fact hash Issue Type: Sub-task Assignee: Unassigned Created: 2017/11/14 10:35 AM Priority: Normal Reporter: Russell Mull Current impl uses clojure's (hash) fn, which we shouldn't be using here. Store this as bytea. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3761) Docs for JSONB fact storage
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3761 Docs for JSONB fact storage Issue Type: Sub-task Assignee: Unassigned Created: 2017/11/14 10:33 AM Priority: Normal Reporter: Russell Mull Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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/op
Jira (PDB-3760) JSONB facts query support
Title: Message Title Russell Mull assigned an issue to Wyatt Alt PuppetDB / PDB-3760 JSONB facts query support Change By: Russell Mull Resolution: Fixed Assignee: Wyatt Alt Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3759) JSONB facts write path
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-3759 JSONB facts write path Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3723) Use JSONB for fact storage
Title: Message Title Russell Mull assigned an issue to Unassigned PuppetDB / PDB-3723 Use JSONB for fact storage Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3756) Add fact_paths gc for jsonb overhaul
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3756 Add fact_paths gc for jsonb overhaul Change By: Russell Mull Story Points: 1 Issue Type: Improvement Sub-task Parent: PDB-3723 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3759) JSONB facts write path
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3759 JSONB facts write path Change By: Russell Mull Summary: JSONB facts write path Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3760) JSONB facts query support
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3760 JSONB facts query support Issue Type: Sub-task Assignee: Unassigned Created: 2017/11/14 10:30 AM Priority: Normal Reporter: Russell Mull Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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/opto
Jira (PDB-3759) JSONB write path
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3759 JSONB write path Issue Type: Sub-task Assignee: Unassigned Created: 2017/11/14 10:30 AM Priority: Normal Reporter: Russell Mull Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5206 Puppet filebucket --local uses $bucketdir instead of $clientbucketdir Change By: Josh Cooper Fix Version/s: PUP 5.3.z Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5206) Puppet filebucket --local uses $bucketdir instead of $clientbucketdir
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-5206 Puppet filebucket --local uses $bucketdir instead of $clientbucketdir Change By: Josh Cooper Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-57) Download a file
Title: Message Title
Henrik Lindberg commented on BOLT-57
Re: Download a file
How about mimicking rcp and have a remote_copy(source, target) where the side being remote must be given as a Target and the side that is a local file is a path? Proposing this because people are probably familiar with rcp, and cp and that this gets rid of the somewhat ambiguous "to"/"from" or "up"/"down".
Here is an example. Note that we encode the path to the file as an option in the Target.
To copy from the remote system to the local bolt controller:
remote_copy(Target('kermit.com', path => '/tmp/buildresult.zip'), "${resultdir}/buildresult.zip")
To copy the other way:
remote_copy("${resultdir}/buildresult.zip", Target('kermit.com', path => '/tmp/buildresult.zip'))
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8172) Puppet 4.10.6 exporting chained dep to puppetdb
Title: Message Title Josh Cooper commented on PUP-8172 Re: Puppet 4.10.6 exporting chained dep to puppetdb ping Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8077) terminus is undefined in lib/puppet/indirector/indirection.rb
Title: Message Title Josh Cooper commented on PUP-8077 Re: terminus is undefined in lib/puppet/indirector/indirection.rb The code looks correct to me as is. Are you using a custom node terminus? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-156) implement powershell input method
Title: Message Title Michael Smith commented on BOLT-156 Re: implement powershell input method Noted in spec - https://github.com/puppetlabs/puppet-specifications/tree/master/tasks#powershell - but it's not very thorough. Should be expanded to include enough detail about what pxp-agent does to implement. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-57) Download a file
Title: Message Title
Alex Dreyer commented on BOLT-57
Re: Download a file
Can this be called "download" since it's the opposite of upload. Would it make more sense to change upload to copy_to and call this copy_from?
What is the syntax for the function? What is the syntax for the {bolt file download}
command? How should it deal with multiple targets?
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-57) Download a file
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-57
Download a file
Change By:
Alex Dreyer
From [~alex]:{quote}I've run into the opposite problem in trying to deploy forge as well. I need to build an artifact on a target and then copy it back to the controller to deploy elsewhere.{quote}This ticket is to add a download file from target nodes to the bolt controller option to the CLI. It probably only makes sense to download from a single node to the controller.See also the ability to upload files TASKS-51.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8172) Puppet 4.10.6 exporting chained dep to puppetdb
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8172
Puppet 4.10.6 exporting chained dep to puppetdb
Change By:
Josh Cooper
If hostA has a manifest that includes these two stanzas:{quote}@@host {$::fqdn: ip => $::ipaddress, host_aliases => $::hostname, tag => $stratum, before => [],}{quote}and{quote}Host <| |> -> Service['lsf']{quote}Then puppetserver/agent exports these to puppetdb such that any machine realizing Host<<| |>> must also have defined an 'lsf' service or the catalogue will fail to compile.This is unexpected behaviour. And is not documented AFAICT as a consequence of using chained deps in the docs: https://puppet.com/docs/puppet/4.10/lang_relationships.html#caveats-when-chaining-resource-collectorsHere is an actual example from a JSON query from puppetdb (edited to remove confidential information):{ { noformat} puppet/:0 root@puppet:manifests$ curl -G -H "Accept: application/json" 'http://localhost:8080/pdb/query/v4/resources' --data-urlencode 'query= ["and" ,["=","certname","xxx"],["=","exported", true]]' --data-urlencode 'pretty=true'[ { "tags" : [ "x", "host", "class", "xxx::collect_hostnames", "xxx::all_machines", "all_machines", "all_machines_really", "xxx", "app-dev", "xxx::all_machines_really", "collect_hostnames", "default", "node" ], "file" : "/etc/puppetlabs/code/environments/international_aws_test/site_data/xxx/manifests/collect_hostnames.pp", "type" : "Host", "title" : "xxx", "line" : 58, "resource" : "f38eac2870292d6fb4286c67dd181c3bca61", "environment" : "international_aws_test", "certname" : "xxx", "parameters" : {"ip" : "10.102.0.223","tag" : "app-dev","before" : [ "Service[lsf]" ],"host_aliases" : "ssh" }, "exported" : true} ] puppet/:0 root@puppet:manifests$ puppet --version4.10.6puppet/:0 root@puppet:manifests$ {noformat } } I've not noticed this behavour in puppet v3.Please could it be confirm if this is expected behaviour or not.If it is could the docs be updated with an extra caveat to cover this?If this is not expected behaviour please could this be fixed?An optional way to stop this chained dep being exported would be appechiated.
Add Comment
Jira (BOLT-185) Add the execution functions from puppet to a bolt module
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-185 Add the execution functions from puppet to a bolt module Change By: David Kramer Sprint: Tasks ELP (1.0) Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8140) NoMethodErrors involving Puppet::Face instances do not have a useful error message
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8140 NoMethodErrors involving Puppet::Face instances do not have a useful error message Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8128) Add URI data type
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8128 Add URI data type Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8067) Selector expression ignored in some scenarios
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8067 Selector _expression_ ignored in some scenarios Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8050) puppet agent -e environment
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8050 puppet agent -e environment Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7822) Make the fact() function from stdlib part of core puppet so that the dot syntax is available in the DSL by default
Title: Message Title Ben Ford commented on PUP-7822 Re: Make the fact() function from stdlib part of core puppet so that the dot syntax is available in the DSL by default I very much like the function solution. I think the most user friendly solution is just making facts dot-accessible without extra language decoration, so that the fact looks exactly the same whether on the CLI (facter networking.interfaces.en0.ip) and in the language ($networking.interfaces.en0.ip), but I can see that being rather difficult to implement. The function is a close second. However, I dislike the .get() name. I very much prefer the .value() name that I proposed earlier. The reason for that is that .get() implies an imperative action, and .value() feels more declarative. We all know that the language itself is not declarative, that it instead builds a declarative catalog, but I think it's prudent to take the opportunity to encourage people to think about what things are rather than instructions to do things. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7326) Group resource (with auth_membership) failes if local Winows group contains not resolvable Domain accounts
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-7326 Group resource (with auth_membership) failes if local Winows group contains not resolvable Domain accounts Change By: Owen Rodabaugh CS Priority: Normal CS Impact: Group is one of the core resource types and should work as expected on all supported platform including windows. CS Severity: 3 - Serious CS Business Value: 5 - $$ CS Frequency: 2 - 5-25% of Customers Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3526) Add online index rebuild capability to PuppetDB
Title: Message Title Owen Rodabaugh updated an issue PuppetDB / PDB-3526 Add online index rebuild capability to PuppetDB Change By: Owen Rodabaugh CS Priority: Major CS Impact: Maintenance of Postgresql is one of the most common solutions to performance issue at large scale customers. Having this capability built into the product would increase customer satisfaction and reduce the support burden. CS Severity: 4 - Major CS Business Value: 5 - $$ CS Frequency: 2 - 5-25% of Customers Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8167) Service SMF provider tries to stop absent service
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8167 Service SMF provider tries to stop absent service Change By: Geoff Nichols Sprint: Platform Core OS Grooming /Triage Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8167) Service SMF provider tries to stop absent service
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8167 Service SMF provider tries to stop absent service Change By: Geoff Nichols Team: Platform Core OS Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7888) Pluginsync modules with deep directories fail on Windows
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-7888 Pluginsync modules with deep directories fail on Windows Change By: Owen Rodabaugh CS Priority: Minor CS Impact: It appears that there is a workaround for this by turning "NTFS long path support." Unfortunately the issue is on the windows side so short of pulling in resources to turn on this setting by default there doesn't seem to be much we can do other than try to limit path lengths in our modules. CS Severity: 2 - Annoyance CS Business Value: 3 - CS Frequency: 2 - 5-25% of Customers Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8113) Remove incorrect deprecation warning for `audit` metaparam
Title: Message Title Kris Bosland commented on PUP-8113 Re: Remove incorrect deprecation warning for `audit` metaparam Created pull request for review: https://github.com/puppetlabs/puppet/pull/6361 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1799) Disabling facter
Title: Message Title Maciej Kostkiewicz created an issue Facter / FACT-1799 Disabling facter Issue Type: Improvement Assignee: Unassigned Created: 2017/11/14 6:50 AM Priority: Trivial Reporter: Maciej Kostkiewicz Hi, sorry to post it here, I thought that this kind of discussion can be done on github, but anyway... I want to ask if there is any posibility to disable facter when invoking puppet apply? Facter version: 2.4.1 Puppet version: 3.7.4 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8094) Lookup ignores environment from the classifier when using rule with trusted facts
Title: Message Title Thomas Hallgren assigned an issue to Eric Sorenson Puppet / PUP-8094 Lookup ignores environment from the classifier when using rule with trusted facts Change By: Thomas Hallgren Assignee: Thomas Hallgren Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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.
