Jira (FACT-2210) memory fact for OSX
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Facter / FACT-2210 memory fact for OSX Change By: Luchian Nemes Assignee: Luchian Nemes 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338916.1576053231000.6009.1576741560215%40Atlassian.JIRA.
Jira (FACT-1472) Ensure the collection has enough information about external facts to cache them.
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1472 Ensure the collection has enough information about external facts to cache them. Change By: Mihai Buzgau Team: Platform OS Night's Watch 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.143279.1469463305000.6004.1576741260443%40Atlassian.JIRA.
Jira (PUP-10160) Puppet should not load types and providers during environment convergence
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10160 Puppet should not load types and providers during environment convergence Change By: Josh Cooper Release Notes Summary: Previously puppet agents could fail to apply a catalog if the agent switched environments based on node classification and there were different versions of a module in those environments. As a result of this change, an agent should converge to its server-assigned environment more quickly , only load types and will providers once, and only update its cached catalog if the environment converges. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.337880.157548855.5837.1576712880363%40Atlassian.JIRA.
Jira (PUP-10146) Add File HTTP service
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10146
Add File HTTP service
Change By:
Josh Cooper
Implement a {{:file}} service with methods for:{noformat} GET /puppet/v3/file_metadata get_file_metadata GET /puppet/v3/file_metadatas get_file_metadatas GET /puppet/v3/file_content get_file_content {noformat} See Puppet::Indirector::Rest#headers for how to generate list of accepted headers h4. file_metadata get_file_metadata Requires Required arguments {{:mount_point}}, {{:path}}, {{environment}} , arguments Optionally accepts Optional arguments {{links}}, {{checksum_type}}, {{source_permissions}}, defaulting to whatever puppet 6 doesUse the {{ ssl_context Content-Type }} Call header in the response to lookup the network formatter. If the {{ Puppet::FileServing::Metadata#render Content-Type }} contains a {{charset}}, force encode the response body that that encoding. Use the formatter to serialize and deserialize the {{Puppet::FileServing::Metadata #mime }} instance.If the response code is 404, then I believe we want to specify content-type treat that as not an error (due to a long standing puppet bug). h4. file_metadatas get_file_metadatas Requires Required arguments {{:mount_point}}, {{:path}}, {{environment}} arguments Optionally accepts Optional arguments {{recurse}}, {{ignore}}, {{links}}, {{checksum_type}}, {{source_permissions}} , {{ssl_context}} Call Use the {{ Puppet::FileServing::Metadata#render Content-Type }} header in the response to serialize and lookup the network formatter. Use the formatter to deserialize an array of {{Puppet::FileServing::Metadata #mime }} instances.If the response code is 404, then I believe we want to specify content-type treat that as not an error (due to a long standing puppet bug). h4. file_content get_file_content Require Required arguments {{:mount_point}}, {{:path}} Optional accepts {{ssl_context}} Always set header {{Accept: application/octet-stream}}. Force encode the response body as {{Encoding::BINARY}}.Stream the response body to the caller.
Add Comment
Jira (PUP-10038) Add Report HTTP service
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10038
Add Report HTTP service
Change By:
Josh Cooper
Implement a report service with support for the following method:{noformat}put_report(name, report, environment: , :ssl_context: nil ){noformat}* Submit the report to {{/puppet/v3/report/}}* Include Require the {{environment}} argument and send it as an HTTP query parameter* Serialize report via Use {{ Puppet[:preferred_serialization_format]}} to select the formatter:{code:ruby}formatter = Puppet::Network::FormatHandler.format_for(Puppet[:preferred_serialization_format]){code}* Set the request body to the serialized report : {{formatter .render (report) }} , and pass * Set the {{Content- Length}} to the number of bytes in the serialized report* Set the {{Content- Type}} as header to {{ report formatter .mime}}* Set the {{ Accept }} header to to the mime types that we support for the Report* Accept response content as {{application/json, application/x-msgpack, text/pson}}. See For example: { { code:ruby}model = Puppet:: Indirector Transaction :: Rest#headers Reportmodel.supported_formats.reject { |f| f == :yaml } } for how this list is generated for each .map { |f| model .get_format ( Report, Catalog, etc f ). mime } {code} * If we fail to send the report, the server version is < 5 and the current serialization format is not pson, then emit an error that {{preferred_serialization_format}} should be set to {{pson}}.See puppet/indirector/report/rest.rb
Add Comment
This message
Jira (PUP-10165) puppetdb_query doesn't respect hostprivkey & hostcert settings
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10165 puppetdb_query doesn't respect hostprivkey & hostcert settings Change By: Josh Cooper Release Notes Summary: It was no longer possible to override the client certificate and corresponding private key using the `hostcert` and `hostprivkey` puppet settings. This fix restores that capability. Release Notes: Bug Fix 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338500.1575710302000.5456.1576703220127%40Atlassian.JIRA.
Jira (PUP-10148) Include X-Puppet-Profiling header
Title: Message Title Melissa Stone updated an issue Puppet / PUP-10148 Include X-Puppet-Profiling header Change By: Melissa Stone Release Notes Summary: Puppet::HTTP::Client can now pass in the 'X-Puppet-Profiler' header when making http requests if Puppet[:profile] is true. Release Notes: Enhancement 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335811.157412461.5394.1576699920127%40Atlassian.JIRA.
Jira (PUP-10034) Implement DELETE, HEAD, POST
Title: Message Title Melissa Stone updated an issue Puppet / PUP-10034 Implement DELETE, HEAD, POST Change By: Melissa Stone Release Notes Summary: Puppet::HTTP::Client now has the ability to make HEAD, POST, and DELETE requests Release Notes: Enhancement 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326122.1569365544000.5392.1576699860131%40Atlassian.JIRA.
Jira (PUP-10148) Include X-Puppet-Profiling header
Title: Message Title Melissa Stone updated an issue Puppet / PUP-10148 Include X-Puppet-Profiling header Change By: Melissa Stone Fix Version/s: PUP 6.12.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335811.157412461.5390.1576699800142%40Atlassian.JIRA.
Jira (PUP-10034) Implement DELETE, HEAD, POST
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10034 Implement DELETE, HEAD, POST Change By: Josh Cooper Fix Version/s: PUP 6.12.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326122.1569365544000.5382.1576699560123%40Atlassian.JIRA.
Jira (PUP-10034) Implement DELETE, HEAD, POST
Title: Message Title Josh Cooper commented on PUP-10034 Re: Implement DELETE, HEAD, POST Merged to master in https://github.com/puppetlabs/puppet/commit/55ca3acbbcc2aa91a3dab3b20046ecdd960746c5 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326122.1569365544000.5379.1576699500635%40Atlassian.JIRA.
Jira (PDB-4606) Partition the reports table
Title: Message Title Robert Roland created an issue PuppetDB / PDB-4606 Partition the reports table Issue Type: Story Assignee: Robert Roland Components: PuppetDB Created: 2019/12/18 10:39 AM Priority: Normal Reporter: Robert Roland The report table needs to be partitioned by day, like the resource_events table, to optimize storage and make it easier to deal with additional data being added from Bolt. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10160) Puppet should not load types and providers during environment convergence
Title: Message Title Melissa Stone commented on PUP-10160 Re: Puppet should not load types and providers during environment convergence Merged into 5.5.x with https://github.com/puppetlabs/puppet/commit/e98edbe9197b541982f256d50485aa4aa901b921 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.337880.157548855.5011.1576693680815%40Atlassian.JIRA.
Jira (FACT-2258) Facter does not detect t3a instances on AWS
Title: Message Title
Mihai Buzgau updated an issue
Facter / FACT-2258
Facter does not detect t3a instances on AWS
Change By:
Mihai Buzgau
On PE version 2019.2.1 Agent version 6.10.1 (Windows)Facter version: 3.14.5 seems facter is not correctly detecting AWS EC2 t3a instances, as the {{ec2_metadata}} fact won’t shop up on these machines. Fact info I’m getting from a t3a.small or t3a.medium EC2 instance:{code:java} dmi: { "bios" :{ "release_date" : "10/16/2017", "vendor" : "Amazon EC2", "version" : "1.0" }, "board" :{ "asset_tag" : "i-04d4699a2ac8f0206", "manufacturer" : "Amazon EC2" }, "chassis" :{ "asset_tag" : "Amazon EC2", "type" : "Other" }, "manufacturer" : "Amazon EC2", "product" :{ "name" : "t3a.small", "serial_number" : "ec2e1c0f-43da-7dca-7ccf-2772fa8ab624", "uuid" : "EC2E1C0F-43DA-7DCA-7CCF-2772FA8AB624" }}is_virtual:true processors:{ "count" : 2, "isa" : "x86_64", "models" : [ "AMD EPYC 7571", "AMD EPYC 7571" ], "physicalcount" : 1 }productname:t3a.small virtual:kvm {code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-2258) Facter does not detect t3a instances on AWS
Title: Message Title Kevin Reeuwijk updated an issue Facter / FACT-2258 Facter does not detect t3a instances on AWS Change By: Kevin Reeuwijk Affects Version/s: FACT 3.14.5 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340118.1576692534000.4985.1576692960455%40Atlassian.JIRA.
Jira (FACT-2258) Facter does not detect t3a instances on AWS
Title: Message Title
Mihai Buzgau updated an issue
Facter / FACT-2258
Facter does not detect t3a instances on AWS
Change By:
Mihai Buzgau
On PE 2019.2.1 seems facter is not correctly detecting AWS EC2 t3a instances, as the {{ec2_metadata}} fact won’t shop up on these machines. Fact info I’m getting from a t3a.small or t3a.medium EC2 instance:{code:java} dmi: { "bios" :{ "release_date" : "10/16/2017", "vendor" : "Amazon EC2", "version" : "1.0" }, "board" :{ "asset_tag" : "i-04d4699a2ac8f0206", "manufacturer" : "Amazon EC2" }, "chassis" :{ "asset_tag" : "Amazon EC2", "type" : "Other" }, "manufacturer" : "Amazon EC2", "product" :{ "name" : "t3a.small", "serial_number" : "ec2e1c0f-43da-7dca-7ccf-2772fa8ab624", "uuid" : "EC2E1C0F-43DA-7DCA-7CCF-2772FA8AB624" }}is_virtual:true processors:{ "count" : 2, "isa" : "x86_64", "models" : [ "AMD EPYC 7571", "AMD EPYC 7571" ], "physicalcount" : 1 }productname:t3a.small virtual:kvm {code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-2258) Facter does not detect t3a instances on AWS
Title: Message Title
Mihai Buzgau created an issue
Facter / FACT-2258
Facter does not detect t3a instances on AWS
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/12/18 10:08 AM
Priority:
Normal
Reporter:
Mihai Buzgau
seems facter is not correctly detecting AWS EC2 t3a instances, as the ec2_metadata fact won’t shop up on these machines. Fact info I’m getting from a t3a.small or t3a.medium EC2 instance:
dmi: {
"bios" :
{ "release_date" : "10/16/2017", "vendor" : "Amazon EC2", "version" : "1.0" }
,
"board" :
{ "asset_tag" : "i-04d4699a2ac8f0206", "manufacturer" : "Amazon EC2" }
Jira (PUP-10178) split function shouldn't coerce strings to regex
Title: Message Title Henrik Lindberg commented on PUP-10178 Re: split function shouldn't coerce strings to regex This is for historic reasons - the split function has been doing this since the very start. If this is changed it will need to be changed on a major version boundary as results will be different. The change would need some kind of deprecation - which is tricky as it would be for every call to split where it is given a string. Users would need to convert to regexp to avoid the deprecation, then once the major release takes place the function would stop turning strings into regexp. Alternatively, an option (use_as_string Bool) could be added to the function to tell it what to do - i.e. without option it would be backwards compatible. This would be trivial to add and can be added in any version. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.339939.1576610242000.4405.1576668480232%40Atlassian.JIRA.
Jira (FACT-2203) identity fact for OSX
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-2203 identity fact for OSX Change By: Dorin Pleava Assignee: Dorin Pleava 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338908.1576053116000.4342.1576663800190%40Atlassian.JIRA.
Jira (FACT-2257) Handle ruby native extensions in Facter NG
Title: Message Title Mihai Buzgau created an issue Facter / FACT-2257 Handle ruby native extensions in Facter NG Issue Type: Task Assignee: Unassigned Created: 2019/12/18 1:46 AM Priority: Normal Reporter: Mihai Buzgau Right now, puppet gem does not require any native extensions when installing on Linux based platforms. root@grave-dweller:~# gem install puppet Fetching: facter-2.5.6.gem (100%) Successfully installed facter-2.5.6 Fetching: hiera-3.6.0.gem (100%) Successfully installed hiera-3.6.0 Fetching: semantic_puppet-1.0.2.gem (100%) Successfully installed semantic_puppet-1.0.2
