Jira (PDB-4312) report_event table can contain duplicates during hashing in migration 67
Title: Message Title Erik Hansen updated an issue PuppetDB / PDB-4312 report_event table can contain duplicates during hashing in migration 67 Change By: Erik Hansen Labels: customer0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9467) Type validation fails when there is no type - needs human-readable error message
Title: Message Title Erik Hansen updated an issue Puppet / PUP-9467 Type validation fails when there is no type - needs human-readable error message Change By: Erik Hansen Summary: Type validation fails when there is no type - needs human-readable error message Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9467) Type validation fails when there is no type
Title: Message Title
Erik Hansen created an issue
Puppet / PUP-9467
Type validation fails when there is no type
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
trace.txt
Created:
2019/01/28 10:35 AM
Priority:
Normal
Reporter:
Erik Hansen
A class with an optional parameter with no type that defaults to undef isn't handled well by /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/type_mismatch_describer.rb For example if I have a class:
class test::validation (
Optional $whatever = undef
){
notice($whatever)
}
Jira (PUP-9436) Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Title: Message Title Erik Hansen updated an issue Puppet / PUP-9436 Exported resources in Puppet 6.x are realized with Binary values from Eyaml Change By: Erik Hansen Attachment: 5_catalog.json Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9436) Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Title: Message Title Erik Hansen updated an issue Puppet / PUP-9436 Exported resources in Puppet 6.x are realized with Binary values from Eyaml Change By: Erik Hansen Attachment: 6_catalog.json Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9436) Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Title: Message Title
Erik Hansen updated an issue
Puppet / PUP-9436
Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Change By:
Erik Hansen
Comment:
I've reproduced this now. The user resource in the cached 6.0.4 catalog looks like this:{code:json}"parameters": { "ensure": "present", "password": { "__ptype": "Binary", "__pvalue": "c2VjcmV0X3Bhc3MxMjM=" } },{code}Whereas the 5.5.4 catalog has:{code:json}"parameters": { "ensure": "present", "password": "secret_pass123" },{code}Additional details: When the 5.5.4 applies the 6.0.4 cached catalog there is an error:{noformat}Error: Could not send report: Error 400 on SERVER: Bad Request: The request body is invalid: Could not intern from json: Internal Error: Puppet Context ':loaders' missing{noformat}The catalog applies any changes, but the report isn't sentThere's a similar error if the 6.0.4 agent tries to apply the 6.0.4 cached catalog:{noformat}Error: Cached catalog for hmlilodi28f6x5y.delivery.puppetlabs.net failed: Could not parse JSON data for catalog hmlilodi28f6x5y.delivery.puppetlabs.net: Could not intern from rich_data_json: Internal Error: Puppet Context ':loaders' missing{noformat}In this case the cached catalog cannot be applied and the agent requests a new one.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9436) Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Title: Message Title Erik Hansen updated an issue Puppet / PUP-9436 Exported resources in Puppet 6.x are realized with Binary values from Eyaml Change By: Erik Hansen Attachment: 6_catalog.json Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9436) Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Title: Message Title Erik Hansen updated an issue Puppet / PUP-9436 Exported resources in Puppet 6.x are realized with Binary values from Eyaml Change By: Erik Hansen Attachment: 5_catalog.json Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9436) Exported resources in Puppet 6.x are realized with Binary values from Eyaml
Title: Message Title
Erik Hansen commented on PUP-9436
Re: Exported resources in Puppet 6.x are realized with Binary values from Eyaml
I've reproduced this now. The user resource in the cached 6.0.4 catalog looks like this:
"parameters": {
"ensure": "present",
"password": {
"__ptype": "Binary",
"__pvalue": "c2VjcmV0X3Bhc3MxMjM="
}
},
Whereas the 5.5.4 catalog has:
"parameters": {
"ensure": "present",
"password": "secret_pass123"
},
Additional details: When the 5.5.4 applies the 6.0.4 cached catalog there is an error:
Jira (PDB-4199) Puppet query - Issue with contents of arrays and type
Title: Message Title Erik Hansen updated an issue PuppetDB / PDB-4199 Puppet query - Issue with contents of arrays and type Change By: Erik Hansen Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4199) Puppet query - Issue with contents of arrays and type
Title: Message Title
Erik Hansen created an issue
PuppetDB / PDB-4199
Puppet query - Issue with contents of arrays and type
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/11/28 2:05 PM
Labels:
maintenance
Priority:
Normal
Reporter:
Erik Hansen
There seems to be an issue with the contents of Arrays and interpreting the type when processing a query. For instance this query worked in 2016.4.13:
curl -X POST -H 'Content-Type:application/json' http://localhost:8080/pdb/query/v4/nodes -d '{"query": ["in", ["fact", "uptime_seconds"], ["array",["2.0","150.0", "30"]]]}'
However in 2018.1.4 it returns an error: "All values in array must be the same type." The example comes from documentation here: https://puppet.com/docs/puppetdb/6.0/api/query/v4/ast.html#array
Jira (PUP-9305) Built-in unique function behaves differently with undef
Title: Message Title Erik Hansen commented on PUP-9305 Re: Built-in unique function behaves differently with undef Henrik Lindberg - undef for undef is I think what we want, since that's what the stdlib function does – unless you think this is an issue with my code that was masked by the stdlib version? Some added context - we originally saw this in some acceptance testing which caused a hard failure with the new function, the stdlib function would pass the test without issues. More context here: https://github.com/puppetlabs/puppet_metrics_dashboard/pull/11 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9305) Built-in unique function behaves differently with undef
Title: Message Title
Erik Hansen updated an issue
Puppet / PUP-9305
Built-in unique function behaves differently with undef
Change By:
Erik Hansen
The unique function introduced in PUP-7620 introduces a possible breaking change, as it behaves differently than the stdlib function when passed an undef value.h5. Reproduction:With the following manifest, unique.pp: {code:java} $unique = unique($this_is_undef)notice($unique){code}With stdlib installed (puppet apply unique.pp):{code:java} Warning: Unknown variable: 'this_is_undef'. at /root/unique.pp:1:22Notice: Scope(Class[main]): Notice: Compiled catalog for pe-2016413-master.puppetdebug.vlan in environment production in 0.19 secondsNotice: Applied catalog in 0.33 seconds{code}Without stdlib installed:{code:java} Warning: Unknown variable: 'this_is_undef'. (file: /root/unique.pp, line: 1, column: 22)Error: Evaluation Error: Error while evaluating a Function Call, 'unique' expects one of: (String string, Callable[String] block?) rejected: parameter 'string' expects a String value, got Undef (Hash hash, Callable[Any] block?) rejected: parameter 'hash' expects a Hash value, got Undef (Array array, Callable[Any] block?) rejected: parameter 'array' expects an Array value, got Undef (Iterable iterable, Callable[Any] block?) rejected: parameter 'iterable' expects an Iterable value, got Undef (file: /root/unique.pp, line: 1, column: 15) on node pe-201813-master.puppetdebug.vlan{code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9305) Built-in unique function behaves differently with undef
Title: Message Title Erik Hansen created an issue Puppet / PUP-9305 Built-in unique function behaves differently with undef Issue Type: Bug Assignee: Unassigned Created: 2018/11/07 11:34 AM Priority: Normal Reporter: Erik Hansen The unique function introduced in PUP-7620 introduces a possible breaking change, as it behaves differently than the stdlib function when passed an undef value. Reproduction: With the following manifest, unique.pp: $unique = unique($this_is_undef) notice($unique) With stdlib installed (puppet apply unique.pp): Warning: Unknown variable: 'this_is_undef'. at /root/unique.pp:1:22 Notice: Scope(Class[main]):
Jira (PDB-4174) Encoding issue submitting facts from package inventory
Title: Message Title Erik Hansen updated an issue PuppetDB / PDB-4174 Encoding issue submitting facts from package inventory Change By: Erik Hansen Affects Version/s: PDB 5.2.4 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4174) Encoding issue submitting facts from package inventory
Title: Message Title Erik Hansen updated an issue PuppetDB / PDB-4174 Encoding issue submitting facts from package inventory Change By: Erik Hansen Security: Internal Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4129) PQL query with long filter causes Puppetdb web services to restart
Title: Message Title Erik Hansen moved an issue PuppetDB / PDB-4129 PQL query with long filter causes Puppetdb web services to restart Change By: Erik Hansen Affects Version/s: PE 2018.1.3 Key: PE PDB - 25265 4129 Project: Puppet Enterprise [Internal] PuppetDB Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Erik Hansen updated an issue Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Erik Hansen CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Erik Hansen commented on PUP-9041 Re: AIX nim provider can't be used on a NIM master IBM documentation on the nim command can be found here: https://www.ibm.com/support/knowledgecenter/en/ssw_aix_71/com.ibm.aix.install/nim_op_cust.htm Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title
Erik Hansen updated an issue
Puppet / PUP-9041
AIX nim provider can't be used on a NIM master
Change By:
Erik Hansen
Environment:
Platform: AIX 7.2
When using a package resource and the nim provider, the resource cannot be applied to a NIM master. The error received is:{noformat}Error: Failed to apply catalog: Execution of '/usr/sbin/nimclient -o showres -a installp_flags=L -a resource=lpp_resource' returned 147: 0042-147 nimclient: this command may not be executed on a NIM master.{noformat}This can be reproduced with a simple resource such as:{code:java}package { $install_pkgs: ensure => latest, provider => nim,}{code}On a NIM master you cannot use the nimclient command, the command would have to be:{noformat}/usr/sbin/nim -o showres -a installp_flags=L lpp_resource{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title
Erik Hansen created an issue
Puppet / PUP-9041
AIX nim provider can't be used on a NIM master
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/08/03 12:35 PM
Priority:
Normal
Reporter:
Erik Hansen
When using a package resource and the nim provider, the resource cannot be applied to a NIM master. The error received is:
Error: Failed to apply catalog: Execution of '/usr/sbin/nimclient -o showres -a installp_flags=L -a resource=lpp_resource' returned 147: 0042-147 nimclient: this command may not be executed on a NIM master.
This can be reproduced with a simple resource such as:
package { $install_pkgs:
ensure => latest,
provider => nim,
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Erik Hansen updated an issue Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Erik Hansen Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1870) Stdout in facts invalidates formatted output (yaml/json)
Title: Message Title Erik Hansen updated an issue Facter / FACT-1870 Stdout in facts invalidates formatted output (yaml/json) Change By: Erik Hansen Summary: Errors are printed to stdout Stdout in facts invalidates formatted output (yaml/json) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1870) Errors are printed to stdout
Title: Message Title
Erik Hansen updated an issue
Facter / FACT-1870
Errors are printed to stdout
Change By:
Erik Hansen
Errors in facter When there is output are written to stdout . This is in facts it creates a problem in particular with the format options:{code:java}Facter.add('test') do confine :kernel => 'Linux' begin test = 'nomatch' test = Facter.value(:doesntexist).strip()setcode { test }rescue Exception => ex puts "#{File.basename(__FILE__)} - ruby fact threw an exception: #{ex}" end end{code}Output:{code:java}# facter -p -j testtest.rb - ruby fact threw an exception: undefined method `strip' for nil:NilClass{ "test": ""}{code}Desired Outcome:using --json or --yaml should print the valid format even if there are errors messages sent to stdout .
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it,
Jira (FACT-1870) Errors are printed to stdout
Title: Message Title Erik Hansen moved an issue Facter / FACT-1870 Errors are printed to stdout Change By: Erik Hansen Method Found: Customer Feedback Issue Type: Bug Improvement Key: PA FACT - 2132 1870 Project: Puppet Agent Facter Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Erik Hansen updated an issue Puppet / PUP-8969 Sensitive parameters are not redacted from reports / agent output when used in templates Change By: Erik Hansen Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Erik Hansen assigned an issue to Unassigned Puppet / PUP-8969 Sensitive parameters are not redacted from reports / agent output when used in templates Change By: Erik Hansen Assignee: Erik Hansen Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Erik Hansen commented on PUP-8969 Re: Sensitive parameters are not redacted from reports / agent output when used in templates Josh Cooper - what I was expecting from the sensitive type is that the whole of the diff output would not be redacted, but only the sensitive string from within the diff. Maybe this is more of a feature request, but I think there's an assumption that the Sensitive type should be respected everywhere in Puppet (and if it isn't we should document where Sensitive param values would be exposed) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Erik Hansen created an issue Puppet / PUP-8969 Sensitive parameters are not redacted from reports / agent output when used in templates Issue Type: Bug Affects Versions: PUP 5.5.2 Assignee: Unassigned Created: 2018/06/27 8:50 AM Priority: Normal Reporter: Erik Hansen Description: When I use the sensitive data type I expect it to be treated as sensitive when used in templates. However it is not. Steps to reproduce: I've created a small module / repro case here: https://github.com/suckatrash/sensitive Just apply the class "sensitive" Actual Results: If I declare the class "sensitive" it will create two test files /test1 and /test2. If I make any changes in the files and run puppet again, I'll see: +This string should be redacted: 'this is sensitive' in the output of the puppet run and in the report. If I don't unwrap the sensitive parameter and use the commented line in one of the templates I'll see this: +This string should be redacted: 'Sensitive [value redacted]'
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Erik Hansen updated an issue Puppet / PUP-8969 Sensitive parameters are not redacted from reports / agent output when used in templates Change By: Erik Hansen Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7877) Future Work for Intermediate CA Improvements
Title: Message Title Erik Hansen commented on PUP-7877 Re: Future Work for Intermediate CA Improvements Is / can PE-11151 be part of this epic? Customer RedHat is specifically interested in that piece of the CA work. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Erik Hansen commented on PUP-8002 Re: "Attempt to redefine entity" caused by using a resource collector Owen Rodabaugh - Yes, I believe it was merged here: https://github.com/puppetlabs/puppetdb/pull/2389 Although, there's still an open ticket for that issue with a status "ready for merge": https://tickets.puppetlabs.com/browse/PDB-3734 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3840) Add additional cleanup of the facts table during migrations
Title: Message Title
Erik Hansen updated an issue
PuppetDB / PDB-3840
Add additional cleanup of the facts table during migrations
Change By:
Erik Hansen
I think we need to add this these :{code:java}DELETE from facts WHERE fact_path_id NOT IN (SELECT id FROM fact_paths); DELETE FROM facts WHERE fact_value_id NOT IN (SELECT id FROM fact_values); {code}We already do something similar here: [ https://github.com/puppetlabs/puppetdb/blob/5.1.4/src/puppetlabs/puppetdb/scf/migrate.clj#L1318 ]
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-3840) Add additional cleanup of the facts table during migrations
Title: Message Title Erik Hansen created an issue PuppetDB / PDB-3840 Add additional cleanup of the facts table during migrations Issue Type: Bug Assignee: Unassigned Created: 2018/02/07 5:04 PM Priority: Normal Reporter: Erik Hansen I think we need to add this: DELETE from facts WHERE fact_path_id NOT IN (SELECT id FROM fact_paths); We already do something similar here: https://github.com/puppetlabs/puppetdb/blob/5.1.4/src/puppetlabs/puppetdb/scf/migrate.clj#L1318 Add Comment
Jira (PDB-3838) Queries to the facts endpoint generates jsonb_each
Title: Message Title
Erik Hansen created an issue
PuppetDB / PDB-3838
Queries to the facts endpoint generates jsonb_each
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
facts_entitiy_jsonb_each.sql
Created:
2018/02/07 8:41 AM
Priority:
Normal
Reporter:
Erik Hansen
Example command:
puppet query "facts[name, value, count()] { name in ['is_virtual','kernel','aio_agent_version'] group by name, value }"
And the resulting query plan: (attached in facts_entitiy_jsonb_each.sql)
Add Comment
Jira (PDB-3821) [from nodes [= [fact fact-name] fact-val]] queries generate slow sql
Title: Message Title Erik Hansen commented on PDB-3821 Re: [from nodes [= [fact fact-name] fact-val]] queries generate slow sql Russell Mull Yes, looks like jsonb_each is avoided that way. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3821) [from nodes [= [fact fact-name] fact-val]] queries generate slow sql
Title: Message Title Erik Hansen commented on PDB-3821 Re: [from nodes [= [fact fact-name] fact-val]] queries generate slow sql Russell Mull When we talked about this on Friday, the theory was that the inventory endpoint would not be affected, but I see the same jsonb_each queries there: /pdb/query/v4/inventory --data-urlencode 'query=["and",["~","certname",".*delivery.*"],["=", ["fact","kernel"],"Linux"]]' SQL generated: WITH inactive_nodes AS (SELECT certname FROM certnames WHERE (deactivated IS NOT NULL OR expired IS NOT NULL)) SELECT certnames.certname AS certname, fs.timestamp AS timestamp, environments.environment AS environment, (fs.stable||fs.volatile) AS facts, (fs.stable||fs.volatile)->'trusted' AS trusted FROM factsets fs LEFT JOIN environments ON fs.environment_id = environments.id LEFT JOIN producers ON fs.producer_id = producers.id LEFT JOIN certnames ON fs.certname = certnames.certname WHERE (((certnames.certname ~ $1 AND certnames.certname IS NOT NULL) AND ((certnames.certname) in (SELECT certname FROM ( (SELECT fs.certname AS certname FROM (select certname,environment_id,(jsonb_each((stable||volatile))).* from factsets) fs LEFT JOIN environments env ON fs.environment_id = env.id WHERE ((fs.key = $2) AND (fs.value = $3))) ) sub))) AND NOT ((certnames.certname) in (SELECT certname FROM ( (SELECT inactive_nodes.certname AS certname FROM inactive_nodes) ) sub))) 2018-01-29 16:27:27.162 UTC [db:pe-puppetdb,sess:5a6f415c.53a,pid:1338,vtid:8/192,tid:0] DETAIL: parameters: $1 = '.*delivery.*', $2 = 'kernel', $3 = '"Linux"'
Jira (PDB-3821) [from nodes [= [fact fact-name] fact-val]] queries generate slow sql
Title: Message Title Erik Hansen updated an issue PuppetDB / PDB-3821 [from nodes [= [fact fact-name] fact-val]] queries generate slow sql Change By: Erik Hansen Method Found: Needs Assessment Customer Feedback Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3821) [from nodes [= [fact fact-name] fact-val]] queries generate slow sql
Title: Message Title Erik Hansen commented on PDB-3821 Re: [from nodes [= [fact fact-name] fact-val]] queries generate slow sql Something that could also be problematic: /pdb/query/v4/nodes?query=["and",["~","certname",".*test.*"],["=", ["fact","kernel"],"Linux"]] Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8264) Schedule and Filebucket resources have a null containing class
Title: Message Title Erik Hansen commented on PUP-8264 Re: Schedule and Filebucket resources have a null containing class I found a way to reproduce this. Just interrupt a puppet run at the time that facts are loading: # puppet agent -t Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts ^CNotice: Caught INT; exiting Add Comment
Jira (PUP-8264) Schedule and Filebucket resources have a null containing class
Title: Message Title Erik Hansen updated an issue Puppet / PUP-8264 Schedule and Filebucket resources have a null containing class Change By: Erik Hansen Attachment: Screen Shot 2017-12-19 at 9.59.54 AM.png Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8264) Schedule and Filebucket resources have a null containing class
Title: Message Title Erik Hansen updated an issue Puppet / PUP-8264 Schedule and Filebucket resources have a null containing class Change By: Erik Hansen Summary: Resources Schedule and Filebucket resources have a null containing class Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8264) Resources have a null containing class
Title: Message Title Erik Hansen created an issue Puppet / PUP-8264 Resources have a null containing class Issue Type: Bug Affects Versions: PUP 4.10.4 Assignee: Unassigned Created: 2017/12/18 3:12 PM Priority: Normal Reporter: Erik Hansen I'm not sure how this happens but it's possible to see Schedule and Filebucket resources that are not contained by any class. I think this might be happening here: https://github.com/puppetlabs/puppet/blob/5.3.3/lib/puppet/resource/catalog.rb#L321-L332 Here is a snippet of a report where one of these events is skipped: "status": "skipped", "timestamp": "2017-12-18T18:00:20.303+00:00",
Jira (PDB-3770) anonymization via the "puppet db export" command not working
Title: Message Title Erik Hansen commented on PDB-3770 Re: anonymization via the "puppet db export" command not working Here's a workaround for getting the same exported data from the API. Example: curl --cacert /etc/puppetlabs/puppet/ssl/certs/ca.pem \ --cert-type pem \ -H "X-Authentication: $(cat /root/.puppetlabs/token | xargs echo -n)" \ -X GET http://localhost:8080/pdb/admin/v1/archive\?anonymization_profile=full \ -o /tmp/anonymized-export.tar.gz Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-7968) group resource doesn't default to ensure=>present
Title: Message Title Erik Hansen assigned an issue to Erik Hansen Puppet / PUP-7968 group resource doesn't default to ensure=>present Change By: Erik Hansen Assignee: Erik Hansen Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3770) anonymization via the "puppet db export" command not working
Title: Message Title Erik Hansen updated an issue PuppetDB / PDB-3770 anonymization via the "puppet db export" command not working Change By: Erik Hansen Affects Version/s: PDB 4.4.1 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3770) anonymization via the "puppet db export" command not working
Title: Message Title Erik Hansen updated an issue PuppetDB / PDB-3770 anonymization via the "puppet db export" command not working Change By: Erik Hansen Summary: anonymization via the "puppet db export" command not working Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3770) anonymization via the "puppet db export" not working
Title: Message Title Erik Hansen created an issue PuppetDB / PDB-3770 anonymization via the "puppet db export" not working Issue Type: Bug Affects Versions: PDB 5.1.3 Assignee: Unassigned Created: 2017/12/01 9:40 AM Priority: Normal Reporter: Erik Hansen The "puppet db export" command described here does not anonymize data: https://puppet.com/docs/puppetdb/5.1/anonymization.html#using-the-export-command # puppet db export ./test.tar.gz --anonymization full Unknown flag: '--anonymization'
Jira (PDB-3734) Ensure that resource indirection uses existing resource type
Title: Message Title Erik Hansen commented on PDB-3734 Re: Ensure that resource indirection uses existing resource type Russell Mull Actually, we've only seen this reported in versions past the LTS. Although I don't know enough about the technical detail to know if it could happen there or not. 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-8037) Configuring "server_urls" causes connection attempts to port 0
Title: Message Title Erik Hansen commented on PUP-8037 Re: Configuring "server_urls" causes connection attempts to port 0 Also, in some situations these connection attempts are made to an actual server and not one called 'nil': Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) for "puppet" port 0 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-8037) Configuring "server_urls" causes connection attempts to port 0
Title: Message Title Erik Hansen created an issue Puppet / PUP-8037 Configuring "server_urls" causes connection attempts to port 0 Issue Type: Bug Affects Versions: PUP 4.10.8 Assignee: Unassigned Created: 2017/10/09 12:43 PM Priority: Normal Reporter: Erik Hansen When configuring an agent with "server_urls", failover events that exhaust the list of servers result in connection attempts to port 0: Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) for nil port 0 I couldn't find this behavior documented anywhere. Is it intentional?
Jira (PUP-8036) Use of server_urls can cause misleading agent errors
Title: Message Title
Erik Hansen updated an issue
Puppet / PUP-8036
Use of server_urls can cause misleading agent errors
Change By:
Erik Hansen
h3. The issue:the "server_urls" configuration setting can mask server-side issues by mistakingly pointing to a connectivity issue on port 0:{noformat}Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) for nil port 0{noformat}h3. Replication: Configure an agent to connect to a master with the server_list setting:{noformat}[agent]#server = pe-201724-master.puppetdebug.vlanserver_list = pe-201724-master.puppetdebug.vlan:8140{noformat}Revoke the agent's certificate on the master and observer observe the error on the next agent run:h3. Actual result:{noformat}Warning: Could not select a functional puppet masterWarning: Unable to fetch my node definition, but the agent run will continue:Warning: Connection refused - connect(2) for nil port 0Info: Retrieving pluginfactsError: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) for nil port 0Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: Connection refused - connect(2) for nil port 0Info: Retrieving pluginError: /File[/opt/puppetlabs/puppet/cache/lib]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) for nil port 0Error: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: Connection refused - connect(2) for nil port 0Info: Loading factsError: Could not retrieve catalog from remote server: Connection refused - connect(2) for nil port 0Warning: Not using cache on failed catalogError: Could not retrieve catalog; skipping runError: Could not send report: Connection refused - connect(2) for nil port 0{noformat}h3. Expected result:Change the agent's configuration to use the "server" setting and observe the difference. The error points more clearly to an SSL issue:{noformat}Warning: Unable to fetch my node definition, but the agent run will continue:Warning: SSL_connect SYSCALL returned=5 errno=0 state=unknown stateInfo: Retrieving pluginfactsError: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': SSL_connect SYSCALL returned=5 errno=0 state=unknown stateError: /File[/opt/puppetlabs/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: SSL_connect SYSCALL returned=5 errno=0 state=unknown stateInfo: Retrieving pluginError: /File[/opt/puppetlabs/puppet/cache/lib]: Failed to generate additional resources using 'eval_generate': SSL_connect SYSCALL returned=5 errno=0 state=unknown stateError: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: SSL_connect SYSCALL returned=5 errno=0 state=unknown stateInfo: Loading factsError: Could not retrieve catalog from remote server: SSL_connect SYSCALL returned=5 errno=0 state=unknown stateWarning: Not using cache on failed catalogError: Could not retrieve catalog; skipping runError: Could
Jira (PUP-8036) Use of server_urls can cause misleading agent errors
Title: Message Title Erik Hansen created an issue Puppet / PUP-8036 Use of server_urls can cause misleading agent errors Issue Type: Bug Affects Versions: PUP 4.10.8 Assignee: Unassigned Created: 2017/10/09 12:25 PM Priority: Normal Reporter: Erik Hansen The issue: the "server_urls" configuration setting can mask server-side issues by mistakingly pointing to a connectivity issue on port 0: Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Connection refused - connect(2) for nil port 0 Replication: Configure an agent to connect to a master with the server_list setting:
Jira (PUP-7308) classes do not honor refresh events when running with tags
Title: Message Title Erik Hansen updated an issue Puppet / PUP-7308 classes do not honor refresh events when running with tags Change By: Erik Hansen CS Priority: Needs Priority 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-3645) Long postgres query related to Puppet_enterprise::Profile::Console resources
Title: Message Title Erik Hansen created an issue PuppetDB / PDB-3645 Long postgres query related to Puppet_enterprise::Profile::Console resources Issue Type: Bug Assignee: Unassigned Attachments: explain-2017-08-28-15-15-29.out, postgresql-Wed.log.zip Created: 2017/08/28 8:59 AM Priority: Blocker Reporter: Erik Hansen Walmart noticed that their console node more frequently fails to check in and spawns the error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Failed to execute '/pdb/query/v4' on at least 1 of the following 'server_urls': https://pe-puppetdb.wal-mart.com:8081 at /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/trapperkeeper/console_services.pp:196:12 at /opt/puppetlabs/puppet/modules/puppet_enterprise/manifests/console_services.pp:43 on node oser501242.wal-mart.com
Jira (PUP-7796) An agent should be able to recover from a provider failure
Title: Message Title Erik Hansen commented on PUP-7796 Re: An agent should be able to recover from a provider failure Josh Cooper here you go: [root@pe-201720-master ~]# puppet apply test_pip.pp --trace Notice: Compiled catalog for pe-201720-master.example.com in environment production in 0.96 seconds Error: Failed to apply catalog: [nil] /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/execution.rb:86:in `execpipe' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider.rb:117:in `execpipe' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package/pip.rb:34:in `instances' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package.rb:4:in `prefetch' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:323:in `prefetch' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:223:in `prefetch_if_necessary'
Jira (PUP-7796) An agent should be able to recover from a provider failure
Title: Message Title Erik Hansen created an issue Puppet / PUP-7796 An agent should be able to recover from a provider failure Issue Type: Bug Affects Versions: PUP 4.10.4 Assignee: Unassigned Created: 2017/07/21 3:07 PM Environment: Tested on Centos 6.7 Labels: maintenance triage Priority: Normal Reporter: Erik Hansen The issue If a provider fails for some reason, even non-dependent catalog resources fail to be applied. To reproduce This test case involves the pip provider. Install pip:
Jira (PDB-3611) Fact filter from overview page uses nested loops and times out
Title: Message Title Erik Hansen updated an issue PuppetDB / PDB-3611 Fact filter from overview page uses nested loops and times out Change By: Erik Hansen Method Found: Needs Assessment Customer Feedback 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-3611) Fact filter from overview page uses nested loops and times out
Title: Message Title Erik Hansen created an issue PuppetDB / PDB-3611 Fact filter from overview page uses nested loops and times out Issue Type: Bug Affects Versions: PDB 4.4.1 Assignee: Unassigned Created: 2017/07/05 1:18 PM Priority: Normal Reporter: Erik Hansen Attempting to filter the console overview page based on two fact filters causes a timeout in the console. The attempted query was: 2017-07-03 13:49:03.676 UTC [db:pe-puppetdb,sess:595a3ced.c711,pid:50961,vtid:22/490887,tid:0] LOG: duration: 503820.138 ms execute S_826/C_827: WITH inactive_nodes AS (SELECT certname FROM certnames WHERE (deactivated IS NOT NULL OR expired IS NOT NULL)) SELECT certnames.certname AS certname FROM factsets fs LEFT JOIN environments ON fs.environment_id = environments.id LEFT JOIN producers ON fs.producer_id = producers.id LEFT JOIN certnames ON fs.certname = certnames.certname WHERE (((certnames.certname) in ( (SELECT fs.certname AS certname FROM factsets fs INNER JOIN facts f ON fs.id = f.factset_id INNER JOIN fact_paths fp ON f.fact_path_id = fp.id INNER JOIN value_types vt ON f.value_type_id = vt.id LEFT JOIN environments env ON fs.environment_id = env.id WHERE (vt.id <> 5 AND ((fp.path ~ $1 AND fp.path IS NOT NULL) AND (f.value_string = $2 ) ) AND
Jira (PUP-7744) Puppet CA's CRL is prone to duplicate entries
Title: Message Title Erik Hansen commented on PUP-7744 Re: Puppet CA's CRL is prone to duplicate entries Josh Cooper Just a clarification, the duplicate entries can be produced without multiple writers though. It occurs simply by attempting to purge a certificate name that has already been revoked. 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-7744) Puppet CA's CRL is prone to duplicate entries
Title: Message Title Erik Hansen updated an issue Puppet / PUP-7744 Puppet CA's CRL is prone to duplicate entries Change By: Erik Hansen Method Found: Needs Assessment Customer Feedback 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-7744) Puppet CA's CRL is prone to duplicate entries
Title: Message Title Erik Hansen created an issue Puppet / PUP-7744 Puppet CA's CRL is prone to duplicate entries Issue Type: Bug Assignee: Unassigned Created: 2017/06/30 9:50 AM Priority: Normal Reporter: Erik Hansen Using the 'puppet node purge' command it is possible to put duplicate revoked certificates in Puppet's CRL. For example: # puppet cert generate testcert Notice: testcert has a waiting certificate request Notice: Signed certificate request for testcert Now purge the node / certificate:
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Erik Hansen commented on PDB-2487 Re: Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Fannie Mae hitting this in: https://puppetlabs.zendesk.com/agent/tickets/26371 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-7589) install.bash script does not restart services on AIX
Title: Message Title
Erik Hansen updated an issue
Puppet / PUP-7589
install.bash script does not restart services on AIX
Change By:
Erik Hansen
If I run the install.bash script in order to upgrade an AIX agent the puppet / pxp-agent / mcollective services don't get restarted (they do on other platforms). This was observed upgrading the agent packages from 1.5.2 (and also from 1.7.2) to 1.10.1This can cause issues as the stale process in AIX can cause errors in puppet's scheduled runs.To reproduce:* Install agent package puppet-agent-1.5.2-1.aix7.1.ppc.rpm on AIX 7.1* connect the agent to a master on 2016.4.5* run the bash installer:{noformat}curl -1 https://pe-201643-master.example.com:8140/packages/current/install.bash | sed -e "s/[!\! ]bash/bash -x/" |bash -x 2>&1 |tee /tmp/install_debug.out{noformat}You can see in the output file that the services never get a restart, you can also see this by checking the output of: 'ps -ef | egrep 'puppet|pxp|mcoll' | grep -v grep'{noformat}root 9568366 3277006 0 08:21:09 - 0:00 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/mcollectived --config=/etc/puppetlabs/mcollective/server.cfg --no-daemonizeroot 10354832 3277006 0 08:21:07 - 0:00 /opt/puppetlabs/puppet/bin/pxp-agent --foregroundroot 11993134 3277006 0 08:21:03 - 0:01 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/bin/puppet agent --no-daemonize{noformat}Attaching debug output from an AIX agent as well as from a RedHat agent where all three services refresh.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7589) install.bash script does not restart services on AIX
Title: Message Title Erik Hansen commented on PUP-7589 Re: install.bash script does not restart services on AIX Looks like this might be PA-390 . I'll verify and close this out if that's the case 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-7589) install.bash script does not restart services on AIX
Title: Message Title Erik Hansen created an issue Puppet / PUP-7589 install.bash script does not restart services on AIX Issue Type: Bug Assignee: Unassigned Attachments: aix_install_debug.out, redhat_install_debug.out Created: 2017/05/23 9:01 AM Priority: Normal Reporter: Erik Hansen If I run the install.bash script in order to upgrade an AIX agent the puppet / pxp-agent / mcollective services don't get restarted (they do on other platforms). This can cause issues as the stale process in AIX can cause errors in puppet's scheduled runs. To reproduce: Install agent package puppet-agent-1.5.2-1.aix7.1.ppc.rpm on AIX 7.1 connect the agent to a master on 2016.4.5 run the bash installer:
Jira (PUP-7454) The schedule metaparameter should allow for suppressing skip events
Title: Message Title
Erik Hansen created an issue
Puppet / PUP-7454
The schedule metaparameter should allow for suppressing skip events
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2017/04/18 3:31 PM
Priority:
Normal
Reporter:
Erik Hansen
The following code snippet generates 48 event messages every day (per node) with the default run interval. 47 of the events are a "skipped" event and one being a success:
schedule { 'allowed_hours':
period => daily,
range => "5:00 - 17:00",
repeat => 1,
Jira (PUP-7372) puppet 4.9.4 lookup fails with undefined method error message
Title: Message Title Erik Hansen updated an issue Puppet / PUP-7372 puppet 4.9.4 lookup fails with undefined method error message Thomas Hallgren I think I have what is a minimal reproduction case. Please see the attached tarball. The error occurs when the "ecds" module (with hiera v5 hiera.yaml file) is present. Without the module present the command completes with the --merge flag and returns the expected data. Succeeds: puppet lookup --facts=/etc/puppetlabs/code/environments/production/facts.yaml --node bwdprdx-db501.bnaint.com --type Hash ecds::bnai::fs Fails: puppet lookup --facts=/etc/puppetlabs/code/environments/production/facts.yaml --node bwdprdx-db501.bnaint.com --type Hash --merge deep ecds::bnai::fs (facts.yaml contains the needed fact resolutions) What is really strange is that when I rename the directory that the module resides in, the error goes away. mv modules/ecds modules/test Change By: Erik Hansen
Jira (PUP-7047) Moduledata: lookup function fails looking up a false value when the value refers back to module scope
Title: Message Title
Erik Hansen created an issue
Puppet / PUP-7047
Moduledata: lookup function fails looking up a false value when the value refers back to module scope
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
hieratest.tar.gz
Created:
2016/12/22 3:35 PM
Priority:
Normal
Reporter:
Erik Hansen
Using hiera 4 module data with key / values:
cat data/common.yaml:
---
hieratest::message: "%{stringvalue}"
hieratest::trueboolean: "%{truevalue}"
Jira (PUP-7035) Enforcing the status of a domain user / group fails until DS cache is refreshed
Title: Message Title
Erik Hansen created an issue
Puppet / PUP-7035
Enforcing the status of a domain user / group fails until DS cache is refreshed
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/12/19 2:08 PM
Priority:
Normal
Reporter:
Erik Hansen
This was reported on RHEL 5, 6 and 7 agents that are connected to a DS for account creation. Attempting to enforce attributes of the existing DS users (or groups) fails until the NS cache is refreshed on the system.
Example manifest:
user {'test':
ensure => 'present',
gid => 'test',
password => 'test',
Jira (PUP-7022) The HTTP report processor should timeout requests that take too long
Title: Message Title Erik Hansen created an issue Puppet / PUP-7022 The HTTP report processor should timeout requests that take too long Issue Type: Bug Assignee: Unassigned Created: 2016/12/16 9:21 AM Priority: Normal Reporter: Erik Hansen The HTTP report processor currently does not timeout if the endpoint does not reply. This has the effect that a JRuby is tied up indefinitely, and not returned to the pool. This can quickly tie up all available JRubies and prevent further work being done by the puppetserver process. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Erik Hansen commented on PUP-6986 Re: Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Anyone hitting this issue might be able to work around the problem by setting the environment variable LC_CTYPE=en_US.UTF-8 either as a system setting or applied to the environment that the agent runs in. 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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars
Title: Message Title Erik Hansen created an issue Puppet / PUP-6986 Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars Issue Type: Improvement Assignee: Unassigned Created: 2016/12/07 3:37 PM Priority: Normal Reporter: Erik Hansen When a service resource uses the parameter `hasstatus => false`, puppet will search the output of `ps -ef` to determine the status of the service. If the output of `ps -ef` happens to contain non-ASCII characters, we see the following stack trace: Error: /Stage[main]/Automic/Service[automic]: Could not evaluate: invalid byte sequence in US-ASCII /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/base.rb:38:in `match' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/base.rb:38:in `block (2 levels) in getpid'
Jira (PUP-6929) Improvements around hiera error messaging
Title: Message Title
Erik Hansen updated an issue
Puppet / PUP-6929
Improvements around hiera error messaging
Change By:
Erik Hansen
In some cases a syntax error in the hiera backend produces strange errors that don't necessarily point to the problem and can often obfuscate the real issue. A few examples:h5. This was tracked down to a stray tab in a .yaml file { code:java noformat }Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Error from DataBinding 'hiera' while looking up 'puppet_enterprise::certificate_authority_port': undefined method `empty?' for nil:NilClass on node agent.example.com{ code noformat }h5. This ended up being a stray string in a .yaml file, but the file didn't contain the key / value in the error message at all: { code:java noformat }Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Error from DataBinding 'hiera' while looking up 'ntp::autoupdate': undefined method `empty?' for nil:NilClass on node agent.example.com{ code noformat }h5. The following two examples occurred on different nodes. The issue was tracked down to extra whitespace in a .yaml file, but not one that contained either of the keys in the error message.{ code:java noformat }Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Resource Statement, Lookup of key 'puppet_agent::arch' failed: DataBinding 'hiera': undefined method `empty?' for nil:NilClass on node agent.example.com{ code noformat }{ code:java noformat }Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Resource Statement, Lookup of key 'hiera::backends' failed: DataBinding 'hiera': undefined method `empty?' for nil:NilClass at /etc/puppetlabs/code/environments/production/site/profile/manifests/puppetmaster.pp:6:3 on node agent.example.com{ code noformat }
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6929) Improvements around hiera error messaging
Title: Message Title Erik Hansen moved an issue Puppet / PUP-6929 Improvements around hiera error messaging Change By: Erik Hansen Key: ENTERPRISE PUP - 957 6929 Project: Puppet Enterprise 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-6801) agent_specified_environment fact doesn't populate with the environment setting in the [agent] section
Title: Message Title Erik Hansen commented on PUP-6801 Re: agent_specified_environment fact doesn't populate with the environment setting in the [agent] section Michael Smith I only noticed it using 'facter -p agent_specified_environment' and in /etc/puppetlabs/mcollective/facts.yaml. With environment set in the [main] section this works. If the environment is in the [agent] section, no dice. puppet.conf: server = pe-201620-master.example.com #environment = nothing [agent] certname = pe-201620-agent2 environment = nothing Run: /opt/puppetlabs/puppet/bin/refresh-mcollective-metadata [root@pe-201620-agent2 ~]# cat /etc/puppetlabs/mcollective/facts.yaml | grep agent_spec [root@pe-201620-agent2 ~]# [root@pe-201620-agent2 ~]# facter -p agent_specified_environment (no output) Edit puppet.conf: [main] server = pe-201620-master.example.com
Jira (PDB-3109) Puppetdb logs are managed by logrotate and logback.xml
Title: Message Title Erik Hansen moved an issue PuppetDB / PDB-3109 Puppetdb logs are managed by logrotate and logback.xml Change By: Erik Hansen Key: PE PDB - 18078 3109 Project: Puppet Enterprise [Internal] PuppetDB 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-6800) Better error messaging around invalid class names
Title: Message Title Erik Hansen commented on PUP-6800 Re: Better error messaging around invalid class names Henrik Lindberg The documentation says that class names must match the regex: \A[a-z][a-z0-9_]*\Z Or, for multiple namespaces: \A([a-z][a-z0-9_])?(::[a-z][a-z0-9_])*\Z Do we need to change this so that uppercase characters are included? 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-6822) Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist
Title: Message Title
Erik Hansen created an issue
Puppet / PUP-6822
Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/10/16 9:36 AM
Priority:
Normal
Reporter:
Erik Hansen
Linux agents don't seem to have this issue, for example:
]# puppet apply -e 'service {"notaservice": ensure => "stopped", enable => false,}'
Notice: Compiled catalog for pe-201620-master.example.com in environment production in 0.12 seconds
Notice: Applied catalog in 0.33 seconds
However, on Windows, an attempt to apply the same resource gives:
Jira (PUP-6820) Puppetdb logs are managed by logrotate and logback.xml
Title: Message Title Erik Hansen created an issue Puppet / PUP-6820 Puppetdb logs are managed by logrotate and logback.xml Issue Type: Bug Assignee: Unassigned Created: 2016/10/14 3:49 PM Priority: Normal Reporter: Erik Hansen Logrotation for puppetdb is configured in both: /etc/logrotate.d/pe-puppetdb - and - /etc/puppetlabs/puppetdb/logback.xml This results in a situation in which we see both file extensions in the log directory. Example: puppetdb-2016-10-05.log.gz puppetdb-2016-10-06.log.gz puppetdb-2016-10-07.log.gz
Jira (PUP-6814) Filebucket fails with recursive backup
Title: Message Title
Erik Hansen updated an issue
Puppet / PUP-6814
Filebucket fails with recursive backup
Change By:
Erik Hansen
Managing a directory with a deep directory structure and that contains a large file causes an error in AIX 7.1:{code:java}Error: /Stage[main]/Filetest/File[/test]/ensure: change from directory to absent failed: failed to allocate memoryError: Could not run: failed to allocate memory{code}The directory /test in this case contains a deep directory structure as well as a large file, I'm not sure what the threshold for receiving the error is but to reproduce I did this:mkdir -p /test/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/temp/tempcd to above directory and :{noformat}dd if=/dev/urandom of=file.txt bs=1048576 count=100 dd if=/dev/urandom of=file2.txt bs=1048576 count=100{noformat}{noformat}puppet filebucket backup /test{noformat}Then, apply a class from the master containing:{code:puppet}class filetest { file {'/test':ensure => absent,force => true,backup => 'main', }}{code} Additionally, although the puppet run produces an error, the report in the console shows a report with no changes, and no failed changes (green status)
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6814) Filebucket fails with recursive backup
Title: Message Title Erik Hansen created an issue Puppet / PUP-6814 Filebucket fails with recursive backup Issue Type: Bug Assignee: Unassigned Created: 2016/10/12 5:24 PM Priority: Normal Reporter: Erik Hansen Managing a directory with a deep directory structure and that contains a large file causes an error in AIX 7.1: Error: /Stage[main]/Filetest/File[/test]/ensure: change from directory to absent failed: failed to allocate memory Error: Could not run: failed to allocate memory The directory /test in this case contains a deep directory structure as well as a large file, I'm not sure what the threshold for receiving the error is but to reproduce I did this: mkdir -p
Jira (PUP-6801) agent_specified_environment fact doesn't populate with the environment setting in the [agent] section
Title: Message Title Erik Hansen created an issue Puppet / PUP-6801 agent_specified_environment fact doesn't populate with the environment setting in the [agent] section Issue Type: Bug Affects Versions: PUP 4.4.0 Assignee: Unassigned Created: 2016/10/06 4:33 PM Priority: Normal Reporter: Erik Hansen Currently, if I want to use the agent_specified_environment fact, I need to set the environment setting in puppet.conf in the [main] section. If I happen to be hitting this bug: PUP-6048, this isn't possible. Putting the environment setting in the [agent] section works around PUP-6048, but doesn't allow me to use agent_specified_environment, the fact ends up empty. Add Comment
Jira (PUP-6800) Better error messaging around invalid class names
Title: Message Title Erik Hansen commented on PUP-6800 Re: Better error messaging around invalid class names What I observed was that a Windows agent was unable to pick up a class role::appserver::windows_2012R2 until the second time that the agent ran the catalog. Here is an example of the info in puppetserver.log: 2016-09-16 14:47:58,964 ERROR [qtp1760965953-81] [puppetserver] Puppet Could not find class role::appserver::windows_2012R2 for puppetagent.example.comt on node puppetagent.example.com There wasn't really anything that identified the invalid class name, but when the class was renamed to role::appserver::windows_2012r2, I no longer saw the 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-6800) Better error messaging around invalid class names
Title: Message Title Erik Hansen created an issue Puppet / PUP-6800 Better error messaging around invalid class names Issue Type: Improvement Assignee: Unassigned Created: 2016/10/06 3:10 PM Priority: Normal Reporter: Erik Hansen The language guide is specific about what allowed class names are: https://docs.puppet.com/puppet/latest/reference/lang_reserved.html#classes-and-defined-resource-types However, if someone were unaware of the character limitation, it can cause issues that are difficult to track down, such as classes not loading or only being available to certain agents. It would be an improvement if puppet server or the console service (or both) would issue clear warnings about class names that do not follow the standard. Add Comment
Jira (PUP-6048) error running puppet with non existing and non default environment
Title: Message Title Erik Hansen commented on PUP-6048 Re: error running puppet with non existing and non default environment Henrik Lindberg Kylo Ginsberg There might be something else to consider here, and maybe a separate ticket needs to be created, but AFAIK the puppet fact "agent_specified_environment" is only populated when the environment is specified in the [main] section. If you want to use that fact, but are hitting this issue and put the environment setting in the [agent] section to avoid it, then you would kind of be out of luck. 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-6711) Puppet lookup doesn't know about custom facts
Title: Message Title Erik Hansen commented on PUP-6711 Re: Puppet lookup doesn't know about custom facts I was testing on a PE 2016.2.0 Master with this repro case. 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-6711) Puppet lookup doesn't know about custom facts
Title: Message Title Erik Hansen updated an issue Puppet / PUP-6711 Puppet lookup doesn't know about custom facts Attaching the module used for testing here Change By: Erik Hansen Attachment: hiera4test.tar.gz 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-6711) Puppet lookup doesn't know about custom facts
Title: Message Title Erik Hansen created an issue Puppet / PUP-6711 Puppet lookup doesn't know about custom facts Issue Type: Bug Assignee: Unassigned Created: 2016/09/16 4:22 PM Priority: Normal Reporter: Erik Hansen I've played around with this for a while and I can't figure out why custom facts are sometimes interpolated inside a hiera.yaml file, and sometimes not (only in the context of puppet lookup) hiera.yaml file for a test module: --- version: 4 datadir: data hierarchy:
Jira (PUP-6709) Escaped characters are handled differently with future parser enabled
Title: Message Title
Erik Hansen updated an issue
Puppet / PUP-6709
Escaped characters are handled differently with future parser enabled
Change By:
Erik Hansen
With the legacy parser, the code below returns:{code:java}\*\.info{code}With future parser enabled I get ' :{code:java} \1\1info ' {code} {code:puppet}$test=regsubst('*.info','([.*])','\\\1','G')notify {$test:}{code}To correct the output with the future parser enabled, I need to add escape characters:{code:puppet}$test=regsubst('*.info','([.*])','\1','G')notify {$test:}{code}
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-6709) Escaped characters are handled differently with future parser enabled
Title: Message Title
Erik Hansen updated an issue
Puppet / PUP-6709
Escaped characters are handled differently with future parser enabled
Change By:
Erik Hansen
With the legacy parser, the code below returns :{code:java} \*\.info {code} With future parser enabled I get '\1\1info'{code:puppet}$test=regsubst('*.info','([.*])','\\\1','G')notify {$test:}{code}To correct the output with the future parser enabled, I need to add escape characters:{code:puppet}$test=regsubst('*.info','([.*])','\1','G')notify {$test:}{code}
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-6709) Escaped characters are handled differently with future parser enabled
Title: Message Title
Erik Hansen updated an issue
Puppet / PUP-6709
Escaped characters are handled differently with future parser enabled
Change By:
Erik Hansen
With the legacy parser, the code below returns ' \*\.info ' With future parser enabled I get '\1\1info'{code:puppet}$test=regsubst('*.info','([.*])','\\\1','G')notify {$test:}{code}To correct the output with the future parser enabled, I need to add escape characters:{code:puppet}$test=regsubst('*.info','([.*])','\1','G')notify {$test:}{code}
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-6709) Escaped characters are handled differently with future parser enabled
Title: Message Title
Erik Hansen created an issue
Puppet / PUP-6709
Escaped characters are handled differently with future parser enabled
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/09/16 1:05 PM
Priority:
Normal
Reporter:
Erik Hansen
With the legacy parser, the code below returns '*\.info'
With future parser enabled I get '\1\1info'
$test=regsubst('*.info','([.*])','\\\1','G')
notify {$test:}
To correct the output with the future parser enabled, I need to add escape characters:
Jira (PUP-6601) Autorequire in mount.rb causes dependency cycle with LVM module
Title: Message Title
Erik Hansen created an issue
Puppet / PUP-6601
Autorequire in mount.rb causes dependency cycle with LVM module
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/08/10 9:51 AM
Priority:
Normal
Reporter:
Erik Hansen
Before the change to the mount provider that was committed here: https://github.com/puppetlabs/puppet/commit/747dae17189c9eb1321196642fcdb91b32d3b09b#diff-6cb22546390c0207d2cab18ad531a34b
You could describe an LVM resource like this:
file { '/apps':
ensure => directory,
}
Jira (PUP-6495) Allow for assigning different environments to Solaris zones
Title: Message Title Erik Hansen created an issue Puppet / PUP-6495 Allow for assigning different environments to Solaris zones Issue Type: New Feature Assignee: Unassigned Created: 2016/07/12 12:31 PM Priority: Normal Reporter: Erik Hansen A Solaris server that has 5 local zones and each zone acts as a different environment for an application. Outside of installing a puppet agent on each zone, looking for a way to assign an environment to each of the zones. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Erik Hansen created an issue Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Issue Type: Bug Assignee: Unassigned Created: 2016/07/08 3:39 PM Priority: Normal Reporter: Erik Hansen When running "puppet resource user" in Windows, the action results in a log entry in the Windows security log: Log Name: Security Source: Microsoft-Windows-Security-Auditing Date: 7/8/2016 10:26:11 PM Event ID: 4625 Task Category: Logon Level: Information Keywords: Audit Failure User: N/A Computer: pe-201612-agent-win2008 Description: An account failed to log on. Subject: Security ID: PE-201612-AGENT\vagrant Account Name: vagrant Account Domain: PE-201612-AGENT Logon ID: 0xf07a Logon Type: 3 Account For Which Logon Failed: Security ID: NULL SID Account Name: vagrant Account Domain: PE-201612-AGENT Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xc06d Sub Status: 0xc06a Process Information: Caller Process ID: 0x538 Caller Process Name: C:\Program Files\Puppet Labs\Puppet\sys\ruby\bin\ruby.exe Network Information: Workstation Name: PE-201612-AGENT Source Network Address: - Source Port: - Detailed Authentication Information: Logon Process: Advapi Authentication Package: Negotiate Transited Services: - Package Name (NTLM only): - Key Length: 0 This event is generated when a logon request fails. It is generated on the computer where access was attempted. The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service
Jira (PUP-6462) Re-enable links to filebucket diffs in the console
Title: Message Title Erik Hansen updated an issue Puppet / PUP-6462 Re-enable links to filebucket diffs in the console Attaching screenshot Change By: Erik Hansen Attachment: Screen Shot 2016-06-30 at 9.35.22 AM.png 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-6462) Re-enable links to filebucket diffs in the console
Title: Message Title Erik Hansen created an issue Puppet / PUP-6462 Re-enable links to filebucket diffs in the console Issue Type: Improvement Assignee: Unassigned Created: 2016/06/30 9:40 AM Priority: Normal Reporter: Erik Hansen In PE 3.8.x you used to be able to find a link to filebucket diffs in the reporting tab. This was useful for troubleshooting and for tracking down what file changes had been made. The link would show up in the the events tab for a changed node under Reports. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6412) Add the ability to pass a filter to classifier API requests.
Title: Message Title Erik Hansen commented on PUP-6412 Re: Add the ability to pass a filter to classifier API requests. This would be useful if you wanted to return only a list of nodes belonging to the group, for example. Node names would be listed in the 'rules' key and it would be a quick way to get a list of nodes in a group from the API. 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-6412) Add the ability to pass a filter to classifier API requests.
Title: Message Title Erik Hansen created an issue Puppet / PUP-6412 Add the ability to pass a filter to classifier API requests. Issue Type: Improvement Assignee: Unassigned Created: 2016/06/15 10:35 AM Priority: Normal Reporter: Erik Hansen For the classifier-api endpoint, it would be nice to add a 'filter' parameter so that the JSON returned could be limited to certain keys. Examples: curl -X GET https://$(hostname -f):4433/classifier-api/v1/groups/e19f7257-1da7-4e8f-b8a4-900df3697614?filter=name curl -X GET https://$(hostname -f):4433/classifier-api/v1/groups/e19f7257-1da7-4e8f-b8a4-900df3697614?filter=name,variables,environment Add Comment
