Jira (PDB-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Wyatt Alt commented on PDB-3058 Re: Report not being stored in PuppetDB due to Unicode Error Jacky Leung Okay, thanks for confirming that. I'll pick this up again tomorrow (I'm US pacific) and get back to you with some more targeted queries. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Jacky Leung commented on PDB-3058 Re: Report not being stored in PuppetDB due to Unicode Error the stored reports don't have the binary data Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Jacky Leung commented on PDB-3058 Re: Report not being stored in PuppetDB due to Unicode Error hm.. they both return zero puppetdb=> select count(*) from reports where metrics_json is not null puppetdb-> ; count --- 0 (1 row) puppetdb=> select count(*) from reports where logs_json is not null; count --- 0
Jira (FACT-1510) Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows
Title: Message Title Rob Reynolds assigned an issue to Unassigned Facter / FACT-1510 Facts from symlinked folders (facts.d / modules) don't work correctly in Vagrant on Windows Change By: Rob Reynolds Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5027) metadata.json is parsed twice
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5027 metadata.json is parsed twice Change By: Eric Thompson QA Risk Assessment Reason: internal changes, covered by existing tests Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5027) metadata.json is parsed twice
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5027 metadata.json is parsed twice Change By: Eric Thompson QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5954) Change deprecation from PUP-2695 (merge class) to error
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5954 Change deprecation from PUP-2695 (merge class) to error Change By: Eric Thompson QA Risk Assessment Reason: deprecation, covered by unit tests Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5954) Change deprecation from PUP-2695 (merge class) to error
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5954 Change deprecation from PUP-2695 (merge class) to error Change By: Eric Thompson QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7091) acceptance: "hiera3_backend" can be used for custom backends in hiera5 config
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7091 acceptance: "hiera3_backend" can be used for custom backends in hiera5 config Change By: Eric Thompson QA Risk Assessment: Needs Assessment Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PDOC-144) acceptance: expand matrix to include windows
Title: Message Title Eric Thompson updated an issue Puppet Strings / PDOC-144 acceptance: expand matrix to include windows Change By: Eric Thompson QA Risk Assessment: Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6811) Acceptance tests for puppet-server hocon vendoring
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6811 Acceptance tests for puppet-server hocon vendoring Change By: Eric Thompson QA Risk Assessment: Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7081) acceptance: defined Objects in catalog and used on the agent/apply
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7081 acceptance: defined Objects in catalog and used on the agent/apply Change By: Eric Thompson QA Risk Assessment: Needs Assessment Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7008) acceptance: hiera v5 can use hiera v3 config and datafiles
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7008 acceptance: hiera v5 can use hiera v3 config and datafiles Change By: Eric Thompson QA Risk Assessment: Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4933) Remove cfacter setting
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4933 Remove cfacter setting Change By: Eric Thompson QA Risk Assessment Reason: code/feature removal Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4933) Remove cfacter setting
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4933 Remove cfacter setting Change By: Eric Thompson QA Risk Assessment: No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6864) non existing env causes undefined method `environment_data_provider' for nil:NilClass error
Title: Message Title Eric Thompson commented on PUP-6864 Re: non existing env causes undefined method `environment_data_provider' for nil:NilClass error ping Ben Ford, or anyone else. anyone know how to reproduce this issue? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7021) Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module
Title: Message Title Moses Mendoza assigned an issue to Unassigned Puppet / PUP-7021 Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module Change By: Moses Mendoza Assignee: Moses Mendoza Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5954) Change deprecation from PUP-2695 (merge class) to error
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5954 Change deprecation from PUP-2695 (merge class) to error Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7119) Acceptance: utf-8 characters in module describe block (puppet describe)
Title: Message Title Sean Griffin created an issue Puppet / PUP-7119 Acceptance: utf-8 characters in module describe block (puppet describe) Issue Type: Improvement Assignee: Sean Griffin Created: 2017/01/19 2:30 PM Priority: Normal Reporter: Sean Griffin Acceptance test to verify the command 'puppet describe' work correctly when there are utf-8 characters in the module's descritpion. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7118) Acceptance: utf-8 characters in function args
Title: Message Title Sean Griffin created an issue Puppet / PUP-7118 Acceptance: utf-8 characters in function args Issue Type: Improvement Assignee: Sean Griffin Created: 2017/01/19 2:11 PM Priority: Normal Reporter: Sean Griffin Acceptance test to verify correct behavior when utf-8 characters are used in puppet function arguments. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7117) Acceptance: utf-8 characters in file resource
Title: Message Title Sean Griffin created an issue Puppet / PUP-7117 Acceptance: utf-8 characters in file resource Issue Type: Improvement Assignee: Sean Griffin Created: 2017/01/19 1:52 PM Priority: Normal Reporter: Sean Griffin Acceptance test to verify correct behavior when utf-8 characters are used in a file resource. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7021) Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7021 Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module Change By: Moses Mendoza Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7021) Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7021 Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module Change By: Moses Mendoza Summary: Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7021) Prevent incompatible encodings reaching Puppet::Parameter#format
Title: Message Title
Moses Mendoza updated an issue
Puppet / PUP-7021
Prevent incompatible encodings reaching Puppet::Parameter#format
Change By:
Moses Mendoza
[Puppet::Parameter#format|https://github.com/puppetlabs/puppet/blob/83909490a047b15f7fd4ca4f72490112740a7aec/lib/puppet/parameter.rb#L541-L543] currently does not check if the strings it is interpolating are of incompatible encodings.This method is used, among other places, in the resource harness when [setting the message for failed change events|https://github.com/puppetlabs/puppet/blob/83909490a047b15f7fd4ca4f72490112740a7aec/lib/puppet/transaction/resource_harness.rb#L147-L149]. If the strings contain incompatible encodings (i.e., they cannot be concatenated) the format method will fail, the event will not contain a message, and then it will fail to be logged.This also results in error messages that look like this:{code}Error: /Stage[main]/Main/Node[ubuntu16.localdomain]/User[foo]: Could not evaluate: Puppet::Util::Log requires a message{code} *Notes** After diving further into this, this form of problem is scattered all through puppet - the concatenation of strings without regard to encoding. The deeper problem is that strings are entering the system in incompatible encodings to begin with. The problem-area that gave rise to this specific bug is the nameservice provider, and specifically it's reliance on the {{Etc}} module in ruby, which can return strings in default external encoding which are then sent around puppet to be compared and munged with utf-8 strings. Thus this ticket is now re-scoped from it's original (smaller context) to include a broader fix of setting strings incoming from {{Etc}} to utf-8.*In Scope** Anywhere we take strings in the from the {{Etc}} module in a provider, these strings should have UTF-8 encoding
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7021) Prevent incompatible encodings reaching Puppet::Parameter#format
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7021 Prevent incompatible encodings reaching Puppet::Parameter#format Change By: Moses Mendoza Acceptance Criteria: Tests pass that show that Puppet::Parameter#format can accept strings with incompatible encodings and either concatenate them safely or fail gracefully - ideally with Given a message that will still result linux host in a log being generated in the case of Puppet::Transaction::ResourceHarness#sync_if_needed non-utf8 locale, such as ja_JP.EUC-JP, a user can have its groups modified from a utf-8 to a different utf-8 name Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7021) Prevent incompatible encodings reaching Puppet::Parameter#format
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7021 Prevent incompatible encodings reaching Puppet::Parameter#format Change By: Moses Mendoza Summary: Handle Prevent incompatible encodings in reaching Puppet::Parameter#format Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2524) Display replication status in the built-in PDB dashboard
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-2524 Display replication status in the built-in PDB dashboard Change By: Russell Mull Assignee: Arafat Mohamed Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2524) Display replication status in the built-in PDB dashboard
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2524 Display replication status in the built-in PDB dashboard Change By: Russell Mull Sprint: HA Accepted 2017-01-25 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1552) Add 'disks' fact resolver for AIX
Title: Message Title Branan Riley assigned an issue to Unassigned Facter / FACT-1552 Add 'disks' fact resolver for AIX Change By: Branan Riley Assignee: Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7073) Comparisons between SELinux file categories should always translate to the numeric version
Title: Message Title Branan Riley assigned an issue to Unassigned Puppet / PUP-7073 Comparisons between SELinux file categories should always translate to the numeric version Change By: Branan Riley Assignee: Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7073) Comparisons between SELinux file categories should always translate to the numeric version
Title: Message Title Branan Riley commented on PUP-7073 Re: Comparisons between SELinux file categories should always translate to the numeric version Trevor Vaughan I've got a PR open for what I think is a reasonable fix (assuming my test case above is valid) https://github.com/puppetlabs/puppet/pull/5513 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5954) Change deprecation from PUP-2695 (merge class) to error
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5954 Change deprecation from PUP-2695 (merge class) to error Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Wyatt Alt commented on PDB-3058 Re: Report not being stored in PuppetDB due to Unicode Error Jacky Leung I spent some time trying to reproduce your issue this morning but haven't been able to yet. Can you verify that the two queries here return counts of zero? psql -d puppetdb -c 'select count(*) from reports where metrics_json is not null' psql -d puppetdb -c 'select count(*) from reports where logs_json is not null' If either of those return nonzero counts, it means the database wasn't actually cleared on the move to 4.2.0. I think the PR linked in this ticket should fix the problem, though I can't say how quickly it'll be released. To get around this you'll need to figure out where the null byte is coming from. You might be able to enable the yaml store for reports (https://docs.puppet.com/puppet/latest/configuration.html#reports), and then once your nodes have checked in, grep through the directory for the word "binary". This will indicate where you've got binary data in the report. When I stick a null byte in one of my reports, I get data that looks like this: https://gist.github.com/wkalt/db5aa9b9d16a5ca4e9f3f873b8b4886d You may be able to grep for that base64 encoded string directly and get lucky, though I could imagine that depending on the representation. Once you find the null byte, it should be pretty easy to backtrack it to a manifest. Add Comment
Jira (PUP-4947) Remove special handling of reserved keywords 'application', 'consumes', 'produces'
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-4947 Remove special handling of reserved keywords 'application', 'consumes', 'produces' Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4947) Remove special handling of reserved keywords 'application', 'consumes', 'produces'
Title: Message Title Thomas Hallgren commented on PUP-4947 Re: Remove special handling of reserved keywords 'application', 'consumes', 'produces' Merged to 5.0 at 33dd35a. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3170) Cap integer and float sizes
Title: Message Title Thomas Hallgren commented on PUP-3170 Re: Cap integer and float sizes Henrik Lindberg, that check uses predefined constants: MAX_INTEGER = 0x7fff MIN_INTEGER = -0x8000 I think that's clear enough. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3170) Cap integer and float sizes
Title: Message Title Henrik Lindberg commented on PUP-3170 Re: Cap integer and float sizes As you say, that cap alone is not enough. We could do it in serialization. We could also do it on all assignments (scope, parameters, calls, setting attributes, inclusion in array and hash etc) as that would take place much closer to the actual problem. The serialization test could actually be done by checking if the value is a Bignum since a FixInt cannot be outside the bounds of MIN/MAX Integer. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7116) Make gettext-setup optional
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-7116 Make gettext-setup optional Issue Type: Task Assignee: Unassigned Created: 2017/01/19 11:45 AM Fix Versions: PUP 4.9.0 Priority: Blocker Reporter: Maggie Dreyer We cannot require that puppetserver provide the gettext-setup gem for the 1.9.0 release, so we need to update Puppet to behave correctly even when the gem isn't present. This involves stubbing the _() method used extract strings and pull in translations. Add Comment
Jira (PUP-7115) Un-vendor semantic_puppet gem for Puppet 5
Title: Message Title Ethan Brown created an issue Puppet / PUP-7115 Un-vendor semantic_puppet gem for Puppet 5 Issue Type: Task Affects Versions: PUP 4.9.0 Assignee: Unassigned Created: 2017/01/19 11:44 AM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Ethan Brown In PUP-7114 the semantic_puppet gem was re-vendored into the Puppet repo to prevent packaging conflicts. In Puppet 5, there will be more latitude to introduce a breaking packaging change that must be coordinated with a server release - and at that point the work from PUP-7114 can be reverted. Add Comment
Jira (PUP-7116) Make gettext-setup optional
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-7116 Make gettext-setup optional Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7114) Re-vendor semantic_pupppet gem
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-7114
Re-vendor semantic_pupppet gem
Change By:
Ethan Brown
Channeling [~moses] from https://groups.google.com/a/puppet.com/forum/#!topic/team-agent-and-platform/_1q5BWWyvxk{quote}BackgroundIn PA-621, puppet-agent added a package conflict with puppet-server <2.7.2 and pe-puppet-server < 2017.0.1.3. This was required becausepuppet added new vendored gem dependencies, and only puppet-server >=2.7.2 satisfies those dependencies too. For even more context, see"extra context" at the bottom.{quote}One approach that has been settled on is to:* Re-vendor the {{semantic_puppet}} gem so that the {{puppet-server}} packages don't need to have the gem installed (and to actually use later specify it as a gem dependency in Puppet 5 when there is greater latitude to make compatibility changes )* See if the {{hocon}} gem is already properly guarded as a Hiera backend for when the gem is missing (it looks to be already)* Make it so that gettext will work / load when the gem is present, but will not fail to load when the gem is not present (on older Puppet servers that don't have the gems vendored, we will stub the {{_}} function)This ticket covers vendoring version {{0.1.4}} of the {{semantic_puppet}} gem back into the codebase Puppet repository . Rather than reverting all of the language related changes that were originally proposed in https://github.com/puppetlabs/puppet/pull/5094 and that ultimately landed in https://github.com/puppetlabs/puppet/pull/5399, it seems simpler to just grab the same code thats present in the gem and include that temporarily , removing the references to external dependencies at the same time .
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7114) Re-vendor semantic_pupppet gem
Title: Message Title Ethan Brown created an issue Puppet / PUP-7114 Re-vendor semantic_pupppet gem Issue Type: Task Assignee: Unassigned Created: 2017/01/19 11:35 AM Fix Versions: PUP 4.9.0 Priority: Blocker Reporter: Ethan Brown Channeling Moses Mendoza from https://groups.google.com/a/puppet.com/forum/#!topic/team-agent-and-platform/_1q5BWWyvxk Background In PA-621 , puppet-agent added a package conflict with puppet-server < 2.7.2 and pe-puppet-server < 2017.0.1.3. This was required because puppet added new vendored gem dependencies, and only puppet-server >= 2.7.2 satisfies those dependencies too. For even more context, see "extra context" at the bottom. One approach that has been settled on is to: Re-vendor the semantic_puppet gem so that the puppet-server packages don't need to have the gem installed (and to actually use a dependency in Puppet 5) See if the hocon gem is already properly guarded as a Hiera backend for when the gem is missing (it looks to be already)
Jira (PDB-3219) Deleting from reports spends most of the time enforcing a constraint on certnames
Title: Message Title Nick Walker updated an issue PuppetDB / PDB-3219 Deleting from reports spends most of the time enforcing a constraint on certnames Change By: Nick Walker Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7079) Windows scheduled_task spec failures on puppet (master)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7079 Windows scheduled_task spec failures on puppet (master) Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7079) Windows scheduled_task spec failures on puppet (master)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7079 Windows scheduled_task spec failures on puppet (master) Change By: Kenn Hussey Fix Version/s: PUP 4.8.2 Fix Version/s: PUP 4.8.z Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3170) Cap integer and float sizes
Title: Message Title Thomas Hallgren commented on PUP-3170 Re: Cap integer and float sizes The Pcore serializer already caps integer values with the following check: raise SerializationError, 'Integer out of bounds' if value > MAX_INTEGER || value < MIN_INTEGER but I'm not sure that this cap alone is sufficient. The serializer is normally not involved when sending catalogs or reports so similar checks will probably need to go into some #to_data_hash methods that are used when their respective Pson is generated. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7113) Implement forcelocal in AIX providers
Title: Message Title Adam Bottchen created an issue Puppet / PUP-7113 Implement forcelocal in AIX providers Issue Type: New Feature Affects Versions: PUP 4.8.1 Assignee: Unassigned Created: 2017/01/19 8:43 AM Priority: Normal Reporter: Adam Bottchen Currently, the forcelocal attribute on user and group resources only works on Linux based systems where libuser is available. However, other operating systems, such as AIX, would also benefit from having user and group resources prevented from reaching out to LDAP or AD backends. This causes problems primarily when a user or group resource is applied when there is a user or group with the same name in the backend database. The provider will error out, and the agent run will fail. AIX does provide the "-R files" flag for many of its user and group management commands. It may be possible to leverage this to implement a forcelocal option without the presence of libuser. Add Comment
Jira (PDB-3256) Drop PQL experimental status
Title: Message Title Wyatt Alt commented on PDB-3256 Re: Drop PQL experimental status Ryan Coleman There's an old confluence page here: https://confluence.puppetlabs.com/display/enterprise/Search+-+PQL+for+PDB+API+CLI+Feature+Page , but I don't know that it's worth reviving since it has a lot of out of date information. I was assuming that we had a place where group feature ownership was defined – it seems like that should exist, but if it doesn't I suppose this is probably okay. The people I'm aware of that would be likely to care are on this ticket already. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7079) Windows scheduled_task spec failures on puppet (master)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7079 Windows scheduled_task spec failures on puppet (master) Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3256) Drop PQL experimental status
Title: Message Title Wyatt Alt commented on PDB-3256 Re: Drop PQL experimental status Beth Cornils to my knowledge ownership by the Enterprise group was just informally decided on yesterday. If it's not written down somewhere we should write it down, then get sign-off from Ken on dropping the experimental status (since I'm not sure where the next-gen stuff is at in relation to this), and after that we're good to go afaik. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7112) puppet master startup errors
Title: Message Title weihw created an issue Puppet / PUP-7112 puppet master startup errors Issue Type: New Feature Affects Versions: None Assignee: Unassigned Created: 2017/01/19 7:02 AM Priority: Normal Reporter: weihw err: /File[/var/lib/puppet/yaml]: Could not evaluate: Could not find group puppet err: /File[/var/lib/puppet/rrd]: Could not evaluate: Could not find group puppet err: /File[/var/lib/puppet/reports]: Could not evaluate: Could not find group puppet err: /File[/var/log/puppet]: Could not evaluate: Could not find group puppet notice: /File[/var/log/puppet/masterhttp.log]: Dependency File[/var/log/puppet] has fail ures: true warning: /File[/var/log/puppet/masterhttp.log]: Skipping because of failed dependencies err: /File[/var/lib/puppet/bucket]: Could not evaluate: Could not find group puppet err: /File[/var/lib/puppet/server_data]: Could not evaluate: Could not find group puppet Could not prepare for execution: Got 6 failure(s) while initializing: Could not evaluate: Coul d not find group puppet; Could not evaluate: Could not find group puppet; Could not evaluate: Could not find group puppet; Could not evaluate: Could not find group puppet; Could not evalua te: Could not find group puppet; Could not evaluate: Could not find group puppet
Jira (PUP-3170) Cap integer and float sizes
Title: Message Title Henrik Lindberg commented on PUP-3170 Re: Cap integer and float sizes The BigDecimal is never really a problem unless someone writes a function that returns BigDecimal. If they do there are plenty of different kinds of types of data that are not represented in the Puppet Type system and that are illegal to use. Don't think we need to do anything for BigDecimal as there is no automatic promotion made by Ruby when a value overflows the size of a 64 bit floating point value. For BigNum it is more complicated. If we make it an instance of type Ruby it is still an Any and can be passed around. It then becomes a problem when serializing (using pcore or some of the hash to yaml/json variants). If we simply error at serialization time this will occur very far from where the error occurred and a user would not know what to do. We could modify all arithmetic operations in the evaluator to check for overflow and then raise an error. That would however make it impossible to do large arithmetic that is scaled down at the end, for example MAX_INT + MAX_INT / 4 would error on the + where it is now results in FixNum MAX_INT/2. We still have no control over what happens in functions. We could try to monkeypatch Bignum and forever cause problems for all 3d party code we are trying to use. (don't even go there) We could check on assignment - when a variable is bound in scope, and when they are set as attributes in resources. We would however need to do that without using the type system as we would otherwise need to have some kind of type that is not an Any. We would also need to always check the return type of functions (we now optimize the Any return type by not doing any type checking). All of the above have performance implications. The other option is to embrace Bignum and add it to the type system as a kind of Integer, We then have the problem of representing it should it need to be serialized. It would need to be an Object as it cannot be represented natively directly in most serialization formats. Attacking this at serialization time may be the most pragmatic. We should not serialize any Ruby instance anyway as that is a security concern; only what is known and mapped to Pcore. Trying to do this for the current pson/json/yaml would not have good performance (we need to scan all values/attributes etc). Maybe leave this to Pcore serialization to sort out? Ping Thomas Hallgren - opinions what to do? Add Comment
Jira (PUP-7006) `puppet lookup` subcommand can't take multiple keys as arguments
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7006 `puppet lookup` subcommand can't take multiple keys as arguments Change By: Henrik Lindberg Sprint: PDE 2017-02-08 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3265) module always requires a local postgresql
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3265 module always requires a local postgresql Issue Type: Bug Assignee: Unassigned Created: 2017/01/19 1:17 AM Priority: Normal Reporter: gepetto-bot Currently this module still requires a local postgresql server even when connecting to a remote one. As it always tries to manage a local postgresql db, this change fixes that problem. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
