Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Michael Smith updated an issue Facter / FACT-718 Allow for disabling certain facts within Facter Change By: Michael Smith Discussed here: https://groups.google.com/forum/#!topic/puppet-users/SCfVE1kpTpkWith version 1.7 facts were added for each mounted volume. When run on a server attached to a SAN with say 1,000 volumes mounted, end up with over 3,000 facts (and chocking our ENC).Would like the ability to disable these facts via a configuration file. A temporary work-around for this in Facter 3 (structured facts) is to declare a custom fact with the same name, which will mask default facts. I'm not sure how to apply that for dynamically-named facts. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1345) Solaris automount entries in mountpoint result in huge fact lists
Title: Message Title Wyatt Alt commented on FACT-1345 Re: Solaris automount entries in mountpoint result in huge fact lists No argument here Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1345) Solaris automount entries in mountpoint result in huge fact lists
Title: Message Title Michael Smith commented on FACT-1345 Re: Solaris automount entries in mountpoint result in huge fact lists That's a useful hack until FACT-718 has a solution. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1398) selinux_config_policy should handle whitespace
Title: Message Title Dylan Ratcliffe created an issue Facter / FACT-1398 selinux_config_policy should handle whitespace Issue Type: Bug Affects Versions: FACT 3.1.5 Assignee: Unassigned Created: 2016/04/19 10:06 PM Priority: Normal Reporter: Dylan Ratcliffe Here we have a regex that is grabbing the selinux_config_policy from /etc/selinux/config. We had a customer here who had a space in their /etc/selinux/config which was breaking the regex as shown here This, and any other relevant regexes should be able to handle some whitespace at the end of the setting as it does not affect the functionality of SELinux at all. Suggested fix: Add whitespace to regex Add Comment
Jira (FACT-1345) Solaris automount entries in mountpoint result in huge fact lists
Title: Message Title
Wyatt Alt commented on FACT-1345
Re: Solaris automount entries in mountpoint result in huge fact lists
I just linked this to PDB-2631 – the puppet-users post referenced in that ticket confirmed that he is not on Solaris, meaning that this is really just a bigger (well-known) issue with the way PuppetDB is storing/updating large structured facts.
I can't point to any way facter could be improved to fix the issue, so this ticket should remain closed. Any users/customers encountering it should probably be pointed to
https://docs.puppet.com/facter/latest/custom_facts.html#fact-precedence
as a way to mask the value of the problematic fact on the nodes where it is large with a custom fact valued nil (possibly "" if nil is problematic on older versions) and weight 100. Nodes where the fact is problematic can be identified by executing
select certname,name,count(*) from fact_paths inner join facts on fact_paths.id=facts.fact_path_id inner join factsets on facts.factset_id=factsets.id where name=any('{"mountpoints", "disks","partitions"}') group by certname, name order by count desc;
against the puppetdb database in psql (should be good back to PDB 2.3.8, but test first obviously).
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You
Jira (PUP-6125) verbose agent runs result data being sent console and syslog
Title: Message Title
Trevor Vaughan commented on PUP-6125
Re: verbose agent runs result data being sent console and syslog
I don't rely on this on purpose, but I've certainly relied on it accidentally since I never paid attention to the documented difference.
I do think that a metaparameter may need to be added to the language that allows for masking specific values.
Something like:
file { '/tmp/secret_sauce':
owner => 'secret',
group => 'squirrel',
content => 'not mah passwords!'
protect => ['content']
}
But, admittedly, that's a lot more work and type `to_s` methods would have to honor it, and all that jazz.
Add Comment
Jira (PDB-2636) implicit relationships for self-referencing entities on certname
Title: Message Title
Wyatt Alt created an issue
PuppetDB / PDB-2636
implicit relationships for self-referencing entities on certname
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2016/04/19 5:33 PM
Priority:
Normal
Reporter:
Wyatt Alt
This is probably worth some discussion, but it would be cool if PQL could express "give me all ipaddress facts for nodes with operatingsystem fact equal to debian"
facts[name, value]{name = "ipaddress" and facts{name = "operatingsystem" and value = "Debian"}}
the facts usecase could be obsoleted by the proposed inventory endpoint, but the same concept could apply to resources and other endpoints. It seems like certname is the most sensible field to relate an entity to itself.
Jira (PDB-2635) implicit subquery relationship between facts and resources via certname
Title: Message Title
Wyatt Alt created an issue
PuppetDB / PDB-2635
implicit subquery relationship between facts and resources via certname
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2016/04/19 5:25 PM
Priority:
Normal
Reporter:
Wyatt Alt
I'm hitting some friction translating some ops usage of puppetdb_query due to the inability to do this implicitly:
facts{resources{type = "Class" and title = "foo"} and name in ["ipaddress", "fqdn"]}
seems like certname is a natural enough link between the two entities for inclusion in our implicit relationships.
Add Comment
Jira (PUP-6179) Puppet CA face broken
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6179 Puppet CA face broken Change By: Eric Thompson QA Risk Assessment: Medium Low Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6179) Puppet CA face broken
Title: Message Title Eric Thompson commented on PUP-6179 Re: Puppet CA face broken validated on rhel7 at puppet-agent master SHA: 0fea3002a9628da1a45f098c7eebc03925936836 [root@qkm8hxby9wwevs1 ~]# puppet ca list [root@qkm8hxby9wwevs1 ~]# puppet cert list [root@qkm8hxby9wwevs1 ~]# puppet help ca USAGE: puppet ca This provides local management of the Puppet Certificate Authority. OPTIONS: --render-as FORMAT - The rendering format to
Jira (PUP-6179) Puppet CA face broken
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-6179 Puppet CA face broken Change By: Eric Thompson Assignee: qa Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6180) Add acceptance test for Puppet CA/cert faces
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6180 Add acceptance test for Puppet CA/cert faces Change By: Eric Thompson It was broken in Puppet 4 and no one knew.take into account:* tests/ssl/puppet_cert_generate_and_autosign.rb* tests/ticket_3961_puppet_ca_should_produce_certs.rb * tests/ticket_3360_allow_duplicate_csr_with_option_set.rb* tests/ssl/autosign_command.rb* tests/ssl/ticket_5274_private_key_modes.rb* tests/ssl/certificate_extensions.rb Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6091) Lookup should parse dot in key consistently throughout
Title: Message Title John Duarte commented on PUP-6091 Re: Lookup should parse dot in key consistently throughout Thanks Henrik Lindberg root@cafnsh7p7x6it68:~# puppet lookup 'key."a.b.c".0' --- a ... Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6180) Add acceptance test for Puppet CA/cert faces
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6180 Add acceptance test for Puppet CA/cert faces Change By: Eric Thompson It was broken in Puppet 4 and no one knew. take into account:* tests/ssl/puppet_cert_generate_and_autosign.rb* tests/ticket_3961_puppet_ca_should_produce_certs.rb Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6091) Lookup should parse dot in key consistently throughout
Title: Message Title John Duarte updated an issue Puppet / PUP-6091 Lookup should parse dot in key consistently throughout Change By: John Duarte QA Risk Assessment Reason: Functional expectation Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Wyatt Alt commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Priscilla Piedra there's no real maximum for fact character size, but 500 characters would be totally safe. It tends to be really large facts that are very dynamic that cause issues like the one you saw. I imagine if that ssl_certificates fact is extremely huge, and an element were inserted at the beginning of the array, you might run into the issue you did, but it's hard for me to know without actually seeing the fact. If that fact is something your company has created (rather than created by a module for instance) one change you can make to reduce the strain on PuppetDB would be to reshape it so that the top-level structure is a hash (keyed on certname for instance) rather than an array. If it doesn't cause further issues though you may as well leave it. I don't expect the changed max_stack_depth setting to cause performance drawbacks, but I would also think that now that you've successfully executed the delete, you should be able to revert it back to 2mb without trouble. The only guidelines I can give you are the ones in the postgres docs I linked, which recommend making the change that you made, so in principle it should be fine to leave, but let us know if you hit more issues. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6091) Lookup should parse dot in key consistently throughout
Title: Message Title John Duarte updated an issue Puppet / PUP-6091 Lookup should parse dot in key consistently throughout Change By: John Duarte QA Risk Assessment: High Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6180) Add acceptance test for Puppet CA/cert faces
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6180 Add acceptance test for Puppet CA/cert faces Change By: Eric Thompson Summary: Add acceptance test for Puppet CA face /cert faces Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6180) Add acceptance test for Puppet CA/cert faces
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6180 Add acceptance test for Puppet CA/cert faces Change By: Eric Thompson It was broken in Puppet 4 and no one new knew . Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6179) Puppet CA face broken
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6179 Puppet CA face broken Change By: Eric Thompson QA Risk Assessment: High Medium Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6091) Lookup should parse dot in key consistently throughout
Title: Message Title Henrik Lindberg commented on PUP-6091 Re: Lookup should parse dot in key consistently throughout John Duarte Depending on your shell, use of double quotes may be something different than what you think. Try quoting the entire key in single quotes: puppet lookup 'key."a.b.c".0' Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6180) Add acceptance test for Puppet CA face
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6180 Add acceptance test for Puppet CA face Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6179) Puppet CA face broken
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6179 Puppet CA face broken Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6179) Puppet CA face broken
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6179 Puppet CA face broken Change By: Eric Thompson QA Risk Assessment: High Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6180) Add acceptance test for Puppet CA face
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6180 Add acceptance test for Puppet CA face Change By: Eric Thompson Component/s: QA Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-40) REPL: replace readline dependency with editline (libedit)
Title: Message Title Henrik Lindberg commented on NPUP-40 Re: REPL: replace readline dependency with editline (libedit) merged to master: b0e5f43 Pulling this straight through to resolved. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4760) Service type should not retrieve ensure status when not needed
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4760 Service type should not retrieve ensure status when not needed Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Assessment: Low QA Risk Probability: Low QA Risk Severity: Low QA Highest Test Level Reason: covered by PR units QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6091) Lookup should parse dot in key consistently throughout
Title: Message Title John Duarte updated an issue Puppet / PUP-6091 Lookup should parse dot in key consistently throughout Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1385) Facter output of negative FixNum values from Ruby facts is incorrect with Ruby 2.2
Title: Message Title Michael Smith commented on FACT-1385 Re: Facter output of negative FixNum values from Ruby facts is incorrect with Ruby 2.2 Changes merged, still in progress for unit tests. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6059) File type does not fsync temp file before checksum verification during file creation
Title: Message Title Michael Smith updated an issue Puppet / PUP-6059 File type does not fsync temp file before checksum verification during file creation Change By: Michael Smith Fix Version/s: PUP 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6179) Puppet CA face broken
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-6179 Puppet CA face broken Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4760) Service type should not retrieve ensure status when not needed
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-4760 Service type should not retrieve ensure status when not needed Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6132) Puppet::Util::Plist should emit formatted plists
Title: Message Title Michael Smith updated an issue Puppet / PUP-6132 Puppet::Util::Plist should emit formatted plists Change By: Michael Smith Acceptance Criteria: Use Puppet to enable/disable a service (or manage something else with plists) and verify the updated plist file is properly formatted. Story Points: 1 Release Notes Summary: Puppet 4.4.0 introduced a new library for managing Mac plists, but as a side-effect it degraded formatting when updating those files. Restore prettier formatting. Sprint: Client 2016-05-04 Release Notes: Bug Fix Fix Version/s: PUP 4.5.0 Add Comment This message was sent by Atlassian JIRA
Jira (PUP-6091) Lookup should parse dot in key consistently throughout
Title: Message Title
John Duarte updated an issue
Puppet / PUP-6091
Lookup should parse dot in key consistently throughout
Change By:
John Duarte
Acceptance Criteria:
That the lookup CLI application and lookup function works the same way wrt: "dotted access" as in hiera.* use of dotted access "drills down" into data e.g. lookup('key , . subkey.0')* verbatim lookup is possible by quoting part of key e.g. lookup('key."a.b.c".0')* interpolation is possible using hiera syntax and semantic - thus making it possible to use a hiera data file without change
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Priscilla Piedra commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Hi Wyatt, Just wondering if there is a stablish max for facts, (eg. max of 500 characters) or objects in case of a structure fact, or can I store information with not limit? Will set max_stack_depth setting to 6MB or higher would cost any performace issues on db? is there a guideline for it? Thanks 2016-04-18 11:10 GMT-06:00 Wyatt Alt (JIRA) < – Ing.Priscilla Piedra Hidalgo Software Developer Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5588) Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times
Title: Message Title Ethan Brown commented on PUP-5588 Re: Monkey patch attempts to load same certs into OpenSSL::X509::Store objects multiple times Cherry-picked previous commit https://github.com/puppetlabs/puppet/commit/4373d41b3943cc7830277a37c3ba100d04037254 from PR 4469 to stable Rebased PR 4879 on stable - pushed to stable in https://github.com/puppetlabs/puppet/commit/482ca99eb4b6f181ed765b83acb648f3cdd2a05e Merged up to master in https://github.com/puppetlabs/puppet/commit/bbd4d58e285b6e5563f58994201b2e0e96f341ab Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6091) Lookup should parse dot in key consistently throughout
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-6091 Lookup should parse dot in key consistently throughout Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6136) newparam(:downgrade) for package type
Title: Message Title Matt Schuchard commented on PUP-6136 Re: newparam(:downgrade) for package type I could see two use cases for this parameter. The server is in an unknown state prior to the Puppet agent applying the catalog. Multiple modules which are not applied in the same catalog, but are being applied to the same server, are also managing the same package resource. Are either of these typical for well-constructed, managed, and monitored server environments? No. Are they typical at companies which have existed for over five years without a relevant greenfield? Yes. Do I work at one of those companies? Three guesses and the first two don't count. I recall seeing a ticket from back when yum downgrade was first implemented that had suggested the downgradeable feature and that suggestion was promptly shot down, otherwise I would consider that route. Maybe opinions have changed though. So I assume dnf inherits the implementation I did for yum based on the code I saw, rpm is also finished, apt I did the version installed accessing and assignment but not comparison, and dpkg I have not started working on but have poked around some. I too was focusing on the RedHat and Debian families' providers for now since those are something like ninety percent of servers/cloud. I would be all for the path of least resistance on this one, but I am not sure what that is. The custom function is an interesting idea, but I am not fond of the Puppetmaster caching it to make updating it difficult. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the
Jira (PUP-6095) Service provider shouldn't die if an smf service is in state "degraded"
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6095 Service provider shouldn't die if an smf service is in state "degraded" Change By: Kylo Ginsberg Sprint: Client 2016-05-04 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6095) Service provider shouldn't die if an smf service is in state "degraded"
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6095 Service provider shouldn't die if an smf service is in state "degraded" Change By: Kylo Ginsberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6095) Service provider shouldn't die if an smf service is in state "degraded"
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6095 Service provider shouldn't die if an smf service is in state "degraded" Change By: Kylo Ginsberg Fix Version/s: PUP 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-41) Implement the `type` function.
Title: Message Title Peter Huene assigned an issue to Peter Huene Native Puppet / NPUP-41 Implement the `type` function. Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2633) PQL & Hashes: Provide new path matching for hashes in AST & PQL
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2633 PQL & Hashes: Provide new path matching for hashes in AST & PQL Change By: Kenneth Barber Fix Version/s: PDB 4.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6025) Windows GetFileAttributes calls fail / symlink? may return false for a valid symlink
Title: Message Title Glenn Sarti commented on PUP-6025 Re: Windows GetFileAttributes calls fail / symlink? may return false for a valid symlink Can't depend on Jenkins build references as they are cleaned up periodically. Build artifacts are at; http://builds.puppetlabs.lan/puppet-agent/d74de3f5b2b599d89ee1087b5e69e9946963ddfb/artifacts/windows/ Confirmed that this includes the commits from this PR Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2632) PQL & Hashes: Create new 'inventory' endpoint for querying facts and trusted as hashes
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2632 PQL & Hashes: Create new 'inventory' endpoint for querying facts and trusted as hashes Change By: Kenneth Barber Fix Version/s: PDB 4.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5727) acceptance: cached catalog should allow encodings from utf8
Title: Message Title Eric Thompson commented on PUP-5727 Re: acceptance: cached catalog should allow encodings from utf8 2nd PR will fix CI against windows10 32bit Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6025) Windows GetFileAttributes calls fail / symlink? may return false for a valid symlink
Title: Message Title James Pogran commented on PUP-6025 Re: Windows GetFileAttributes calls fail / symlink? may return false for a valid symlink x64 build from CI https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/hiera/job/platform_hiera_pkg-van-ship_master/BUILD_TARGET=win-x64,SLAVE_LABEL=beaker/ws/ Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6136) newparam(:downgrade) for package type
Title: Message Title Kylo Ginsberg commented on PUP-6136 Re: newparam(:downgrade) for package type Matt Schuchard a few more thoughts/questions on this: ok good, glad my snippet above represents the desired behavior. But: why is this useful? I'm not contending, but I am trying to wrap my brain around the real-world scenarios. This feels unnecessarily non-deterministic, but I know I'm lacking the motivating use cases here. So that would help if we go this route, I'm thinking it would only apply to some providers, so we'd want to have a new feature (downgradeable?) on the package type. (That name isn't great, since it's not quite the opposite of upgradeable but still might be the best choice.) sorting this out for all package providers in core is probably overkill, but it would be worthwhile understanding how it would behave for "major" providers, e.g. maybe yum, dnf, rpm, apt, dpkg? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2632) PQL & Hashes: Create new 'inventory' endpoint for querying facts and trusted as hashes
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2632 PQL & Hashes: Create new 'inventory' endpoint for querying facts and trusted as hashes Change By: Kenneth Barber As per the proposal put forth in PDB-2356 ... we are looking to implement a new endpoint (for now we are calling it 'inventory') that is a little like 'factsets', but `facts` and `trusted` now just appear as keys with hashes at the top level.This is initially going to require some creative munging, as the implementation will need to co-exist with the current fact endpoints for the lifetime of v4. Ultimately the goal is to replace `facts`, `factsets` and `fact_contents` with this new implementation, once we have this in place and all the query capability these endpoints can probably be deprecated. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2634) PQL & Hashes: Provide hash projection capability for facts & resource params
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-2634 PQL & Hashes: Provide hash projection capability for facts & resource params Issue Type: Task Assignee: Unassigned Created: 2016/04/19 11:15 AM Priority: Normal Reporter: Kenneth Barber Alongside PDB-2632, we should provide a mechanism for projection leaf values inside a hash, for example on the new `inventory` and existing `resources` endpoint we have facts, trusted and parameters. The proposal is to use the dotted notation to express this projection in PQL (and some adequate way in AST also). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2634) PQL & Hashes: Provide hash projection capability for facts & resource params
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2634 PQL & Hashes: Provide hash projection capability for facts & resource params Change By: Kenneth Barber Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2633) PQL & Hashes: Provide new path matching for hashes in AST & PQL
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-2633 PQL & Hashes: Provide new path matching for hashes in AST & PQL Issue Type: Task Assignee: Unassigned Created: 2016/04/19 11:13 AM Fix Versions: PDB 4.1.0 Priority: Normal Reporter: Kenneth Barber Alongside PDB-2632, we also need to implement a mechanism within PQL and AST to provide hash querying for descending into the new hashes (facts & trusted) attached to the `inventory` endpoint. This should work a lot like the fact_contents regex match implementation, but without the need for name & value to be matched independently. Add Comment
Jira (PDB-2633) PQL & Hashes: Provide new path matching for hashes in AST & PQL
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2633 PQL & Hashes: Provide new path matching for hashes in AST & PQL Change By: Kenneth Barber Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1388) virtual fact is wrong sometimes when nested (vmware + lxc)
Title: Message Title Michael Smith updated an issue Facter / FACT-1388 virtual fact is wrong sometimes when nested (vmware + lxc) Change By: Michael Smith Sprint: Client Community Triage Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2632) PQL & Hashes: Create new 'inventory' endpoint for querying facts and trusted as hashes
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2632 PQL & Hashes: Create new 'inventory' endpoint for querying facts and trusted as hashes Change By: Kenneth Barber Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1388) virtual fact is wrong sometimes when nested (vmware + lxc)
Title: Message Title Michael Smith commented on FACT-1388 Re: virtual fact is wrong sometimes when nested (vmware + lxc) That appears to be because the checks virt-what uses are insufficient do distinguish layer order. This appears to duplicate FACT-1289, and be related to FACT-1244. A suggestion on how to handle this is: introduce a new fact to return an array of all virtual layers add some ordering logic to the virtual fact for things that can exist in other things (like containers are always higher layers than full virtual machines, and virtualbox would probably always be run within kvm). This may not be perfect, but should be accurate for more people. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2632) PQL & Hashes: Create new 'inventory' endpoint for querying facts and trusted as hashes
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-2632 PQL & Hashes: Create new 'inventory' endpoint for querying facts and trusted as hashes Issue Type: Task Assignee: Unassigned Created: 2016/04/19 11:07 AM Fix Versions: PDB 4.1.0 Priority: Normal Reporter: Kenneth Barber As per the proposal put forth in PDB-2356 ... we are looking to implement a new endpoint (for now we are calling it 'inventory') that is a little like 'factsets', but `facts` and `trusted` now just appear as keys with hashes at the top level. This is initially going to require some creative munging, as the implementation will need to co-exist with the current fact endpoints for the lifetime of v4. Add Comment
Jira (FACT-1043) Falsely reporting virtual as physical under Windows for OpenStack instance
Title: Message Title Michael Smith updated an issue Facter / FACT-1043 Falsely reporting virtual as physical under Windows for OpenStack instance Change By: Michael Smith Acceptance Criteria: Run on our Windows OpenStack hardware. Story Points: 1 Release Notes Summary: Facter incorrectly reported OpenStack-based Windows VMs as not virtual. This fix changes them to report as virtual, which the label 'openstack'. Sprint: Client 2016-05-04 Scrum Team: Client Platform Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (FACT-1043) Falsely reporting virtual as physical under Windows for OpenStack instance
Title: Message Title Michael Smith updated an issue Facter / FACT-1043 Falsely reporting virtual as physical under Windows for OpenStack instance Change By: Michael Smith Fix Version/s: FACT 3.1.6 Fix Version/s: FACT 2.4.7 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1388) virtual fact is wrong sometimes when nested (vmware + lxc)
Title: Message Title Matthew Gyurgyik commented on FACT-1388 Re: virtual fact is wrong sometimes when nested (vmware + lxc) Upstream discussion: https://www.redhat.com/archives/virt-tools-list/2016-April/msg00017.html In short, virt-what can return facts in any order. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6125) verbose agent runs result data being sent console and syslog
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-6125 verbose agent runs result data being sent console and syslog Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6125) verbose agent runs result data being sent console and syslog
Title: Message Title Michael Smith commented on PUP-6125 Re: verbose agent runs result data being sent console and syslog Charlie Sharpsteen have any feedback on this change? I also plan to send out a note to #puppet or #puppet-dev. It seems undesirable to have verbose/debug/show-diff going to syslog as a default, as they're more likely to contain secrets. For anyone currently running with verbose or show-diff enabled, this could be a non-obvious change that will need to be pointed out in release notes. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6125) verbose agent runs result data being sent console and syslog
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-6125
verbose agent runs result data being sent console and syslog
Change By:
Michael Smith
The documentation states{quote}* --logdest: Where to send log messages. Choose between 'syslog' (the POSIX syslog service), 'eventlog' (the Windows Event Log), 'console', or the path to a log file. If debugging or verbosity is enabled, this defaults to 'console'. Otherwise, it defaults to 'syslog' on POSIX systems and 'eventlog' on Windows.{quote}|| Flags || Syslog || Console ||| None | X | || --logdest console | | X || --logdest syslog | X | || --verbose | X | X || --verbose --logdest console | | X || --test | X | X || --test --verbose | X | X |This becomes a problem when the --test option is used. --test expands and sets show_diff=true --verbose which means diff output will get logged to syslog and the console.The expected result is to send output only to the console, not syslog. This is a concern, because --test enables show-diff, which can contain secrets (such as passwords) that should not be printed. As a default, this suggests we should not log show-diff and verbose/debug output to more permanent locations such as syslog/eventlog.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit
Jira (FACT-1043) Falsely reporting virtual as physical under Windows for OpenStack instance
Title: Message Title Michael Smith commented on FACT-1043 Re: Falsely reporting virtual as physical under Windows for OpenStack instance This should also be addressed for Facter 3. I plan to put up a PR. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result
Title: Message Title Branan Riley commented on FACT-1284 Re: Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result I've got a leatherman PR up for this. Once that's merged and released, the Facter PR can be wrapped up and merged as well. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6025) Windows GetFileAttributes calls fail / symlink? may return false for a valid symlink
Title: Message Title Glenn Sarti assigned an issue to Ethan Brown Puppet / PUP-6025 Windows GetFileAttributes calls fail / symlink? may return false for a valid symlink Change By: Glenn Sarti Assignee: James Pogran Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2631) PDB is incapable of efficiently storing giant facter facts
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2631 PDB is incapable of efficiently storing giant facter facts Issue Type: Bug Assignee: Unassigned Created: 2016/04/19 8:38 AM Priority: Normal Reporter: Wyatt Alt facter's disks, partitions, and mountpoints facts all cause big problems for PDB in cases such as SANs with thousands of mountpoints. This is related to FACT-1345 but fundamentally it's an issue with the way we store structured facts. I'm not sure what the fix is right now, but we should be able to store anything facter sends us. this has been brought up on the users list here: https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/puppet-users/ZUYSvX4aRHg/kc_jxFbHBAAJ and in a couple of recent PE tickets. Add Comment
Jira (PDB-2630) puppetdb module fails with newer postgresql modules
Title: Message Title David Schmitt moved an issue PuppetDB / PDB-2630 puppetdb module fails with newer postgresql modules Change By: David Schmitt Component/s: puppetdb Component/s: Module Key: MODULES PDB - 3214 2630 Project: Forge Modules PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2628) PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted'
Title: Message Title Robert Heinzmann commented on PDB-2628 Re: PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted' This file was automatically generated by the puppetdb module. — master: facts: terminus: puppetdb cache: yaml Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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.
