Jira (PUP-10604) Include the puppetserver_gem package provider with core Puppet
Title: Message Title Austin Boyd updated an issue Puppet / PUP-10604 Include the puppetserver_gem package provider with core Puppet Change By: Austin Boyd Zendesk Ticket Count: 1 Zendesk Ticket IDs: 39595 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367865.1596151607000.5854.1596151800143%40Atlassian.JIRA.
Jira (PUP-10604) Include the puppetserver_gem package provider with core Puppet
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-10604 Include the puppetserver_gem package provider with core Puppet Change By: Charlie Sharpsteen CS Priority: Needs Priority Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367865.1596151607000.5851.1596151740175%40Atlassian.JIRA.
Jira (PUP-10604) Include the puppetserver_gem package provider with core Puppet
Title: Message Title Charlie Sharpsteen commented on PUP-10604 Re: Include the puppetserver_gem package provider with core Puppet The break introduced by PUP-6488 derails a PE upgrade as PE compilers will not be able to apply catalogs required to complete their upgrades until the issue is diagnosed and fixed. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367865.1596151607000.5847.1596151680033%40Atlassian.JIRA.
Jira (PUP-10604) Include the puppetserver_gem package provider with core Puppet
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-10604 Include the puppetserver_gem package provider with core Puppet Issue Type: Improvement Affects Versions: PUP 5.5.20, PUP 6.17.0 Assignee: Unassigned Components: Types and Providers Created: 2020/07/30 4:26 PM Priority: Normal Reporter: Charlie Sharpsteen The core puppet types and providers include a puppet_gem provider for the package resource that knows how to interact with the Ruby interpreter bundled with the puppet-agent package. The puppetserver service also bundles its own JRuby interpreter and requires the used of the puppetserver gem command to install packages. There is an unsupported module, puppetlabs/puppetserver_gem, that adds a puppetserver_gem provider for package resources that fills an analogous role. However, having this provider de-coupled from the Puppet core means it can be broken by changes in the core in a way that interferes with upgrades. PUP-6488 was one such instance where the parent Gem provider was altered in a way that was incompatible with puppet_gem and puppetserver_gem. Both providers were patched, but the breakage in puppet_gem was automatically resolved by an upgrade while the breakage in puppetserver_gem requires users to discover, understand, and then upgrade the module. To prevent these sorts of issues, puppetserver_gem provider should be bundled along with puppet_gem by puppet-agent.
Jira (PDB-4832) Partitioned reports table can result in slower PDB queries
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4832 Partitioned reports table can result in slower PDB queries Change By: Austin Blatt Fix Version/s: PDB 6.11.3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367556.1595978337000.5836.1596151500139%40Atlassian.JIRA.
Jira (PDB-4832) Partitioned reports table can result in slower PDB queries
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4832 Partitioned reports table can result in slower PDB queries Change By: Austin Blatt Affects Version/s: PDB 6.10.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367556.1595978337000.5835.1596151500096%40Atlassian.JIRA.
Jira (PDB-4832) Partitioned reports table can result in slower PDB queries
Title: Message Title Austin Blatt assigned an issue to Rob Browning PuppetDB / PDB-4832 Partitioned reports table can result in slower PDB queries Change By: Austin Blatt Assignee: Austin Blatt Rob Browning Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367556.1595978337000.5833.1596151440127%40Atlassian.JIRA.
Jira (PDB-4832) Partitioned reports table can result in slower PDB queries
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4832 Partitioned reports table can result in slower PDB queries Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367556.1595978337000.5794.1596148980026%40Atlassian.JIRA.
Jira (PUP-5823) Puppet agent with splay on windows begets random interval between runs
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-5823 Puppet agent with splay on windows begets random interval between runs Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.115341.1454671876000.5793.1596148920027%40Atlassian.JIRA.
Jira (PUP-3970) Puppet::Util::Windows::String.wide_string should not embed a NULL char
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3970 Puppet::Util::Windows::String.wide_string should not embed a NULL char Change By: Josh Cooper Summary: Should Puppet::Util::Windows::String.wide_string be changed based on Ruby 2.1 should not embed a NULL char Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.67014.1423178692000.5767.1596147600033%40Atlassian.JIRA.
Jira (PDB-4832) Partitioned reports table can result in slower PDB queries
Title: Message Title Eric Thompson assigned an issue to Austin Blatt PuppetDB / PDB-4832 Partitioned reports table can result in slower PDB queries Change By: Eric Thompson Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367556.1595978337000.5676.1596142500027%40Atlassian.JIRA.
Jira (PDB-4832) Partitioned reports table can result in slower PDB queries
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-4832 Partitioned reports table can result in slower PDB queries Change By: Eric Thompson Team: HA Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367556.1595978337000.5675.1596142440078%40Atlassian.JIRA.
Jira (PDB-4783) Disallow sync with broadcast in pdbext
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4783 Disallow sync with broadcast in pdbext Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.362829.1592239603000.5596.1596138240095%40Atlassian.JIRA.
Jira (PDB-4836) Status endpoint returns an exception when postgres is down
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4836 Status endpoint returns an exception when postgres is down Change By: Austin Blatt Release Notes Summary: Previously (since 6.11.0) the status endpoint might return `null` value a status with an exception when it should have returned `false` for `write_db_up?`. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367714.159605225.5594.1596137460084%40Atlassian.JIRA.
Jira (PDB-4836) Status endpoint returns an exception when postgres is down
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4836 Status endpoint returns an exception when postgres is down Change By: Austin Blatt Summary: Return false not nil for write_db_up? status Status endpoint returns an exception when postgres is down Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367714.159605225.5593.1596137460039%40Atlassian.JIRA.
Jira (PDB-4836) Return false not nil for write_db_up? status
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4836
Return false not nil for write_db_up? status
Change By:
Austin Blatt
When PuppetDB cannot connect to PostgreSQL, and a user queries {{/status/v1/services/puppetdb-status}} the status check throws an error instead of reporting that it cannot connect.When PostgreSQL is running, and PuppetDB can connect, you should get a response like{code}{ "service_version": "6.11.2", "service_status_version": 1, "detail_level": "info", "state": "running", "status": {"maintenance_mode?": false,"queue_depth": 0,"read_db_up?": true,"write_db_up?": true,"write_dbs_up?": true,"write_db": { "default": {"up?": true }} }, "active_alerts": [], "service_name": "puppetdb-status"}{code}When postgresql is not running we would _expect_{code}{ "service_version": "6.11.2", "service_status_version": 1, "detail_level": "info", "state": "error", "status": {"maintenance_mode?": false,"queue_depth": 0,"read_db_up?": false,"write_db_up?": false,"write_dbs_up?": false,"write_db": { "default": {"up?": false }} }, "active_alerts": [], "service_name": "puppetdb-status"}{code}but what is _actually_ returned is{code}{ "service_version": "6.11.2", "service_status_version": 1, "detail_level": "info", "state": "unknown", "status": "Status check for puppetdb-status threw an exception: clojure.lang.ExceptionInfo: Output of status-details does not match schema: \n\n\t \u001b[0;33m {:write_db_up? (not (instance? java.lang.Boolean nil))} \u001b[0m \n\n {:type :schema.core/error, :schema {:maintenance_mode? java.lang.Boolean, :queue_depth (maybe Int), :read_db_up? java.lang.Boolean, :write_db_up? java.lang.Boolean, :write_dbs_up? java.lang.Boolean, :write_db {java.lang.String {:up? java.lang.Boolean}}}, :value {:maintenance_mode? false, :queue_depth 0, :read_db_up? false, :write_db_up? nil, :write_dbs_up? false, :write_db {\"default\" {:up? false}}}, :error {:write_db_up? (not (instance? java.lang.Boolean nil))}}", "active_alerts": [], "service_name": "puppetdb-status"}{code}Once PuppetDB can connect to postgres again the status endpoint will return the expected response.
Add Comment
Jira (PDB-4836) Return false not nil for write_db_up? status
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4836 Return false not nil for write_db_up? status Change By: Austin Blatt Affects Version/s: PDB 6.10.2 Affects Version/s: PDB 6.11.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367714.159605225.5591.1596137100100%40Atlassian.JIRA.
Jira (PDB-4836) Return false not nil for write_db_up? status
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4836 Return false not nil for write_db_up? status Change By: Austin Blatt Release Notes Summary: Previously (since 6. 10 11 . 2 0 ) the status endpoint might return `null` value when it should have returned `false` for `write_db_up?`. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367714.159605225.5590.1596137100042%40Atlassian.JIRA.
Jira (PDB-4838) PuppetDB status endpoint errors when it cannot connect to postgres
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4838 PuppetDB status endpoint errors when it cannot connect to postgres Change By: Austin Blatt Release Notes: Bug Fix Release Notes Summary: PuppetDB's status endpoint would throw an error when it could not connect to postgresql. Team: HA Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367841.1596136663000.5587.1596136800026%40Atlassian.JIRA.
Jira (PDB-4838) PuppetDB status endpoint errors when it cannot connect to postgres
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4838 PuppetDB status endpoint errors when it cannot connect to postgres Change By: Austin Blatt Fix Version/s: PDB 6.11.3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367841.1596136663000.5586.1596136740132%40Atlassian.JIRA.
Jira (PDB-4838) PuppetDB status endpoint errors when it cannot connect to postgres
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4838 PuppetDB status endpoint errors when it cannot connect to postgres Change By: Austin Blatt Affects Version/s: PDB 6.11.2 Affects Version/s: PDB 6.11.1 Affects Version/s: PDB 6.11.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367841.1596136663000.5585.1596136740088%40Atlassian.JIRA.
Jira (PDB-4838) PuppetDB status endpoint errors when it cannot connect to postgres
Title: Message Title
Austin Blatt created an issue
PuppetDB / PDB-4838
PuppetDB status endpoint errors when it cannot connect to postgres
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/07/30 12:17 PM
Priority:
Normal
Reporter:
Austin Blatt
When PuppetDB cannot connect to PostgreSQL, and a user queries /status/v1/services/puppetdb-status the status check throws an error instead of reporting that it cannot connect. When PostgreSQL is running, and PuppetDB can connect, you should get a response like
{
"service_version": "6.11.2",
"service_status_version": 1,
"detail_level": "info",
"state": "running",
"status": {
Jira (PUP-9214) Unfinished/confusing description of "user" resource type attribute
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9214 Unfinished/confusing description of "user" resource type attribute Change By: Josh Cooper Component/s: Docs Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.278354.1538420514000.5533.1596134820029%40Atlassian.JIRA.
Jira (PUP-10417) Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet
Title: Message Title Jean Bond commented on PUP-10417 Re: Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet There's no linked docs ticket, nor is there anything flagged for docs (ping or DOCS tab), so I imagine it has not been documented. Kate Medred, you can pick this up; Maggie Dreyer or Justin Stoller, where specifically would you suggest this be documented? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.354928.1586391583000.5465.1596131520596%40Atlassian.JIRA.
Jira (PDB-4837) Add telemetry data for value api
Title: Message Title Margaret Lee created an issue PuppetDB / PDB-4837 Add telemetry data for value api Issue Type: Task Assignee: Unassigned Created: 2020/07/30 10:18 AM Priority: Normal Reporter: Margaret Lee Add telemetry to the value API so we can learn how people are using this endpoint. how often are they hitting it? are they using defaults? if so, which are being used? common date ranges? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10151) Man page `lookup` needs clarification
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10151 Man page `lookup` needs clarification Change By: Josh Cooper Component/s: Docs Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.336383.157444712.5367.1596128160282%40Atlassian.JIRA.
Jira (PUP-10261) X-Hub-Signature check
Title: Message Title Josh Cooper commented on PUP-10261 Re: X-Hub-Signature check It sounds like this is a feature request for Puppet Enterprise Code Manager? Assuming yes, I'm going to move this ticket to that project. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.344469.1580475995000.5354.1596127920032%40Atlassian.JIRA.
Jira (PUP-10598) Remove setting to ignore pluginsync errors
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10598 Remove setting to ignore pluginsync errors Change By: Josh Cooper Fix Version/s: PUP 7.0.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.366911.1595431337000.5351.1596127560038%40Atlassian.JIRA.
Jira (PUP-10442) Remove http file content terminus
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10442 Remove http file content terminus Change By: Josh Cooper Release Notes Summary: It is no longer possible to retrieve http file content using the indirector. Use puppet's builtin HTTP client instead:```client = Puppet.runtime[:http]response = client.get(URI( ' " http://example.com/path ' " ))``` Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356601.1587681255000.5337.1596126900026%40Atlassian.JIRA.
Jira (PUP-10442) Remove http file content terminus
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10442
Remove http file content terminus
Change By:
Josh Cooper
Release Notes:
Bug Fix
Release Notes Summary:
It is no longer possible to retrieve http file content using the indirector. Use puppet's builtin HTTP client instead:```client = Puppet.runtime[:http]response = client.get(URI('http://example.com/path'))```
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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.356601.1587681255000.5332.1596126720080%40Atlassian.JIRA.
Jira (PUP-10107) Unvendor pathspec
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10107 Unvendor pathspec Change By: Josh Cooper Release Notes: Bug Fix Release Notes Summary: The pathspec ruby library is no longer vendored in puppet. Install the pathspec rubygem if this functionality is required. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.331409.1571780406000.5329.1596126600054%40Atlassian.JIRA.
Jira (PUP-10107) Unvendor pathspec
Title: Message Title Josh Cooper commented on PUP-10107 Re: Unvendor pathspec Merged to main in https://github.com/puppetlabs/puppet/commit/20db5e4f95c5e30d6d4e5942c05622caabaf5907 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.331409.1571780406000.5324.1596126360127%40Atlassian.JIRA.
Jira (PUP-10442) Remove http file content terminus
Title: Message Title Josh Cooper commented on PUP-10442 Re: Remove http file content terminus Merged to main in https://github.com/puppetlabs/puppet/commit/8f9e41375273791c0c517cbf63c14cd728b8aafc Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356601.1587681255000.5299.1596125520034%40Atlassian.JIRA.
Jira (FACT-2724) Confine blocks behave differently with Facter 4, causing spec tests to suddenly fail
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2724 Confine blocks behave differently with Facter 4, causing spec tests to suddenly fail Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367390.1595872598000.5175.1596116400032%40Atlassian.JIRA.
Jira (FACT-2735) virtual not working on EXADATA baremetal
Title: Message Title David commented on FACT-2735 Re: virtual not working on EXADATA baremetal [root@cgcldx0001 ~]# lspci 00:00.0 Host bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 DMI2 (rev 04) 00:02.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 2a (rev 04) 00:02.2 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 2c (rev 04) 00:03.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 3a (rev 04) 00:03.2 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 3c (rev 04) 00:04.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 0 (rev 04) 00:04.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 1 (rev 04) 00:04.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 2 (rev 04) 00:04.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 3 (rev 04) 00:04.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 4 (rev 04) 00:04.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 5 (rev 04) 00:04.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 6 (rev 04) 00:04.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 7 (rev 04) 00:05.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 VTd/Memory Map/Misc (rev 04) 00:05.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IIO RAS (rev 04) 00:05.4 PIC: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IOAPIC (rev 04) 00:11.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Virtual Root Port (rev 06) 00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #2 (rev 06) 00:1c.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 1 (rev b6) 00:1c.7 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 8 (rev b6) 00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #1 (rev 06) 00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC Controller (rev 06) 00:1f.2 SATA controller: Intel Corporation C600/X79 series chipset 6-Port SATA AHCI Controller (rev 06) 00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host Controller (rev 06) 00:1f.6 Signal processing controller: Intel Corporation C600/X79 series chipset Thermal Management Controller (rev 06) 20:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01) 20:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01) 30:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) 30:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) 40:00.0 InfiniBand: Mellanox Technologies MT27500 Family [ConnectX-3] 50:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator] (rev 05) 61:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 02) 62:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 21) 7f:0a.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 0 (rev 04) 7f:0a.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 3 (rev 04) 7f:0b.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5
Jira (FACT-2736) networking facts don't work on EXADATA baremetal
Title: Message Title David commented on FACT-2736 Re: networking facts don't work on EXADATA baremetal [root@cgcldx0001 ~]# ip -o address 1: lo: mtu 65536 qdisc noqueue state UNKNOWN \ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 1: lo inet 127.0.0.1/8 scope host lo\ valid_lft forever preferred_lft forever 1: lo inet6 ::1/128 scope host \ valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq state UP qlen 1000\ link/ether 00:10:e0:5c:07:6e brd ff:ff:ff:ff:ff:ff 2: eth0 inet 10.81.228.21/24 brd 10.81.228.255 scope global eth0\ valid_lft forever preferred_lft forever 2: eth0 inet6 fe80::210:e0ff:fe5c:76e/64 scope link \ valid_lft forever preferred_lft forever 3: eth1: mtu 1500 qdisc noop state DOWN qlen 1000\ link/ether 00:10:e0:5c:07:6f brd ff:ff:ff:ff:ff:ff 4: eth4: mtu 1500 qdisc mq master bondeth0 state UP qlen 1000\ link/ether 90:e2:ba:78:a6:38 brd ff:ff:ff:ff:ff:ff 5: eth5: mtu 1500 qdisc mq master bondeth0 state UP qlen 1000\ link/ether 90:e2:ba:78:a6:38 brd ff:ff:ff:ff:ff:ff 6: eth2: mtu 1500 qdisc mq master bondeth1 state UP qlen 1000\ link/ether 00:10:e0:5c:07:70 brd ff:ff:ff:ff:ff:ff 7: eth3: mtu 1500 qdisc mq master bondeth1 state UP qlen 1000\ link/ether 00:10:e0:5c:07:70 brd ff:ff:ff:ff:ff:ff 8: ib0: mtu 7000 qdisc pfifo_fast state UP qlen 4096\ link/infiniband 80:00:02:08:fe:80:00:00:00:00:00:00:00:10:e0:00:01:43:89:21 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff 8: ib0 inet 10.196.1.1/24 brd 10.196.1.255 scope global ib0\ valid_lft forever preferred_lft forever 8: ib0 inet 169.254.63.218/17 brd 169.254.127.255 scope global ib0:1\ valid_lft forever preferred_lft forever 8: ib0 inet6 fe80::210:e000:143:8921/64 scope link \ valid_lft forever preferred_lft forever 9: ib1: mtu 7000 qdisc pfifo_fast state UP qlen 4096\ link/infiniband 80:00:02:09:fe:80:00:00:00:00:00:00:00:10:e0:00:01:43:89:22 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff 9: ib1 inet 10.196.1.2/24 brd 10.196.1.255 scope global ib1\ valid_lft forever preferred_lft forever 9: ib1 inet 169.254.245.38/17 brd 169.254.255.255 scope global ib1:1\ valid_lft forever preferred_lft forever 9: ib1 inet6 fe80::210:e000:143:8922/64 scope link \ valid_lft forever preferred_lft forever 10: bond0: mtu 1500 qdisc noop state DOWN \ link/ether da:40:75:62:7c:ed brd ff:ff:ff:ff:ff:ff 11: bondeth0: mtu 1500 qdisc noqueue state UP \ link/ether 90:e2:ba:78:a6:38 brd ff:ff:ff:ff:ff:ff 11: bondeth0 inet 10.81.236.42/27 brd 10.81.236.63 scope global bondeth0\ valid_lft forever preferred_lft forever 11: bondeth0 inet 10.81.236.43/27 brd 10.81.236.63 scope global secondary bondeth0:1\ valid_lft forever preferred_lft forever 11: bondeth0 inet 10.81.236.48/27 brd 10.81.236.63 scope global secondary bondeth0:2\ valid_lft forever preferred_lft forever 11: bondeth0 inet6 fe80::92e2:baff:fe78:a638/64 scope link \ valid_lft forever preferred_lft forever 12: bondeth1: mtu 1500 qdisc noqueue state UP \ link/ether 00:10:e0:5c:07:70 brd ff:ff:ff:ff:ff:ff 12: bondeth1 inet 10.81.252.42/27 brd 10.81.252.63 scope global bondeth1\ valid_lft forever preferred_lft forever 12: bondeth1 inet6 fe80::210:e0ff:fe5c:770/64 scope link \ valid_lft forever preferred_lft forever
Jira (FACT-2736) networking facts don't work on EXADATA baremetal
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2736 networking facts don't work on EXADATA baremetal Change By: Bogdan Irimie Summary: netwokring networking facts don't work on EXADATA baremetal Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367756.1596109644000.5159.1596111900099%40Atlassian.JIRA.
Jira (FACT-2735) virtual not working on EXADATA baremetal
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2735 virtual not working on EXADATA baremetal Change By: Bogdan Irimie Issue Type: Task Bug Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367746.1596106786000.5158.1596111900045%40Atlassian.JIRA.
Jira (FACT-2736) netwokring facts don't work on EXADATA baremetal
Title: Message Title Bogdan Irimie commented on FACT-2736 Re: netwokring facts don't work on EXADATA baremetal David can you please provide the output from ip -o address on `EXADATA baremetal` The output would help us identify what happens in our `networking_linux_resolver` Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367756.1596109644000.5156.1596110580022%40Atlassian.JIRA.
Jira (FACT-2736) netwokring facts don't work on EXADATA baremetal
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2736 netwokring facts don't work on EXADATA baremetal Change By: Bogdan Irimie Issue Type: Task Bug Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367756.1596109644000.5155.1596109980066%40Atlassian.JIRA.
Jira (FACT-2736) netwokring facts don't work on EXADATA baremetal
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2736
netwokring facts don't work on EXADATA baremetal
Change By:
Bogdan Irimie
When running facter on `EXADATA baremetal`, running Oracle Linux{code}Linux cgcldx0001.cadc3.oraclecloud.com 4.1.12-94.7.8.el6uek.x86_64 #2 SMP Thu Jan 11 20:41:01 PST 2018 x86_64 x86_64 x86_64 GNU/Linux{code}the networking resolver throws and exception.{code}[2020-07-27 14:15:25.884185 ] ERROR Facter::InternalFactManager - uninitialized constant #::IPAddr /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/utils/networking.rb:13:in `build_binding'/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/networking_linux_resolver.rb:96:in `fill_ip_v4_info!'/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/networking_linux_resolver.rb:45:in `block in retrieve_interface_info'/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/networking_linux_resolver.rb:42:in `each_line'/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/networking_linux_resolver.rb:42:in `retrieve_interface_info'/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/networking_linux_resolver.rb:22:in `retrieve_network_info'/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/networking_linux_resolver.rb:14:in `block in post_resolve'/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/networking_linux_resolver.rb:14:in `fetch'/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/networking_linux_resolver.rb:14:in `post_resolve'/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/base_resolver.rb:21:in `block in resolve'/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/base_resolver.rb:19:in `synchronize'/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/base_resolver.rb:19:in `resolve'/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/facts/linux/ipaddress6_interfaces.rb:11:in `call_the_resolver'/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/framework/core/fact/internal/core_fact.rb:12:in `create'/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/framework/core/fact/internal/internal_fact_manager.rb:41:in `block (2 levels) in start_threads'{code}
Jira (FACT-2736) netwokring facts don't work on EXADATA baremetal
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2736 netwokring facts don't work on EXADATA baremetal Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367756.1596109644000.5153.1596109680099%40Atlassian.JIRA.
Jira (FACT-2736) netwokring facts don't work on EXADATA baremetal
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2736 netwokring facts don't work on EXADATA baremetal Issue Type: Task Assignee: Unassigned Created: 2020/07/30 4:47 AM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367756
Jira (FACT-2735) virtual not working on EXADATA baremetal
Title: Message Title Bogdan Irimie commented on FACT-2735 Re: virtual not working on EXADATA baremetal Also, David could you please run bundle exec facter --debug with the code from FACT-2735 PR and provide the output? The code contains extra logging that could help us determine what is happening. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367746.1596106786000.5151.1596109500088%40Atlassian.JIRA.
Jira (FACT-2735) virtual not working on EXADATA baremetal
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2735 virtual not working on EXADATA baremetal Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367746.1596106786000.5136.1596107160093%40Atlassian.JIRA.
Jira (FACT-2735) virtual not working on EXADATA baremetal
Title: Message Title Bogdan Irimie commented on FACT-2735 Re: virtual not working on EXADATA baremetal David can you please provide the output of `lspci` command when you run in on `EXADATA baremetal`. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367746.1596106786000.5132.1596107100096%40Atlassian.JIRA.
Jira (FACT-2735) virtual not working on EXADATA baremetal
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2735
virtual not working on EXADATA baremetal
Change By:
Bogdan Irimie
On `EXADATA baremetal` running Oracle Linux {code:java} Linux cgcldx0001.cadc3.oraclecloud.com 4.1.12-94.7.8.el6uek.x86_64 #2 SMP Thu Jan 11 20:41:01 PST 2018 x86_64 x86_64 x86_64 GNU/Linux{code}`virtual` fact returns {code:java}virtual: "00:00.0 Host bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 DMI2(rev 04)\n00:02.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCIExpress Root Port 2a (rev 04)\n00:02.2 PCI bridge: Intel Corporation Xeon E7 v2/XeonE5 v2/Core i7 PCI Express Root Port 2c (rev 04)\n00:03.0 PCI bridge: Intel CorporationXeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 3a (rev 04)\n00:03.2 PCI bridge:Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 3c (rev 04)\n00:04.0System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal BeachDMA Channel 0 (rev 04)\n00:04.1 System peripheral: Intel Corporation Xeon E7 v2/XeonE5 v2/Core i7 Crystal Beach DMA Channel 1 (rev 04)\n00:04.2 System peripheral: IntelCorporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 2 (rev 04)\n00:04.3System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal BeachDMA Channel 3 (rev 04)\n00:04.4 System peripheral: Intel Corporation Xeon E7 v2/XeonE5 v2/Core i7 Crystal Beach DMA Channel 4 (rev 04)\n00:04.5 System peripheral: IntelCorporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 5 (rev 04)\n00:04.6System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal BeachDMA Channel 6 (rev 04)\n00:04.7 System peripheral: Intel Corporation Xeon E7 v2/XeonE5 v2/Core i7 Crystal Beach DMA Channel 7 (rev 04)\n00:05.0 System peripheral: IntelCorporation Xeon E7 v2/Xeon E5 v2/Core i7 VTd/Memory Map/Misc (rev 04)\n00:05.2System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IIO RAS (rev04)\n00:05.4 PIC: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IOAPIC (rev 04)\n00:11.0PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Virtual Root Port(rev 06)\n00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2Enhanced Host Controller #2 (rev 06)\n00:1c.0 PCI bridge: Intel Corporation C600/X79series chipset PCI Express Root Port 1 (rev b6)\n00:1c.7 PCI bridge: Intel CorporationC600/X79 series chipset PCI Express Root Port 8 (rev b6)\n00:1d.0 USB controller:Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #1 (rev06)\n00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC Controller(rev 06)\n00:1f.2 SATA controller: Intel Corporation C600/X79 series chipset 6-PortSATA AHCI Controller (rev 06)\n00:1f.3 SMBus: Intel Corporation C600/X79 serieschipset SMBus Host Controller (rev 06)\n00:1f.6 Signal processing controller: IntelCorporation C600/X79 series chipset Thermal Management Controller (rev 06)\n20:00.0Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev01)\n20:00.1 Ethernet
Jira (FACT-2735) virtual not working on EXADATA baremetal
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2735 virtual not working on EXADATA baremetal Issue Type: Task Assignee: Unassigned Created: 2020/07/30 3:59 AM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367746.1596106
Jira (FACT-2734) redhat_release_resolver fails when there is no codename in /etc/redhat-relase
Title: Message Title Bogdan Irimie commented on FACT-2734 Re: redhat_release_resolver fails when there is no codename in /etc/redhat-relase David can you please give the code on 4.x branch a try. The PR was already merged and it should fix the problem of Facter not starting on Xen, DOM-0 with `Oracle VM server release 3.4.4` Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367744.1596097347000.5126.1596106020087%40Atlassian.JIRA.
Jira (FACT-2734) redhat_release_resolver fails when there is no codename in /etc/redhat-relase
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2734
redhat_release_resolver fails when there is no codename in /etc/redhat-relase
Change By:
Bogdan Irimie
On Xen, DOM-0 (hypervisor){code}cat /etc/redhat-releaseOracle VM server release 3.4.4{code}Facter fails with {code}/usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/redhat_release_resolver.rb:36:in `build_fact_list': undefined method `strip' for nil:NilClass (NoMethodError)from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/redhat_release_resolver.rb:24:in `read_redhat_release'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/redhat_release_resolver.rb:17:in `block in post_resolve'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/redhat_release_resolver.rb:17:in `fetch'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/redhat_release_resolver.rb:17:in `post_resolve'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/base_resolver.rb:21:in `block in resolve'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/base_resolver.rb:19:in `synchronize'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/resolvers/base_resolver.rb:19:in `resolve'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/framework/detector/os_detector.rb:66:in `block in detect_distro'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/framework/detector/os_detector.rb:65:in `each'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/framework/detector/os_detector.rb:65:in `detect_distro'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/framework/detector/os_detector.rb:26:in `detect'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/framework/detector/os_detector.rb:13:in `initialize'from /usr/local/peo/tools/ruby/lib/ruby/2.3.0/singleton.rb:142:in `new'from /usr/local/peo/tools/ruby/lib/ruby/2.3.0/singleton.rb:142:in `block in instance'from /usr/local/peo/tools/ruby/lib/ruby/2.3.0/singleton.rb:140:in `synchronize'from /usr/local/peo/tools/ruby/lib/ruby/2.3.0/singleton.rb:140:in `instance'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/framework/core/file_loader.rb:47:in `'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter.rb:7:in `require'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter.rb:7:in `'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter/framework/cli/cli_launcher.rb:7:in `require'from /usr/local/peo/tools/facter/vendor/bundle/ruby/2.3.0/gems/facter-4.0.30/lib/facter
Jira (FACT-2734) redhat_release_resolver fails when there is no codename in /etc/redhat-relase
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-2734 redhat_release_resolver fails when there is no codename in /etc/redhat-relase Change By: Oana Tanasoiu Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367744.1596097347000.5083.1596099600196%40Atlassian.JIRA.
Jira (FACT-2725) Investigate changelog generator
Title: Message Title Florin Dragos assigned an issue to Florin Dragos Facter / FACT-2725 Investigate changelog generator Change By: Florin Dragos Assignee: Florin Dragos Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367645.1596026969000.5076.1596099240028%40Atlassian.JIRA.
Jira (PDB-4830) Big performance impact when upgrading to PuppetDB5/6
Title: Message Title
Nacho Barrientos commented on PDB-4830
Re: Big performance impact when upgrading to PuppetDB5/6
Thanks once again for your time.
Is it important for your usecase that only the queries like /pdb/query/v4/facts// are performant, or do you also make use of queries that don't provide the value, like /pdb/query/v4/facts/?
It'd be a good starting point but to be honest it would not be enough. Most of our queries (generated by the module above) talk directly to /pdb/query/v4/facts passing a query, for example: "Get the value of the ipaddress fact for nodes whose fact fact1 has x as value, fact fact2 has y and fact fact3 has z": via the query_nodes() function:
query_nodes('fact1="x" and fact2="y" and fact3="z"', ipaddress)
translates into:
GET pdb/query/v4/facts --query
'["extract",["value"],["and",["and",["in","certname",["extract","certname",["select_fact_contents",["and",["=","path",["fact2"]],["=","value","y"],["in","certname",["extract","certname",["select_fact_contents",["and",["=","path",["fact1"]],["=","value","x"],["in","certname",["extract","certname",["select_fact_contents",["and",["=","path",["fact3"]],["=","value","z"]],["or",["=","name","ipaddress"'
# PuppetDB 4
real0m0.471s
# PuppetDB 5
real0m16.302s
Jira (FACT-2715) 'is_virtual' fact is true on a baremetal Exadata host
Title: Message Title Bogdan Irimie commented on FACT-2715 Re: 'is_virtual' fact is true on a baremetal Exadata host Hi David, Thank you for the output from `/etc/redhat-release` and `/etc/os-release`, it already helped us identify one of the problems As there are 3 different configurations (Exadata, DOM-0 and DOM-U), I will try to break this task in more focused tickets that try to solve one problem on one platform at a time. On DOM-0, Facter 4 failed to start, I assume this happens because of https://tickets.puppetlabs.com/browse/FACT-2734 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.366495.1595192254000.5061.1596097920096%40Atlassian.JIRA.
Jira (FACT-2734) redhat_release_resolver fails when there is no codename in /etc/redhat-relase
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2734 redhat_release_resolver fails when there is no codename in /etc/redhat-relase Change By: Bogdan Irimie Issue Type: Task Bug Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367744.1596097347000.5062.1596097920139%40Atlassian.JIRA.
Jira (FACT-2734) redhat_release_resolver fails when there is no codename in /etc/redhat-relase
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2734 redhat_release_resolver fails when there is no codename in /etc/redhat-relase Issue Type: Task Assignee: Unassigned Created: 2020/07/30 1:22 AM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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/
Jira (FACT-2734) redhat_release_resolver fails when there is no codename in /etc/redhat-relase
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2734 redhat_release_resolver fails when there is no codename in /etc/redhat-relase Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.367744.1596097347000.5057.1596097380103%40Atlassian.JIRA.
Jira (FACT-2479) Uptime facts on LXC get the uptime from the host OS and not the container.
Title: Message Title Florin Dragos commented on FACT-2479 Re: Uptime facts on LXC get the uptime from the host OS and not the container. Atanas Stoyanov, can you please provide some environment information like os/version ? I've tried reproducing on ubuntu 18.04 and it looks like the uptime is ok: root@antique-counter:~# facter uptime 0:42 hours root@antique-counter:~# lxc exec ubuntu -- facter uptime 0:13 hours Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
