Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

", "projectKey": "FACT", "projectLead": "70121:199f31c7-67c7-42b0-b148-18ad3a391ab0", "projectName": "Facter (Archived)", "projectType": "software", "projectUrl": null, "reporter": "557058:91233464-4152-4228-81dd-172d43a52a03", "status": "In Progress", "statusCategory": "In Progress", "statuscategorychangedate": "11/Mar/23 10:29 AM", "summary": "Switch to relative_require", "timeSpent": "PT0S", "updated": "2023-03-09T11:10:00.000000", "votes": "0", "watchers": []}, {"affectedVersions": [], "assignee": null, "attachments": [], "comments": [{"author": "557058:91233464-4152-4228-81dd-172d43a52a03", "body": "Hi [~accountid:61bbace0755091006a2b896a] facter has a hard dependency on sys-filesystem because it allows us to generate core facts without reinventing the wheel. But I don't think any core facts are missing due to lack of sys-proctable, so I'm going to close this. It's probably best if you create a module to install the gem (using the \"puppet_gem\" package provider) and any custom facts that rely on the gem.", "created": "2023-02-14T14:34:00.000000"}], "components": [], "created": "2023-02-08T04:23:00.000000", "creator": "61bbace0755091006a2b896a", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@12849d15"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|o0lvwh:"}, {"fieldName": "[CHART] Date of First Response", "fieldType": "com.atlassian.jira.ext.charting:firstresponsedate", "value": "14/Feb/23"}, {"fieldName": "[CHART] Time in Status", "fieldType": "com.atlassian.jira.ext.charting:timeinstatus", "value": "1_*:*_1_*:*_555059502_*|*_6_*:*_1_*:*_0"}], "description": "in facts often i want to access the process table. but i dont want to exec ps and grep and transform the data all the time. there is a gem wich does this in a propper ruby way djberg96/sys-proctable. we already have sys-filesystem in the gemset, so this would be a good addition.\n\ntalked already a bit with [~accountid:557058:ddaa4b87-3b61-49bb-98f9-56fd02cdbb6b] at ConfgMgmtCmp about it.\u00a0\n\nif this is the wrong project, feel free to move it where it fits.", "epicLinkSummary": null, "estimate": "PT0S", "externalId": "62079", "fixedVersions": [], "id": "62079", "issueType": "Task", "key": "FACT-3183", "labels": [], "originalEstimate": "PT0S", "parent": null, "parentSummary": null, "priority": "Normal", "projectDescription": "

Welcome to your project

Describe your project here

Welcome to your project

Describe your project here

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

", "projectKey": "FACT", "projectLead": "70121:199f31c7-67c7-42b0-b148-18ad3a391ab0", "projectName": "Facter (Archived)", "projectType": "software", "projectUrl": null, "reporter": "623c0c4cee1b5a007029321b", "status": "Ready for Merge", "statusCategory": "In Progress", "statuscategorychangedate": "11/Mar/23 10:29 AM", "summary": "Size calculations for AIX blockdevice and partitions", "timeSpent": "PT0S", "updated": "2023-02-24T12:29:00.000000", "votes": "0", "watchers": []}, {"affectedVersions": [], "assignee": null, "attachments": [], "comments": [], "components": [], "created": "2022-10-08T08:00:00.000000", "creator": "623c12b950bb2b0070b6b384", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@7dd400ec"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "Epic Link", "fieldType": "com.pyxis.greenhopper.jira:gh-epic-link", "value": "PUP-11619"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "Method Found", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|o0k5f5:"}, {"fieldName": "Release Notes", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Bug Fix"}, {"fieldName": "Release Notes Summary", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:textarea", "value": "facter's install.rb script is now compatible with Ruby 3.x\nCommunity contribution from https://github.com/jcharaoui"}, {"fieldName": "Story Points", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:float", "value": "1.0"}, {"fieldName": "[CHART] Time in Status", "fieldType": "com.atlassian.jira.ext.charting:timeinstatus", "value": "10008_*:*_1_*:*_432270082_*|*_1_*:*_1_*:*_281102587_*|*_10007_*:*_1_*:*_159028952_*|*_5_*:*_1_*:*_0"}], "description": "The install.rb script fails when running on Ruby 3.0.0:\n\n\n{quote}./install.rb --destdir=debian/facter --sitelibdir=/usr/lib/ruby/vendor_ruby --ruby=/usr/bin/ruby\n/usr/lib/ruby/3.0.0/fileutils.rb:865:in `install': wrong number of arguments (given 3, expected 2) (ArgumentError)\n from ./install.rb:75:in `block in do_libs'\n from ./install.rb:70:in `each'\n from ./install.rb:70:in `do_libs'\n from ./install.rb:287:in `block in run'\n from /usr/lib/ruby/3.0.0/fileutils.rb:139:in `chdir'\n from /usr/lib/ruby/3.0.0/fileutils.rb:139:in `cd'\n from ./install.rb:277:in `run'\n from ./install.rb:293:in `

'{quote}\n", "epicLinkSummary": "Puppet Maintenance CY22 Q4", "estimate": "PT0S", "externalId": "62444", "fixedVersions": ["FACT 4.2.14"], "id": "62444", "issueType": "Bug", "key": "FACT-3159", "labels": [], "originalEstimate": "PT0S", "parent": "26723", "parentSummary": "Puppet Maintenance CY22 Q4", "priority": "Normal", "projectDescription": "

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

", "projectKey": "FACT", "projectLead": "70121:199f31c7-67c7-42b0-b148-18ad3a391ab0", "projectName": "Facter (Archived)", "projectType": "software", "projectUrl": null, "reporter": "557058:06f72a0b-6e3a-4c35-be93-e0c1fe6e150d", "status": "Accepted", "statusCategory": "To Do", "statuscategorychangedate": "11/Mar/23 10:29 AM", "summary": "Add Block Groups to GCE Facts", "timeSpent": "PT0S", "updated": "2022-08-03T07:15:00.000000", "votes": "0", "watchers": []}, {"affectedVersions": [], "assignee": null, "attachments": [], "comments": [{"author": "62ccea54bd54f8d3ffb61ce1", "body": "I'm not sure why calling the ruby functions below using inline_template provides the old value {*}UTC{*}, but facts that use them (such as [https://github.com/puppetlabs/facter/blob/e5ad338bb6b5909c1d84cc7a580dc5dafed77e68/lib/facter/resolvers/timezone.rb#L16)] show the correct value *MST* when run manually with {*}puppet agent -t{*}.\n{code:java}inline_template(\"<%= Time.now.localtime.strftime('%Z') %>\\n\") // UTC\ninline_template(\"<%= Time.now.zone %>\\n\") // UTC\n$facts['timezone'] // MST\n$facts['timezone_custom'] // MST\u00a0 \u00a0 ", "created": "2022-06-02T18:05:00.000000"}, {"author": "62ccea54bd54f8d3ffb61ce1", "body": "Restarting the puppetserver service on the Puppet master server appears to fix this issue. Not sure why it is keeping the old value until the restart though. And only for the automated agent check-in, not the manual *puppet agent -t* command.", "created": "2022-06-02T18:12:00.000000"}, {"author": "62ccea54bd54f8d3ffb61ce1", "body": "It looks like the server facts on the Puppet master are not updated after the initial connection. For instance, I just changed the server timezone to America/Chicago, but the facts still show MST.\n{code:java}[root@puppet-master production]# timedatectl set-timezone \"America/Chicago\"\n[root@puppet-master production]# puppet agent -t\n{code}\n...\n{code:java}[root@puppet-master production]# cat /opt/puppetlabs/server/data/puppetserver/server_data/facts/puppet-master.test.local.json | jq | grep timezone\n\u00a0 \u00a0 \"timezone\": \"MST\",\n\u00a0 \u00a0 \"timezone_custom\": \"MST\",\n[root@puppet-master production]# tail -n +1 /tmp/output*.txt\n==> /tmp/output1.txt <==\nCDT\n==> /tmp/output2.txt <==\nCDT\n==> /tmp/output3.txt <==\nMST\n{code}", "created": "2022-06-02T18:22:00.000000"}, {"author": "62ccea54bd54f8d3ffb61ce1", "body": "Facter upload changes the JSON file on the Puppet master, but the issue still persists until puppetserver.service is restarted.\n\n[root@puppet-master production]# facter upload\n\n[root@puppet-master production]# cat /opt/puppetlabs/server/data/puppetserver/server_data/facts/puppet-master.test.local.json | jq | grep timezone\n{code:java}\u00a0 \u00a0 \"timezone\": \"CDT\",\n\u00a0 \u00a0 \"timezone_custom\": \"CDT\",{code}\n{code:java}==> /tmp/output1.txt <==\nCDT\n==> /tmp/output2.txt <==\nCDT\n==> /tmp/output3.txt <==\nMST\n{code}", "created": "2022-06-02T18:42:00.000000"}, {"author": "557058:4786f794-5167-4041-b3c0-deb1e8ba3438", "body": "[~accountid:62ccea54bd54f8d3ffb61ce1] puppet-server uses jRuby and handles timezones differently. ", "created": "2022-06-07T14:21:00.000000"}], "components": ["Community", "Facter 4"], "created": "2022-06-02T16:00:00.000000", "creator": "62ccea54bd54f8d3ffb61ce1", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@280f0194"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "Method Found", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|o0gutd:"}, {"fieldName": "[CHART] Date of First Response", "fieldType": "com.atlassian.jira.ext.charting:firstresponsedate", "value": "07/Jun/22"}, {"fieldName": "[CHART] Time in Status", "fieldType": "com.atlassian.jira.ext.charting:timeinstatus", "value": "1_*:*_1_*:*_426066275_*|*_6_*:*_1_*:*_0"}], "description": "I have an example scenario where my server timezone is originally *UTC* on boot, but then manually changed to *MST* a few minutes after boot. Manual runs of\u00a0*puppet agent -t* show the timezone fact has the current (correct) value of {*}MST{*}, but when the agent periodically checks in with the master (automated) it shows the original (bad) value of {*}UTC{*}. It seems like the automated agent check-in might be using cached facts or old facts?\n\n\u00a0\n\nPuppet: 7.16.0\n\nRuby: ruby 2.7.6p219 (2022-04-12 revision c9c2245c0a) [x86_64-linux]\n\nDistribution: CentOS 7.9.2009\n\n--------------------------------------------\n{code:java}/etc/puppetlabs/code/environments/production/manifests/site.pp:\nnode default\n{ \u00a0 include ::role::base_app }\n{code}\n----------------------------------------\n{code:java}/etc/puppetlabs/code/environments/production/site/role/manifests/base_app.pp:\nclass role::base_app\n{ \u00a0 include profile::security::base }\n{code}\n----------------------------------------\n{code:java}/etc/puppetlabs/code/environments/production/site/profile/manifests/security/base.pp:\nclass profile::security::base (\n) {\n\u00a0 $tz = $facts['timezone']\n\u00a0 file{ \"/tmp/output1.txt\": content => \"$tz\\n\" }\n\u00a0 file { \"/tmp/output2.txt\": \u00a0 \u00a0 content => inline_template(\"<%= @timezone %>\\n\") \u00a0 }\n\u00a0 file{ \"/tmp/output3.txt\": \u00a0 \u00a0 content => inline_template(\"<%= Time.now.localtime.strftime('%Z') %>\\n\") \u00a0 }\n}\n{code}\n----------------------------------------\n\nManual run of\u00a0{*}puppet agent -t{*}.\n{code:java}==> /tmp/output1.txt <==\nMST\n==> /tmp/output2.txt <==\nMST\n==> /tmp/output3.txt <==\nUTC\n{code}\n----------------------------------------\n\nAutomated agent check-in:\n{code:java}==> /tmp/output1.txt <==\nUTC\n==> /tmp/output2.txt <==\nUTC\n==> /tmp/output3.txt <==\nUTC\n{code}\nThe *facter -p*\u00a0continues to show the timezone fact as\u00a0{*}MST{*}, even after the automated agent runs.\n{code:java}[root@puppet-master production]# facter -p | grep -i timezone\ntimezone => MST\n[root@puppet-master production]# /opt/puppetlabs/puppet/bin/ruby -e \"puts Time.now.localtime.strftime('%Z')\"\nMST\n{code}", "epicLinkSummary": null, "estimate": "PT0S", "externalId": "61503", "fixedVersions": [], "id": "61503", "issueType": "Bug", "key": "FACT-3125", "labels": [], "originalEstimate": "PT0S", "parent": null, "parentSummary": null, "priority": "Normal", "projectDescription": "

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

", "projectKey": "FACT", "projectLead": "70121:199f31c7-67c7-42b0-b148-18ad3a391ab0", "projectName": "Facter (Archived)", "projectType": "software", "projectUrl": null, "reporter": "70121:13e9ba64-d0e3-4303-948b-08ee1e68f2de", "status": "Needs Information", "statusCategory": "To Do", "statuscategorychangedate": "11/Mar/23 10:29 AM", "summary": "partition `mounted_as` attribue", "timeSpent": "PT0S", "updated": "2022-05-24T14:33:00.000000", "votes": "0", "watchers": []}, {"affectedVersions": [], "assignee": null, "attachments": [], "comments": [{"author": "557058:5176c2d2-2593-4064-a449-19964b30258e", "body": "https://github.com/puppetlabs/facter/pull/2492", "created": "2022-05-10T11:47:00.000000"}], "components": ["Facter 4"], "created": "2022-05-10T11:44:00.000000", "creator": "557058:5176c2d2-2593-4064-a449-19964b30258e", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@935638c"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "Method Found", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|hyk3z5:r9090004"}, {"fieldName": "Story Points", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:float", "value": "1.0"}], "description": "{{facter virtual}} returns {{lxc}}. Illumos (SmartOS/OmniOS) LX is a Linux syscall emulation layer, not an LXC Linux Container. It would be helpful if Facter could return a more accurate result.", "environment": "https://en.wikipedia.org/wiki/SmartOS#LX_(Linux_Emulation)\nvs\nhttps://en.wikipedia.org/wiki/LXC", "epicLinkSummary": null, "estimate": "PT0S", "externalId": "62065", "fixedVersions": [], "id": "62065", "issueType": "Bug", "key": "FACT-3121", "labels": [], "originalEstimate": "PT0S", "parent": null, "parentSummary": null, "priority": "Normal", "projectDescription": "

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Welcome to your project

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

", "projectKey": "FACT", "projectLead": "70121:199f31c7-67c7-42b0-b148-18ad3a391ab0", "projectName": "Facter (Archived)", "projectType": "software", "projectUrl": null, "reporter": "5f8ea473461cc400752375b3", "status": "Needs Information", "statusCategory": "To Do", "statuscategorychangedate": "11/Mar/23 10:29 AM", "summary": "Facter allowlist", "timeSpent": "PT0S", "updated": "2021-10-01T12:54:00.000000", "votes": "0", "watchers": []}, {"affectedVersions": [], "assignee": null, "attachments": [], "comments": [{"author": "70121:4596f954-1fdf-472f-a700-6b7c2ffbc525", "body": "[~accountid:623e79d48d8b9c0068b9f47f], on which OS is this happening?", "created": "2021-09-02T05:18:00.000000"}, {"author": "623e79d48d8b9c0068b9f47f", "body": "The OS is Windows 2019.", "created": "2021-09-03T13:43:00.000000"}, {"author": "623e79d48d8b9c0068b9f47f", "body": "Facter 4.x's domain and FQDN are incorrect on Windows 2016 DataCenter running on AWS:\n\nIn one AWS environment on Windows 2016 DataCenter:\n\nFacter logs the correct hostname and domain in the \"Managed to read\" debug line:\nFacter: Managed to read hostname: myhost and domain: mydomain.mytld\n\nBut the following are incorrect:\n\nFacter: fact \"networking.domain\" has resolved to: ec2.internal\nFacter: fact \"domain\" has resolved to: ec2.internal\nFacter: fact \"networking.fqdn\" has resolved to: myhost.ec2.internal\nFacter: fact \"fqdn\" has resolved to: myhost.ec2.internal\n\n--------------------\n\nIn another AWS environment on Windows 2016 DataCenter:\nIn this environment, too, Facter logs the correct hostname and domain in the \"Managed to read\" debug line:\nFacter: Managed to read hostname: myhost and domain: mydomain.mytld\n\nBut the following are incorrect:\nFacter: fact \"networking.domain\" has resolved to: mydomain1.mytld1 mysubdomain1.mydomain2.mytld2 mysubdomain2.mydomain1.mytld1\nFacter: fact \"domain\" has resolved to: mydomain1.mytld1 mysubdomain1.mydomain2.mytld2 mysubdomain2.mydomain1.mytld1\nFacter: fact \"networking.fqdn\" has resolved to: myhost.mydomain1.mytld1 mysubdomain1.mydomain2.mytld2 mysubdomain2.mydomain1.mytld1\nFacter: fact \"fqdn\" has resolved to: myhost.mydomain1.mytld1 mysubdomain1.mydomain2.mytld2 mysubdomain2.mydomain1.mytld1\n\n(Note that the output has multiple domain suffixes, separated by spaces)\n\nShould a separate ticket be logged for AWS?\n\n\u00a0", "created": "2021-09-10T15:22:00.000000"}, {"author": "623e79d48d8b9c0068b9f47f", "body": "Is there an ETA for fixing these Facter 4.x issues with discovering domain and FQDN on Azure and AWS?", "created": "2021-09-10T15:25:00.000000"}, {"author": "623e79d48d8b9c0068b9f47f", "body": "Hello, Is there any update about this ticket? It affects all Azure and AWS environments.", "created": "2021-09-15T12:22:00.000000"}, {"author": "70121:ede92dff-cc7b-4a0e-9ea1-e6d39be6ea56", "body": "Hi [~accountid:623e79d48d8b9c0068b9f47f], we're going to start looking over this.\n\nThis happening on both Azure and AWS might be linked to the fact that the Windows flavor is DataCenter, so there shouldn't be a separate ticket for that.", "created": "2021-09-17T05:32:00.000000"}, {"author": "70121:ede92dff-cc7b-4a0e-9ea1-e6d39be6ea56", "body": "[~accountid:623e79d48d8b9c0068b9f47f] it's likely that you are hitting the same issue fixed in https://puppet.atlassian.net/browse/FACT-2923.\n\nIs this error reproducible with the latest puppet-agent/facter?", "created": "2021-09-17T06:36:00.000000"}, {"author": "623e79d48d8b9c0068b9f47f", "body": "We are on 4.0.49 with Puppet agent 6.16.\n\nShould we try [https://rubygems.org/gems/facter/versions/4.2.4]\u00a0?", "created": "2021-09-17T11:37:00.000000"}, {"author": "70121:4596f954-1fdf-472f-a700-6b7c2ffbc525", "body": "I'm not sure that you can simply update the gem. Can you try puppet 6.21.1 or newer?", "created": "2021-09-17T12:03:00.000000"}, {"author": "623e79d48d8b9c0068b9f47f", "body": "We use open-source Puppet Agent 6.16.0 with Facter 4.0.49. In our setup, we can update just the Facter gem. If this issue is resolved in higher Facter 4.x versions (actually, looks like FACT-2923\u00a0was fixed in 4.0.50), we can try\u00a0[https://rubygems.org/gems/facter/versions/4.2.4]\u00a0. Please confirm.\u00a0", "created": "2021-09-17T12:13:00.000000"}, {"author": "70121:4596f954-1fdf-472f-a700-6b7c2ffbc525", "body": "Hi [~accountid:623e79d48d8b9c0068b9f47f],\n\nYou can try to manually update the facter gem, but this is not something that we tested or support.\nWe recommend you to upgrade to latest open-source puppet-agent version or at least 6.21.1.\n\nSince the problem is known and already addressed in newer versions, I will close this ticket.", "created": "2021-09-20T04:42:00.000000"}], "components": ["Facter 4"], "created": "2021-08-31T10:50:00.000000", "creator": "623e79d48d8b9c0068b9f47f", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@534eb48c"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "Method Found", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|o0awar:"}, {"fieldName": "[CHART] Date of First Response", "fieldType": "com.atlassian.jira.ext.charting:firstresponsedate", "value": "02/Sep/21"}, {"fieldName": "[CHART] Time in Status", "fieldType": "com.atlassian.jira.ext.charting:timeinstatus", "value": "1_*:*_2_*:*_1150495925_*|*_6_*:*_1_*:*_0_*|*_10004_*:*_1_*:*_3368_*|*_10005_*:*_2_*:*_555466254"}], "description": "Facter 4.x on MS Azure: wrong domain is used in FQDN\nWhen running Facter 4.0.49 on MicroSoft Azure, instead of using the actual DNS domain, the Azure's default DNS suffix: reddog.microsoft.com is being used:\nFacter: fact \"domain\" has resolved to: {color:#FF0000}reddog.microsoft.com{color}\nFacter: fact \"networking.fqdn\" has resolved to: myhost.{color:#FF0000}reddog.microsoft.com{color}\nFacter: fact \"fqdn\" has resolved to: myhost.reddog.microsoft.com\n\nThe actual DNS domain is: {color:#4c9aff}*mydomain.mytld*{color}\n\nThe DNS does not have myhost.reddog.microsoft.com, so any network request to the bad FQDN fails.\n\n\nWhereas Facter 3.x has the correct domain on the same Azure environment:\nFacter: fact \"domain\" has resolved to \"{color:#4c9aff}mydomain.mytld{color}\"\nFacter: fact \"fqdn\" has resolved to \"myhost.{color:#4c9aff}*mydomain.mytld*{color}\".", "epicLinkSummary": null, "estimate": "PT0S", "externalId": "60877", "fixedVersions": [], "id": "60877", "issueType": "Bug", "key": "FACT-3069", "labels": ["needs_repro"], "originalEstimate": "PT0S", "parent": null, "parentSummary": null, "priority": "Blocker", "projectDescription": "

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

", "projectKey": "FACT", "projectLead": "70121:199f31c7-67c7-42b0-b148-18ad3a391ab0", "projectName": "Facter (Archived)", "projectType": "software", "projectUrl": null, "reporter": "557058:be86c7d6-2807-42d3-9715-80da0cf607cd", "resolution": "Won't Fix", "resolutionDate": "2021-03-02T00:22:00.000000", "status": "Closed", "statusCategory": "Done", "statuscategorychangedate": "11/Mar/23 10:29 AM", "summary": "puppet facts diff shows inconsistent networking values on macOS", "timeSpent": "PT0S", "updated": "2021-03-02T00:22:00.000000", "votes": "0", "watchers": []}, {"affectedVersions": [], "assignee": "6007ea942a6b66006902c024", "attachments": [], "comments": [{"author": "557058:c241032a-c552-4408-9a96-dcd5a643ff69", "body": "I think this might be a bug related to switching to Facter 4. I'll ask around /cc [~accountid:5abd613dd4cf3c56be24b70d]", "created": "2021-02-17T11:21:00.000000"}, {"author": "557058:c241032a-c552-4408-9a96-dcd5a643ff69", "body": "To help verify if this is a Facter issue, would you mind running the following on your system, on both Puppet 6 and Puppet 7, and letting us know the output? It should be the same across versions, but if it isn't, that could be the issue here.\n\n{code}\nfacter hostname domain fqdn\npuppet config print certname\n{code}", "created": "2021-02-17T12:33:00.000000"}, {"author": "623e790aa9575800695c0976", "body": "Hi Maggie.\n\nHere is the information you asked :\n Puppet 6\n{code}root@puppetdev:~# facter hostname domain fqdn\ndomain => example.org\nfqdn => puppetdev.example.org\nhostname => puppetdev\nroot@puppetdev:~# puppet config print certname\npuppetdev.example.org\n{code}\n\u00a0\n Puppet 7\n{code}root@puppetdev:~# facter hostname domain fqdn\ndomain => example.org\nfqdn => puppetdev.example.org\nhostname => puppetdev\nroot@puppetdev:~# puppet config print certname\npuppetdev.example.org\n{code}\nUnfortunately, the output is the same.\n\nBut following your hint (Puppet unable to get the right FQDN of the host) and after stumbling on this ticket https://puppet.atlassian.net/browse/PUP-7667, I found a dirty workaround :\n{code}root@puppetdev:~# puppetserver ca list --all\nThe cadir is currently configured to be inside the /etc/puppetlabs/puppet/ssl directory. This config setting and the directory location will not be used in a future version of puppet. Please run the puppetserver ca tool to migrate out from the puppet confdir to the /etc/puppetlabs/puppetserver/ca directory. Use `puppetserver ca migrate --help` for more info.\nSigned Certificates:\n puppetagent1.example.org (SHA256) 7E:E6:DF:B0:83:B7:36:C2:F1:4E:D8:33:31:74:75:A4:EE:58:C9:0D:A2:78:AC:D9:D4:04:1D:8A:AA:00:9B:19\n puppetagent2.example.org (SHA256) 09:EB:01:B7:41:5F:6B:18:DC:25:B5:13:6A:F7:4B:34:66:E0:81:49:6F:25:9B:EC:5F:1B:09:21:EE:1E:27:F0\n puppetdev (SHA256) 74:44:78:C8:66:97:1E:38:E5:73:E0:47:02:38:21:CD:2C:EF:FB:C0:05:C1:D9:9C:55:2A:7F:9F:D9:0C:F8:3E\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev\"]\tauthorization extensions: [pp_cli_auth: true]\n puppetdev.example.org (SHA256) E4:6D:7F:84:71:D8:74:15:ED:1E:F7:79:D8:A5:A4:93:B6:A2:5A:52:1C:B6:08:34:D4:88:32:C2:99:CD:87:20\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev.example.org\"]\tauthorization extensions: [pp_cli_auth: true]\nroot@puppetdev:~# systemctl disable puppetserver.service \nSynchronizing state of puppetserver.service with SysV service script with /lib/systemd/systemd-sysv-install.\nExecuting: /lib/systemd/systemd-sysv-install disable puppetserver\nRemoved /etc/systemd/system/multi-user.target.wants/puppetserver.service.\nroot@puppetdev:~# puppet node clean puppetdev\nWarning: The cadir is currently configured to be inside the /etc/puppetlabs/puppet/ssl directory. This config setting and the directory location will not be used in a future version of puppet. Please run the puppetserver ca tool to migrate out from the puppet confdir to the /etc/puppetlabs/puppetserver/ca directory. Use `puppetserver ca migrate --help` for more info.\nNotice: Revoked certificate for puppetdev\nNotice: Cleaned files related to puppetdev\npuppetdev\nroot@puppetdev:~# systemctl stop puppetserver.service \nroot@puppetdev:~# rm /etc/puppetlabs/puppet/ssl/*/puppetdev.pem\nroot@puppetdev:~# cat /etc/hostname \npuppetdev\nroot@puppetdev:~# echo 'puppetdev.example.org' > /etc/hostname \nroot@puppetdev:~# cat /etc/hostname \npuppetdev.example.org\nroot@puppetdev:~# reboot\nroot@puppetdev:~# hostname\npuppetdev.example.org\nroot@puppetdev:~# hostname -f\npuppetdev.example.org\nroot@puppetdev:~# hostname -s\npuppetdev\nroot@puppetdev:~# cat /etc/hostname \npuppetdev.example.org\nroot@puppetdev:~# systemctl start puppetserver.service \nroot@puppetdev:~# puppetserver ca list --all\nThe cadir is currently configured to be inside the /etc/puppetlabs/puppet/ssl directory. This config setting and the directory location will not be used in a future version of puppet. Please run the puppetserver ca tool to migrate out from the puppet confdir to the /etc/puppetlabs/puppetserver/ca directory. Use `puppetserver ca migrate --help` for more info.\nSigned Certificates:\n puppetagent1.example.org (SHA256) 7E:E6:DF:B0:83:B7:36:C2:F1:4E:D8:33:31:74:75:A4:EE:58:C9:0D:A2:78:AC:D9:D4:04:1D:8A:AA:00:9B:19\n puppetagent2.example.org (SHA256) 09:EB:01:B7:41:5F:6B:18:DC:25:B5:13:6A:F7:4B:34:66:E0:81:49:6F:25:9B:EC:5F:1B:09:21:EE:1E:27:F0\n puppetdev.example.org (SHA256) E4:6D:7F:84:71:D8:74:15:ED:1E:F7:79:D8:A5:A4:93:B6:A2:5A:52:1C:B6:08:34:D4:88:32:C2:99:CD:87:20\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev.example.org\"]\tauthorization extensions: [pp_cli_auth: true]\n{code}\nIt is not clean since /etc/hostname must not contain the FQDN of the host. But I think that it shows that the problem is linked to the fact that Puppet 7 is unable the right FQDN of the host.\n\nHope it helps.", "created": "2021-02-17T14:23:00.000000"}, {"author": "5abd613dd4cf3c56be24b70d", "body": "Hi [~accountid:623e790aa9575800695c0976],\n\nWe were not able to reproduce this issue on Debian 10.8 using the versions of Puppet Agent and Server that you've mentioned.\n\nWould it be possible to get the output of the following on a Puppet 7 node that's experiencing this issue (before the\u00a0_/etc/hostname_ workaround):\n{code:java}\npuppetserver --version\n\npuppetserver irb\nrequire 'facter'\nFacter.value('fqdn')\nFacter.value('domain')\nFacter.value('hostname'){code}\nIt would be great if you could provide the content of _/etc/resolv.conf_\n\nand the output of _facter fqdn --debug_\n\n\u00a0\n\nThank you!", "created": "2021-02-18T08:02:00.000000"}, {"author": "623e790aa9575800695c0976", "body": "Hi Mihai Buzgau,\n\nHere is the informations you asked.\n\n{code}\nroot@puppetdev:~# puppetserver --version\npuppetserver version: 7.0.3\nroot@puppetdev:~# puppetserver irb\nirb(main):001:0> require 'facter'\n=> true\nirb(main):002:0> \nirb(main):003:0> Facter.value('fqdn')\n=> \"puppetdev\"\nirb(main):004:0> \nirb(main):005:0> Facter.value('domain')\n=> nil\nirb(main):006:0> \nirb(main):007:0> Facter.value('hostname')\n=> \"puppetdev\"\nirb(main):008:0> \nroot@puppetdev:~# cat /etc/resolv.conf \n# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)\n# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN\nnameserver 192.168.122.1\nroot@puppetdev:~# facter fqdn --debug\n[2021-02-18 18:18:57.154991 ] INFO Facter - executed with command line: fqdn --debug \n[2021-02-18 18:18:57.155190 ] DEBUG Facter - Facter version: 4.0.51 \n[2021-02-18 18:18:57.157252 ] DEBUG Facter::FactLoader - Loading internal facts \n[2021-02-18 18:18:57.157362 ] DEBUG Facter::FactLoader - Loading all internal facts \n[2021-02-18 18:18:57.157617 ] DEBUG Facter::FactLoader - Loading external facts \n[2021-02-18 18:18:57.157719 ] DEBUG Facter::FactLoader - Loading custom facts \n[2021-02-18 18:18:57.158789 ] DEBUG Facter::FactLoader - Loading external facts \n[2021-02-18 18:18:57.159081 ] DEBUG Facter::QueryParser - User query is: [\"fqdn\"] \n[2021-02-18 18:18:57.159189 ] DEBUG Facter::QueryParser - Query is fqdn \n[2021-02-18 18:18:57.159365 ] DEBUG Facter::QueryParser - Checking query tokens fqdn \n[2021-02-18 18:18:57.160694 ] DEBUG Facter::QueryParser - List of resolvable facts: [#] \n[2021-02-18 18:18:57.160943 ] DEBUG Facter::InternalFactManager - Resolving facts sequentially \n[2021-02-18 18:18:57.161291 ] DEBUG Facter::Resolvers::Hostname - Only managed to read hostname: puppetdev, no domain was found. \n[2021-02-18 18:18:57.161746 ] DEBUG Facter::Resolvers::Hostname - Managed to read hostname: puppetdev and domain: example.org \n[2021-02-18 18:18:57.161933 ] DEBUG Facter::FactManager - fact \"fqdn\" has resolved to: puppetdev.example.org \n[2021-02-18 18:18:57.162149 ] DEBUG Facter::LegacyFactFormatter - Formatting for single user query \npuppetdev.example.org\n{code}\n", "created": "2021-02-18T10:25:00.000000"}, {"author": "5abd613dd4cf3c56be24b70d", "body": "Thank you\u00a0[~accountid:623e790aa9575800695c0976]\u00a0this is really useful.\n\nas [~accountid:557058:c241032a-c552-4408-9a96-dcd5a643ff69]\u00a0mentioned earlier. this seems to be a Facter issue so I'm moving the ticket to the FACT project.", "created": "2021-02-18T10:37:00.000000"}, {"author": "557058:91233464-4152-4228-81dd-172d43a52a03", "body": "Merged to main in [https://github.com/puppetlabs/facter/commit/b56cb31644a17153b13d15b4904d1487630a110b,]\u00a0passed CI in facter#3390419c5", "created": "2021-03-09T14:45:00.000000"}, {"author": "6007ea942a6b66006902c024", "body": "Hi [~accountid:623e790aa9575800695c0976],\n\n\u00a0\n\nUntil the next release, it would be helpful if you can try [http://nightlies.puppet.com/apt/pool/buster/puppet7-nightly/p/puppet-agent/puppet-agent_7.4.1.90.g54cd2d413-1buster_amd64.deb]\u00a0to fully validate the fix.\n\n\u00a0", "created": "2021-03-10T04:28:00.000000"}, {"author": "6007ea942a6b66006902c024", "body": "!https://user-images.githubusercontent.com/49147761/109532395-c1955c00-7ac1-11eb-9b24-e14f528306f4.png!", "created": "2021-03-10T04:30:00.000000"}, {"author": "623e790aa9575800695c0976", "body": "Hi [~accountid:6007ea942a6b66006902c024] ,\n\nI just tried the puppet-agent nightly package on the same platform.\n\nThe problem is still there. I don't see any differences :(\n{code}root@puppetdev:~# puppetserver ca list --all\nThe cadir is currently configured to be inside the /etc/puppetlabs/puppet/ssl directory. This config setting and the directory location will not be used in a future version of puppet. Please run the puppetserver ca tool to migrate out from the puppet confdir to the /etc/puppetlabs/puppetserver/ca directory. Use `puppetserver ca migrate --help` for more info.\nSigned Certificates:\n puppetagent1.example.org (SHA256) 7E:E6:DF:B0:83:B7:36:C2:F1:4E:D8:33:31:74:75:A4:EE:58:C9:0D:A2:78:AC:D9:D4:04:1D:8A:AA:00:9B:19\n puppetagent2.example.org (SHA256) 09:EB:01:B7:41:5F:6B:18:DC:25:B5:13:6A:F7:4B:34:66:E0:81:49:6F:25:9B:EC:5F:1B:09:21:EE:1E:27:F0\n puppetdev (SHA256) 74:44:78:C8:66:97:1E:38:E5:73:E0:47:02:38:21:CD:2C:EF:FB:C0:05:C1:D9:9C:55:2A:7F:9F:D9:0C:F8:3E\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev\"]\tauthorization extensions: [pp_cli_auth: true]\n puppetdev.example.org (SHA256) E4:6D:7F:84:71:D8:74:15:ED:1E:F7:79:D8:A5:A4:93:B6:A2:5A:52:1C:B6:08:34:D4:88:32:C2:99:CD:87:20\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev.example.org\"]\tauthorization extensions: [pp_cli_auth: true]\nroot@puppetdev:~# puppet node clean puppetdev\nWarning: The cadir is currently configured to be inside the /etc/puppetlabs/puppet/ssl directory. This config setting and the directory location will not be used in a future version of puppet. Please run the puppetserver ca tool to migrate out from the puppet confdir to the /etc/puppetlabs/puppetserver/ca directory. Use `puppetserver ca migrate --help` for more info.\nNotice: Revoked certificate for puppetdev\nNotice: Cleaned files related to puppetdev\npuppetdev\nroot@puppetdev:~# systemctl stop puppetserver.service \nroot@puppetdev:~# rm /etc/puppetlabs/puppet/ssl/*/puppetdev.pem\nroot@puppetdev:~# wget http://nightlies.puppet.com/apt/pool/buster/puppet7-nightly/p/puppet-agent/puppet-agent_7.4.1.90.g54cd2d413-1buster_amd64.deb\nroot@puppetdev:~# apt install ./puppet-agent_7.4.1.90.g54cd2d413-1buster_amd64.deb \nroot@puppetdev:~# puppet --version\n7.5.0\nroot@puppetdev:~# facter --version\n4.0.52\nroot@puppetdev:~# puppetserver --version\npuppetserver version: 7.0.3\nroot@puppetdev:~# systemctl start puppetserver.service \nroot@puppetdev:~# ls -1 /etc/puppetlabs/puppet/ssl/*/puppetdev*.pem\n/etc/puppetlabs/puppet/ssl/certs/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/certs/puppetdev.pem\n/etc/puppetlabs/puppet/ssl/private_keys/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/private_keys/puppetdev.pem\n/etc/puppetlabs/puppet/ssl/public_keys/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/public_keys/puppetdev.pem\nroot@puppetdev:~# puppetserver ca list --all\nThe cadir is currently configured to be inside the /etc/puppetlabs/puppet/ssl directory. This config setting and the directory location will not be used in a future version of puppet. Please run the puppetserver ca tool to migrate out from the puppet confdir to the /etc/puppetlabs/puppetserver/ca directory. Use `puppetserver ca migrate --help` for more info.\nSigned Certificates:\n puppetagent1.example.org (SHA256) 7E:E6:DF:B0:83:B7:36:C2:F1:4E:D8:33:31:74:75:A4:EE:58:C9:0D:A2:78:AC:D9:D4:04:1D:8A:AA:00:9B:19\n puppetagent2.example.org (SHA256) 09:EB:01:B7:41:5F:6B:18:DC:25:B5:13:6A:F7:4B:34:66:E0:81:49:6F:25:9B:EC:5F:1B:09:21:EE:1E:27:F0\n puppetdev (SHA256) 9D:39:E0:B3:A3:D4:A6:92:24:3B:A5:A8:AA:5F:96:87:76:8F:8D:1A:11:12:03:5E:B7:D3:89:0C:AC:7C:21:BD\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev\"]\tauthorization extensions: [pp_cli_auth: true]\n puppetdev.example.org (SHA256) E4:6D:7F:84:71:D8:74:15:ED:1E:F7:79:D8:A5:A4:93:B6:A2:5A:52:1C:B6:08:34:D4:88:32:C2:99:CD:87:20\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev.example.org\"]\tauthorization extensions: [pp_cli_auth: true]\nroot@puppetdev:~# puppetserver irb\nirb(main):001:0> require 'facter'\n=> true\nirb(main):002:0> Facter.value('fqdn')\n=> \"puppetdev\"\nirb(main):003:0> Facter.value('domain')\n=> nil\nirb(main):004:0> Facter.value('hostname')\n=> \"puppetdev\"\nroot@puppetdev:~# facter fqdn --debug\n[2021-03-10 18:02:57.087296 ] INFO Facter - executed with command line: fqdn --debug \n[2021-03-10 18:02:57.087461 ] DEBUG Facter - Facter version: 4.0.52 \n[2021-03-10 18:02:57.089252 ] DEBUG Facter::FactLoader - Loading internal facts \n[2021-03-10 18:02:57.089342 ] DEBUG Facter::FactLoader - Loading all internal facts \n[2021-03-10 18:02:57.089537 ] DEBUG Facter::FactLoader - Loading external facts \n[2021-03-10 18:02:57.089622 ] DEBUG Facter::FactLoader - Loading custom facts \n[2021-03-10 18:02:57.090527 ] DEBUG Facter::FactLoader - Loading external facts \n[2021-03-10 18:02:57.090762 ] DEBUG Facter::QueryParser - User query is: [\"fqdn\"] \n[2021-03-10 18:02:57.090853 ] DEBUG Facter::QueryParser - Query is fqdn \n[2021-03-10 18:02:57.090974 ] DEBUG Facter::QueryParser - Checking query tokens fqdn \n[2021-03-10 18:02:57.092078 ] DEBUG Facter::QueryParser - List of resolvable facts: [#] \n[2021-03-10 18:02:57.092284 ] DEBUG Facter::InternalFactManager - Resolving facts sequentially \n[2021-03-10 18:02:57.092564 ] DEBUG Facter::Resolvers::Hostname - Only managed to read hostname: puppetdev, no domain was found. \n[2021-03-10 18:02:57.093014 ] DEBUG Facter::Resolvers::Hostname - Managed to read hostname: puppetdev and domain: example.org \n[2021-03-10 18:02:57.093239 ] DEBUG Facter::FactManager - fact \"fqdn\" has resolved to: puppetdev.example.org \n[2021-03-10 18:02:57.093478 ] DEBUG Facter::LegacyFactFormatter - Formatting for single user query \npuppetdev.example.org\n{code}", "created": "2021-03-10T10:37:00.000000"}, {"author": "557058:91233464-4152-4228-81dd-172d43a52a03", "body": "-Thanks for testing that out [~accountid:623e790aa9575800695c0976]! Unfortunately CI did not finish last night so the nightly build you tried doesn't have [~accountid:6007ea942a6b66006902c024]'s change:-\n\n-Could you retry the test later today/tomorrow using version 7.4.1.102.g1725eb470 of puppet-agent (the builds aren't there yet, but should be soon)-\n\nSorry nevermind, I misread the facter git history. It's not working yet.", "created": "2021-03-10T10:58:00.000000"}, {"author": "6007ea942a6b66006902c024", "body": "Hi [~accountid:623e790aa9575800695c0976],\n\nCould you please try :\u00a0\n{code:java}\npuppetserver irb\nrequire 'facter'\nFacter.version{code}\nAnd post the output? It would be very helpful.", "created": "2021-03-10T11:22:00.000000"}, {"author": "623e790aa9575800695c0976", "body": "Hi [~accountid:6007ea942a6b66006902c024],\n\nHere the output you ask (with puppet-agent_7.4.1.90.g54cd2d413-1buster_amd64.deb installed) :\n\n {code}\nroot@puppetdev:~# puppet --version\n7.5.0\nroot@puppetdev:~# puppetserver --version\npuppetserver version: 7.0.3\nroot@puppetdev:~# facter --version\n4.0.52\nroot@puppetdev:~# puppetserver irb\nirb(main):001:0> require 'facter'\n=> true\nirb(main):002:0> Facter.version\n=> \"4.0.52\"\n {code}\n\nIf you need the output with another package version, feel free to ask.\n", "created": "2021-03-10T12:06:00.000000"}, {"author": "557058:91233464-4152-4228-81dd-172d43a52a03", "body": "Merged to main in https://github.com/puppetlabs/facter/commit/b56cb31644a17153b13d15b4904d1487630a110b and https://github.com/puppetlabs/facter/commit/06069eb4a26e387d96e8bea0671e9891ccadd49f", "created": "2021-03-11T11:45:00.000000"}, {"author": "5abd613dd4cf3c56be24b70d", "body": "Hi [~accountid:623e790aa9575800695c0976],\u00a0\n\nWe've just published a new nightly build.\n\nWould you be so kind to try it out and let us know if this fixes your issue?\n\nYou can download the build from here:\u00a0http://nightlies.puppet.com/apt/pool/buster/puppet7-nightly/p/puppet-agent/puppet-agent-dbgsym_7.4.1.109.g573c9c580-1buster_amd64.deb\n\nThank you!", "created": "2021-03-11T13:05:00.000000"}, {"author": "623e790aa9575800695c0976", "body": "Hi [~accountid:5abd613dd4cf3c56be24b70d] ,\n\nI used this package (the one without the debug symbols) :\u00a0[http://nightlies.puppet.com/apt/pool/buster/puppet7-nightly/p/puppet-agent/puppet-agent_7.4.1.109.g573c9c580-1buster_amd64.deb]\n\nAnd it is a success ! :)\n\nGreat job ! Thanks a lot.\n\nHere is the full log.\n{code}root@puppetdev:~# ls -1 /etc/puppetlabs/puppet/ssl/*/puppetdev*.pem\n/etc/puppetlabs/puppet/ssl/certs/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/certs/puppetdev.pem\n/etc/puppetlabs/puppet/ssl/private_keys/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/private_keys/puppetdev.pem\n/etc/puppetlabs/puppet/ssl/public_keys/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/public_keys/puppetdev.pem\nroot@puppetdev:~# puppetserver ca list --all\nThe cadir is currently configured to be inside the /etc/puppetlabs/puppet/ssl directory. This config setting and the directory location will not be used in a future version of puppet. Please run the puppetserver ca tool to migrate out from the puppet confdir to the /etc/puppetlabs/puppetserver/ca directory. Use `puppetserver ca migrate --help` for more info.\nSigned Certificates:\n puppetagent1.example.org (SHA256) 7E:E6:DF:B0:83:B7:36:C2:F1:4E:D8:33:31:74:75:A4:EE:58:C9:0D:A2:78:AC:D9:D4:04:1D:8A:AA:00:9B:19\n puppetagent2.example.org (SHA256) 09:EB:01:B7:41:5F:6B:18:DC:25:B5:13:6A:F7:4B:34:66:E0:81:49:6F:25:9B:EC:5F:1B:09:21:EE:1E:27:F0\n puppetdev (SHA256) 9D:39:E0:B3:A3:D4:A6:92:24:3B:A5:A8:AA:5F:96:87:76:8F:8D:1A:11:12:03:5E:B7:D3:89:0C:AC:7C:21:BD\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev\"]\tauthorization extensions: [pp_cli_auth: true]\n puppetdev.example.org (SHA256) E4:6D:7F:84:71:D8:74:15:ED:1E:F7:79:D8:A5:A4:93:B6:A2:5A:52:1C:B6:08:34:D4:88:32:C2:99:CD:87:20\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev.example.org\"]\tauthorization extensions: [pp_cli_auth: true]\nroot@puppetdev:~# puppet node clean puppetdev\nWarning: The cadir is currently configured to be inside the /etc/puppetlabs/puppet/ssl directory. This config setting and the directory location will not be used in a future version of puppet. Please run the puppetserver ca tool to migrate out from the puppet confdir to the /etc/puppetlabs/puppetserver/ca directory. Use `puppetserver ca migrate --help` for more info.\nNotice: Revoked certificate for puppetdev\nNotice: Cleaned files related to puppetdev\npuppetdev\nroot@puppetdev:~# systemctl stop puppetserver.service \nroot@puppetdev:~# rm /etc/puppetlabs/puppet/ssl/*/puppetdev.pem\nroot@puppetdev:~# wget http://nightlies.puppet.com/apt/pool/buster/puppet7-nightly/p/puppet-agent/puppet-agent_7.4.1.109.g573c9c580-1buster_amd64.deb\nroot@puppetdev:~# apt install ./puppet-agent_7.4.1.109.g573c9c580-1buster_amd64.deb\n7.5.0\nroot@puppetdev:~# facter --version\n4.0.52\nroot@puppetdev:~# puppetserver --version\npuppetserver version: 7.0.3\nroot@puppetdev:~# systemctl start puppetserver.service \nroot@puppetdev:~# ls -1 /etc/puppetlabs/puppet/ssl/*/puppetdev*.pem\n/etc/puppetlabs/puppet/ssl/certs/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/private_keys/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/public_keys/puppetdev.example.org.pem\nroot@puppetdev:~# puppetserver ca list --all\nThe cadir is currently configured to be inside the /etc/puppetlabs/puppet/ssl directory. This config setting and the directory location will not be used in a future version of puppet. Please run the puppetserver ca tool to migrate out from the puppet confdir to the /etc/puppetlabs/puppetserver/ca directory. Use `puppetserver ca migrate --help` for more info.\nSigned Certificates:\n puppetagent1.example.org (SHA256) 7E:E6:DF:B0:83:B7:36:C2:F1:4E:D8:33:31:74:75:A4:EE:58:C9:0D:A2:78:AC:D9:D4:04:1D:8A:AA:00:9B:19\n puppetagent2.example.org (SHA256) 09:EB:01:B7:41:5F:6B:18:DC:25:B5:13:6A:F7:4B:34:66:E0:81:49:6F:25:9B:EC:5F:1B:09:21:EE:1E:27:F0\n puppetdev.example.org (SHA256) E4:6D:7F:84:71:D8:74:15:ED:1E:F7:79:D8:A5:A4:93:B6:A2:5A:52:1C:B6:08:34:D4:88:32:C2:99:CD:87:20\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev.example.org\"]\tauthorization extensions: [pp_cli_auth: true]\nroot@puppetdev:~# puppetserver irb\nirb(main):001:0> require 'facter'\n=> true\nirb(main):002:0> Facter.value('fqdn')\n=> \"puppetdev.example.org\"\nirb(main):003:0> Facter.value('domain')\n=> \"example.org\"\nirb(main):004:0> Facter.value('hostname')\n=> \"puppetdev\"\nirb(main):005:0> \nroot@puppetdev:~# facter fqdn --debug\n[2021-03-11 21:35:51.172953 ] INFO Facter - executed with command line: fqdn --debug \n[2021-03-11 21:35:51.173002 ] DEBUG Facter - Facter version: 4.0.52 \n[2021-03-11 21:35:51.174650 ] DEBUG Facter::FactLoader - Loading internal facts \n[2021-03-11 21:35:51.174679 ] DEBUG Facter::FactLoader - Loading all internal facts \n[2021-03-11 21:35:51.174776 ] DEBUG Facter::FactLoader - Loading external facts \n[2021-03-11 21:35:51.174797 ] DEBUG Facter::FactLoader - Loading custom facts \n[2021-03-11 21:35:51.175626 ] DEBUG Facter::FactLoader - Loading external facts \n[2021-03-11 21:35:51.175765 ] DEBUG Facter::QueryParser - User query is: [\"fqdn\"] \n[2021-03-11 21:35:51.175815 ] DEBUG Facter::QueryParser - Query is fqdn \n[2021-03-11 21:35:51.175842 ] DEBUG Facter::QueryParser - Checking query tokens fqdn \n[2021-03-11 21:35:51.176940 ] DEBUG Facter::QueryParser - List of resolvable facts: [#] \n[2021-03-11 21:35:51.177058 ] DEBUG Facter::InternalFactManager - Resolving facts sequentially \n[2021-03-11 21:35:51.190785 ] DEBUG Facter::Resolvers::Linux::Hostname - Tried to retrieve hostname and got: puppetdev \n[2021-03-11 21:35:51.190836 ] DEBUG Facter::Resolvers::Linux::Hostname - Only managed to read hostname: puppetdev, no domain was found. \n[2021-03-11 21:35:51.191206 ] DEBUG Facter::Resolvers::Linux::Hostname - Managed to read hostname: puppetdev and domain: example.org \n[2021-03-11 21:35:51.191279 ] DEBUG Facter::FactManager - fact \"fqdn\" has resolved to: puppetdev.example.org \n[2021-03-11 21:35:51.191425 ] DEBUG Facter::LegacyFactFormatter - Formatting for single user query \npuppetdev.example.org\n{code}", "created": "2021-03-11T13:44:00.000000"}, {"author": "557058:91233464-4152-4228-81dd-172d43a52a03", "body": "Passed CI in 06069eb4a", "created": "2021-03-11T13:49:00.000000"}, {"author": "623e790aa9575800695c0976", "body": "Hi [~accountid:63d40628f6e1b543161789a7] ,\n\nI made a test on another platform (not a test one but a production one) where the problem was present too.\n\nAnd I can confirm it is now fixed.\n\nThanks !", "created": "2021-03-13T00:43:00.000000"}, {"author": "557058:ad82b2fe-94cd-4b81-bed7-c8cbe892ae3e", "body": "Hi,\n I'm having som issues with my unit tests in a module with custom types that I think could be related to this...\n Since 16.03.2021 at 00:01:40 my rspec unit tests with puppet6 started failing like this\n{noformat}An error occurred while loading ./spec/unit/puppet/provider/am_agent_j2ee/ruby_spec.rb.\n Failure/Error: defaultto \"amAgent_#{Facter.value('fqdn').gsub('.', '_')}_80.log\"\n Puppet::Error:\n Could not autoload puppet/type/am_agent_j2ee: undefined method `gsub' for nil:NilClass\n{noformat}\nIt seems like Facter 4.0.52 does not report the fqdn fact and I wonder if [https://github.com/puppetlabs/facter/pull/2315]\u00a0could have caused this?\n\nI'm running rspec tests on CentOS 7.9 and ruby 2.5.3", "created": "2021-03-17T05:57:00.000000"}, {"author": "557058:91233464-4152-4228-81dd-172d43a52a03", "body": "Hi [~accountid:557058:ad82b2fe-94cd-4b81-bed7-c8cbe892ae3e], can you provide a way to reproduce and the output of {{bundle exec gem list}} and {{bundle exec gem env}}? I'm guessing there's some interaction between rspec-puppet and puppet that is changed due to the ffi change.\n\nAlso one thing, passing an interpolated string to {{defaultto}} means the value will be looked up as soon as the provider ruby code is loaded. You may instead want to pass a block to {{defaulttto}} so that the resolution is deferred until the resource is applied (and likely after rspec-puppet has stubbed the value). So try changing the provider to:\n\n{code:ruby}\ndefaultto { \"amAgent_#{Facter.value('fqdn').gsub('.', '_')}_80.log\" }\n{code}\n\nSee https://github.com/puppetlabs/puppet-specifications/blob/master/language/resource_types.md#defaultto for more info about the difference", "created": "2021-03-17T16:23:00.000000"}, {"author": "557058:b2fe0420-6f4f-4922-9c44-0119b369c167", "body": "[~accountid:63d40628f6e1b543161789a7] I'm also seeing odd behaviour in Facter 4.0.52. (4.0.51 works just fine)\u00a0 I'm missing the fqdn and hostname legacy facts.\n\n```\nroot@b9b108b35f62:/workspaces/puppet-editor-services# bundle exec facter --show-legacy\narchitecture => amd64\nblockdevice_sda_model => Virtual Disk\nblockdevice_sda_size => 274877906944\nblockdevice_sda_vendor => Msft\nblockdevice_sdb_model => Virtual Disk\nblockdevice_sdb_size => 274877906944\nblockdevice_sdb_vendor => Msft\n...\nfacterversion => 4.0.52\nfilesystems => btrfs,ext2,ext3,ext4,iso9660,msdos,squashfs,vfat,xfs\nfips_enabled => false\ngid => root\nhardwareisa => unknown\nhardwaremodel => x86_64\nhypervisors => {\n docker => {\n id => \"b9b108b35f6204f72f262d70a6e1967a89d5fd8802de0618d737161581433939\"\n }\n}\nid => root\nidentity => {\n gid => 0,\n group => \"root\",\n privileged => true,\n uid => 0,\n user => \"root\"\n}\ninterfaces => eth0,lo,sit0\nipaddress => 172.17.0.2\n...\n```\n\nThis is running on Debian 10.7.\u00a0 Running Puppet and Facter as a gem. Puppet agent NOT installed.\n\n* First seen as failing integration tests for [https://github.com/puppetlabs/puppet-editor-services/runs/2228454033]\n* Found that the output from Facter was missing hostname (which is what I'm testing for)\n\nReproduction steps\n* Requires Docker, VS Code and the VS Code Remote Containers extension\n* Clone\u00a0 [https://github.com/puppetlabs/puppet-editor-services]\n* Start VS Code and \"Reopen in Container\".\u00a0 This starts the editor inside inside a docker container.\n\u00a0 You could also shortcut this by running the Dockerfile directly ([https://github.com/puppetlabs/puppet-editor-services/blob/main/.devcontainer/Dockerfile)]\n\n* bundle install\n* bundle exec facter --show-legacy", "created": "2021-03-30T20:30:00.000000"}, {"author": "557058:b2fe0420-6f4f-4922-9c44-0119b369c167", "body": "Also missing certname \ud83d\ude2d\n\n```\nroot@b9b108b35f62:/workspaces/puppet-editor-services# bundle exec facter certname hostname fqdn\ncertname =>\nfqdn =>\nhostname =>\nroot@b9b108b35f62:/workspaces/puppet-editor-services#\n```", "created": "2021-03-30T20:37:00.000000"}, {"author": "557058:b2fe0420-6f4f-4922-9c44-0119b369c167", "body": "Okay ... certname is a red herring.\u00a0 This is facter gem, so there's no certificate to get the name of\n\n\u00a0\n\nBut ...\n\n\u00a0\n\n```\nroot@b9b108b35f62:/workspaces/puppet-editor-services# bundle exec facter certname hostname fqdn --debug\n[2021-03-31 02:38:47.739512 ] INFO Facter - executed with command line: certname hostname fqdn --debug\n[2021-03-31 02:38:47.739580 ] DEBUG Facter - Facter version: 4.0.52\n[2021-03-31 02:38:47.741917 ] DEBUG Facter::FactLoader - Loading internal facts\n[2021-03-31 02:38:47.742002 ] DEBUG Facter::FactLoader - Loading all internal facts\n[2021-03-31 02:38:47.742141 ] DEBUG Facter::FactLoader - Loading external facts\n[2021-03-31 02:38:47.742198 ] DEBUG Facter::FactLoader - Loading custom facts\n[2021-03-31 02:38:47.744542 ] DEBUG Facter::FactLoader - Loading external facts\n[2021-03-31 02:38:47.744661 ] DEBUG Facter::QueryParser - User query is: [\"certname\", \"hostname\", \"fqdn\"]\n[2021-03-31 02:38:47.744700 ] DEBUG Facter::QueryParser - Query is certname\n[2021-03-31 02:38:47.744724 ] DEBUG Facter::QueryParser - Checking query tokens certname\n[2021-03-31 02:38:47.745685 ] DEBUG Facter::QueryParser - List of resolvable facts: []\n[2021-03-31 02:38:47.745742 ] DEBUG Facter::QueryParser - Query is hostname\n[2021-03-31 02:38:47.745767 ] DEBUG Facter::QueryParser - Checking query tokens hostname\n[2021-03-31 02:38:47.746930 ] DEBUG Facter::QueryParser - List of resolvable facts: [#]\n[2021-03-31 02:38:47.746985 ] DEBUG Facter::QueryParser - Query is fqdn\n[2021-03-31 02:38:47.747012 ] DEBUG Facter::QueryParser - Checking query tokens fqdn\n[2021-03-31 02:38:47.748081 ] DEBUG Facter::QueryParser - List of resolvable facts: [#]\n[2021-03-31 02:38:47.748173 ] DEBUG Facter::InternalFactManager - Resolving facts sequentially\n[2021-03-31 02:38:47.749962 ] DEBUG Facter::Resolvers::Linux::Hostname - resolving fact hostname, but cannot load such file -- ffi\n[2021-03-31 02:38:47.751378 ] DEBUG Facter::Resolvers::Linux::Hostname - resolving fact fqdn, but cannot load such file -- ffi\n[2021-03-31 02:38:47.751526 ] DEBUG Facter::LegacyFactFormatter - Formatting for multiple user queries\n[2021-03-31 02:38:47.751608 ] DEBUG Facter::LegacyFactFormatter - Converting hash to pretty json\n[2021-03-31 02:38:47.751671 ] DEBUG Facter::LegacyFactFormatter - Change key value delimiter from : to =>\n[2021-03-31 02:38:47.751718 ] DEBUG Facter::LegacyFactFormatter - Remove quotes from parent nodes\n[2021-03-31 02:38:47.751820 ] DEBUG Facter::LegacyFactFormatter - Remove double backslashes from paths\n[2021-03-31 02:38:47.751897 ] DEBUG Facter::LegacyFactFormatter - Removing enclosing accolades\n[2021-03-31 02:38:47.751954 ] DEBUG Facter::LegacyFactFormatter - Remove empty lines\n[2021-03-31 02:38:47.752012 ] DEBUG Facter::LegacyFactFormatter - Fix indentation after removing enclosed accolades\n[2021-03-31 02:38:47.752064 ] DEBUG Facter::LegacyFactFormatter - remove comas from query results\n[2021-03-31 02:38:47.752115 ] DEBUG Facter::LegacyFactFormatter - Remove unnecessary comma and quotation marks on root facts\n[2021-03-31 02:38:47.752192 ] DEBUG Facter::LegacyFactFormatter - Convert newline characters to actual newlines\n[2021-03-31 02:38:47.752253 ] DEBUG Facter::LegacyFactFormatter - Remove quotes from value if value is a string\ncertname =>\nfqdn =>\nhostname =>\nroot@b9b108b35f62:/workspaces/puppet-editor-services# bundle exec facter certname hostname fqdn --debug\n```\n\nIt appears I don't have ffi available...\n\nBut Facter has no dependency on FFI so...... how is this supposed to work?", "created": "2021-03-30T20:42:00.000000"}, {"author": "557058:b2fe0420-6f4f-4922-9c44-0119b369c167", "body": "Ahh ok... works on Windows due to Puppet Gem bringing in FFI.... but this is on Debian.", "created": "2021-03-30T20:49:00.000000"}], "components": [], "created": "2021-02-14T06:38:00.000000", "creator": "623e790aa9575800695c0976", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@47fe834a"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "Method Found", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|o06lp4:"}, {"fieldName": "Release Notes", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Bug Fix"}, {"fieldName": "Release Notes Summary", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:textarea", "value": "Description of the problem: Facter fails to retrieve domain using jruby because the Socket.getaddrinfo call fails.\nDescription of the fix: On linux if any of the Socket method calls fail, try to retrieve information using FFI methods (as described in the diagram below). "}, {"fieldName": "Story Points", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:float", "value": "3.0"}, {"fieldName": "[CHART] Date of First Response", "fieldType": "com.atlassian.jira.ext.charting:firstresponsedate", "value": "17/Feb/21"}, {"fieldName": "[CHART] Time in Status", "fieldType": "com.atlassian.jira.ext.charting:timeinstatus", "value": "10008_*:*_2_*:*_445215535_*|*_1_*:*_1_*:*_276172547_*|*_10007_*:*_1_*:*_88306276_*|*_3_*:*_1_*:*_81789591_*|*_10009_*:*_2_*:*_256847161_*|*_5_*:*_2_*:*_24192023_*|*_10005_*:*_1_*:*_1013302845"}], "description": "*Puppet Version: 7.4.0*\n *Puppet Server Version: 7.0.3*\n *OS Name/Version: Debian Buster 10.8*\n\nStarting with a Puppet 6 platform installed on Debian Buster 10.8 from the officials Puppetlabs packages (using [https://apt.puppetlabs.com/).]\n\nHere is how I upgrade to Puppet 7 (Take a close look to the output of 'puppetserver ca list --all' before the upgrade and after).\n{code}\nroot@puppetdev:~# cat /etc/puppetlabs/puppet/puppet.conf \n# This file can be used to override the default puppet settings.\n# See the following links for more details on what settings are available:\n# - https://puppet.com/docs/puppet/latest/config_important_settings.html\n# - https://puppet.com/docs/puppet/latest/config_about_settings.html\n# - https://puppet.com/docs/puppet/latest/config_file_main.html\n# - https://puppet.com/docs/puppet/latest/configuration.html\n[server]\nvardir = /opt/puppetlabs/server/data/puppetserver\nlogdir = /var/log/puppetlabs/puppetserver\nrundir = /var/run/puppetlabs/puppetserver\npidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid\ncodedir = /srv/puppet/code\nstoreconfigs=true\nstoreconfigs_backend=puppetdb\nreports=store,puppetdb\ndns_alt_names=puppetdev.example.org,puppetdev\n[main]\nstrict_variables=true\n[agent]\nenvironment=development\nserver=puppetdev.example.org\nroot@puppetdev:~# hostname\npuppetdev\nroot@puppetdev:~# hostname -f\npuppetdev.example.org\nroot@puppetdev:~# puppetserver ca list --all\nSigned Certificates:\n puppetagent1.example.org (SHA256) 7E:E6:DF:B0:83:B7:36:C2:F1:4E:D8:33:31:74:75:A4:EE:58:C9:0D:A2:78:AC:D9:D4:04:1D:8A:AA:00:9B:19\n puppetagent2.example.org (SHA256) 09:EB:01:B7:41:5F:6B:18:DC:25:B5:13:6A:F7:4B:34:66:E0:81:49:6F:25:9B:EC:5F:1B:09:21:EE:1E:27:F0\n puppetdev.example.org (SHA256) E4:6D:7F:84:71:D8:74:15:ED:1E:F7:79:D8:A5:A4:93:B6:A2:5A:52:1C:B6:08:34:D4:88:32:C2:99:CD:87:20\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev.example.org\"]\tauthorization extensions: [pp_cli_auth: true]\nroot@puppetdev:~# ls -1 /etc/puppetlabs/puppet/ssl/*/puppetdev*.pem\n/etc/puppetlabs/puppet/ssl/certs/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/private_keys/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/public_keys/puppetdev.example.org.pem\nroot@puppetdev:~# puppet --version\n6.21.0\nroot@puppetdev:~# wget https://apt.puppetlabs.com/puppet7-release-buster.deb\nroot@puppetdev:~# apt install ./puppet7-release-buster.deb \nroot@puppetdev:~# apt update;apt full-upgraderoot@puppetdev:~# puppet --version\n7.4.0\nroot@puppetdev:~# puppetserver ca list --all\nThe cadir is currently configured to be inside the /etc/puppetlabs/puppet/ssl directory. This config setting and the directory location will not be used in a future version of puppet. Please run the puppetserver ca tool to migrate out from the puppet confdir to the /etc/puppetlabs/puppetserver/ca directory. Use `puppetserver ca migrate --help` for more info.\nSigned Certificates:\n puppetagent1.example.org (SHA256) 7E:E6:DF:B0:83:B7:36:C2:F1:4E:D8:33:31:74:75:A4:EE:58:C9:0D:A2:78:AC:D9:D4:04:1D:8A:AA:00:9B:19\n puppetagent2.example.org (SHA256) 09:EB:01:B7:41:5F:6B:18:DC:25:B5:13:6A:F7:4B:34:66:E0:81:49:6F:25:9B:EC:5F:1B:09:21:EE:1E:27:F0\n puppetdev (SHA256) 46:3C:3C:0D:CD:5A:36:81:38:97:17:E9:58:AF:74:B7:94:20:A4:F2:F3:8B:55:87:64:B0:12:28:3D:D1:C5:32\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev\"]\tauthorization extensions: [pp_cli_auth: true]\n puppetdev.example.org (SHA256) E4:6D:7F:84:71:D8:74:15:ED:1E:F7:79:D8:A5:A4:93:B6:A2:5A:52:1C:B6:08:34:D4:88:32:C2:99:CD:87:20\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev.example.org\"]\tauthorization extensions: [pp_cli_auth: true]\nroot@puppetdev:~# ls -1 /etc/puppetlabs/puppet/ssl/*/puppetdev*.pem\n/etc/puppetlabs/puppet/ssl/certs/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/certs/puppetdev.pem\n/etc/puppetlabs/puppet/ssl/private_keys/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/private_keys/puppetdev.pem\n/etc/puppetlabs/puppet/ssl/public_keys/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/public_keys/puppetdev.pem\n{code}\n\u00a0\n\n*Desired Behavior:*\n After the upgrade to Puppet 7, the command 'puppetserver ca list --all' output should be identical to the output before the upgrade.\n\n*Actual Behavior:*\n After the upgrade to Puppet 7, the command 'puppetserver ca list --all' output now shows a 4th node with certname 'puppetdev'.\n\nIf you remove this certificate, it is recreated when Puppet Server starts :\n{code}\nroot@puppetdev:~# puppet node clean puppetdev\nNotice: Revoked certificate for puppetdev\nNotice: Cleaned files related to puppetdev\npuppetdev\nroot@puppetdev:~# systemctl stop puppetserver.service \nroot@puppetdev:~# rm /etc/puppetlabs/puppet/ssl/*/puppetdev.pem\nroot@puppetdev:~# systemctl start puppetserver.service \nroot@puppetdev:~# ls /etc/puppetlabs/puppet/ssl/*/puppetdev*.pem\n/etc/puppetlabs/puppet/ssl/certs/puppetdev.example.org.pem /etc/puppetlabs/puppet/ssl/private_keys/puppetdev.example.org.pem /etc/puppetlabs/puppet/ssl/public_keys/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/certs/puppetdev.pem\t\t /etc/puppetlabs/puppet/ssl/private_keys/puppetdev.pem\t /etc/puppetlabs/puppet/ssl/public_keys/puppetdev.pem\nroot@puppetdev:~# puppetserver ca list --all\nSigned Certificates:\n puppetagent1.example.org (SHA256) 7E:E6:DF:B0:83:B7:36:C2:F1:4E:D8:33:31:74:75:A4:EE:58:C9:0D:A2:78:AC:D9:D4:04:1D:8A:AA:00:9B:19\n puppetagent2.example.org (SHA256) 09:EB:01:B7:41:5F:6B:18:DC:25:B5:13:6A:F7:4B:34:66:E0:81:49:6F:25:9B:EC:5F:1B:09:21:EE:1E:27:F0\n puppetdev (SHA256) 27:67:97:4A:B1:B9:99:AF:14:2F:28:37:72:06:E8:B7:C5:E1:64:EF:0A:DE:F7:2D:21:83:5E:89:70:F6:42:B4\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev\"]\tauthorization extensions: [pp_cli_auth: true]\n puppetdev.example.org (SHA256) E4:6D:7F:84:71:D8:74:15:ED:1E:F7:79:D8:A5:A4:93:B6:A2:5A:52:1C:B6:08:34:D4:88:32:C2:99:CD:87:20\talt names: [\"DNS:puppetdev.example.org\", \"DNS:puppetdev\", \"DNS:puppetdev.example.org\"]\tauthorization extensions: [pp_cli_auth: true]\nroot@puppetdev:~# ls -1 /etc/puppetlabs/puppet/ssl/*/puppetdev*.pem\n/etc/puppetlabs/puppet/ssl/certs/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/certs/puppetdev.pem\n/etc/puppetlabs/puppet/ssl/private_keys/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/private_keys/puppetdev.pem\n/etc/puppetlabs/puppet/ssl/public_keys/puppetdev.example.org.pem\n/etc/puppetlabs/puppet/ssl/public_keys/puppetdev.pem\n{code}\nI never encountered this behavior with Puppet 6.\n\nI managed to reproduce this behavior reliably on test server when upgrading from Puppet 6 to Puppet 7.\n\n\u00a0", "epicLinkSummary": null, "estimate": "PT0S", "externalId": "61811", "fixedVersions": ["FACT 4.0.52"], "id": "61811", "issueType": "Bug", "key": "FACT-2944", "labels": ["community", "doc_reviewed"], "originalEstimate": "PT0S", "parent": null, "parentSummary": null, "priority": "Normal", "projectDescription": "

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Welcome to your project

Describe your project here

Change the project description to include details about your project.

", "projectKey": "FACT", "projectLead": "70121:199f31c7-67c7-42b0-b148-18ad3a391ab0", "projectName": "Facter (Archived)", "projectType": "software", "projectUrl": null, "reporter": "557058:e0340dee-9d48-48c3-8c6a-02597af847c9", "status": "Needs Information", "statusCategory": "To Do", "statuscategorychangedate": "11/Mar/23 10:29 AM", "summary": "Facter does not correctly detect that it is running inside of a podman container", "timeSpent": "PT0S", "updated": "2022-11-23T06:50:00.000000", "votes": "0", "watchers": []}, {"affectedVersions": [], "assignee": "70121:b92a8953-f29c-406d-a628-2e9b7468e50d", "attachments": [], "comments": [{"author": "70121:4596f954-1fdf-472f-a700-6b7c2ffbc525", "body": "also bump sys-filesystem in puppet-agent", "created": "2021-04-14T03:52:00.000000"}], "components": [], "created": "2021-01-28T02:44:00.000000", "creator": "6243b3c84fe01d006ba5c5e3", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@5ab6d7cd"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "Method Found", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|o07th6:"}, {"fieldName": "Release Notes", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Bug Fix"}, {"fieldName": "Release Notes Summary", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:textarea", "value": "When a mountpoint file cannot be read, or is missing, Facter would throw\nan error, without specifying what mountpoint/file has failed.\nThe error is now silent, allowing Facter to continue resolving facts. The detailed error is still shown when running Facter with debug logging enabled."}, {"fieldName": "Story Points", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:float", "value": "1.0"}, {"fieldName": "[CHART] Date of First Response", "fieldType": "com.atlassian.jira.ext.charting:firstresponsedate", "value": "14/Apr/21"}, {"fieldName": "[CHART] Time in Status", "fieldType": "com.atlassian.jira.ext.charting:timeinstatus", "value": "10008_*:*_1_*:*_538014733_*|*_1_*:*_1_*:*_2853582282_*|*_10007_*:*_1_*:*_585805901_*|*_3_*:*_1_*:*_437303348_*|*_5_*:*_1_*:*_0_*|*_10005_*:*_1_*:*_4498163771"}], "description": "# puppet --version\n7.3.0\n\non CentOS 7 with up2date system.\n\nWhen running puppet or gathering facts, I had the following error:\n\n{code}\n# puppet facts show\n[...]\nDebug: Facter: Executing command: which blkid\nError: Facter: statvfs() function failed: No such file or directory\nDebug: Facter: Executing command: /bin/cat /proc/uptime\n[...]\n{code}\n\nAfter poking around in the vendored ruby, I figured out this error is raised in `/opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/sys-filesystem-1.3.2/lib/sys/unix/sys/filesystem.rb` on line 205.\n\nAfter instrumenting the code with:\n\n{code}\n if statvfs(path, fs) < 0\nputs path\nputs fs.inspect\nputs caller\n raise Error, 'statvfs() function failed: ' + strerror(FFI.errno)\n end\n{code}\n\nI got the following:\n\n{code}\n# puppet facts show\n[...]\n/var/named/chroot/etc/localtime (deleted)\n#\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/util/resolvers/filesystem_helper.rb:20:in `read_mountpoint_stats'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/resolvers/mountpoints.rb:70:in `get_mount_sizes'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/resolvers/mountpoints.rb:54:in `block in read_mounts'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/resolvers/mountpoints.rb:48:in `each'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/resolvers/mountpoints.rb:48:in `read_mounts'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/resolvers/mountpoints.rb:16:in `block in post_resolve'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/resolvers/mountpoints.rb:16:in `fetch'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/resolvers/mountpoints.rb:16:in `post_resolve'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/resolvers/base_resolver.rb:26:in `block in resolve'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/resolvers/base_resolver.rb:24:in `synchronize'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/resolvers/base_resolver.rb:24:in `resolve'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/facts/linux/partitions.rb:14:in `partitions'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/facts/linux/partitions.rb:9:in `call_the_resolver'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/internal/core_fact.rb:16:in `block in create'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/benchmarking/timer.rb:18:in `measure'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/internal/core_fact.rb:15:in `create'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/internal/internal_fact_manager.rb:47:in `block in resolve_sequentially'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/internal/internal_fact_manager.rb:44:in `each'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/internal/internal_fact_manager.rb:44:in `resolve_sequentially'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact/internal/internal_fact_manager.rb:12:in `resolve_facts'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact_manager.rb:24:in `resolve_facts'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:385:in `values'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/cli/cli.rb:126:in `arg_parser'\n/opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'\n/opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'\n/opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'\n/opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.0.1/lib/thor/invocation.rb:116:in `invoke'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:43:in `resolve'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/facts/facter.rb:107:in `find_with_options'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/facts/facter.rb:37:in `find'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:223:in `find'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/face/facts.rb:148:in `block (3 levels) in '\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/interface/action.rb+eval[wrapper]:261:in `show'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/face_base.rb:254:in `main'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:437:in `run_command'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:421:in `block in run'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:735:in `exit_on_fail'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:421:in `run'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:143:in `run'\n/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:77:in `execute'\n/opt/puppetlabs/puppet/bin/puppet:5:in `

'\nError: Facter: statvfs() function failed: No such file or directory\n{code}\n\nSo I looked at my mounts:\n\n{code}\n# mount\n[...]\n/dev/mapper/vg-root on /var/named/chroot/etc/localtime type ext4 (rw,relatime,seclabel,data=ordered)\n/dev/mapper/vg-root on /var/named/chroot/etc/named.root.key type ext4 (rw,relatime,seclabel,data=ordered)\n/dev/mapper/vg-root on /var/named/chroot/etc/named.conf type ext4 (rw,relatime,seclabel,data=ordered)\n/dev/mapper/vg-root on /var/named/chroot/etc/named.rfc1912.zones type ext4 (rw,relatime,seclabel,data=ordered)\n/dev/mapper/vg-root on /var/named/chroot/etc/rndc.key type ext4 (rw,relatime,seclabel,data=ordered)\n/dev/mapper/vg-root on /var/named/chroot/etc/named.iscdlv.key type ext4 (rw,relatime,seclabel,data=ordered)\n/dev/mapper/vg-root on /var/named/chroot/etc/protocols type ext4 (rw,relatime,seclabel,data=ordered)\n/dev/mapper/vg-root on /var/named/chroot/etc/services type ext4 (rw,relatime,seclabel,data=ordered)\n/dev/mapper/vg-root on /var/named/chroot/etc/named type ext4 (rw,relatime,seclabel,data=ordered)\n/dev/mapper/vg-root on /var/named/chroot/usr/lib64/bind type ext4 (rw,relatime,seclabel,data=ordered)\ntmpfs on /var/named/chroot/run/named type tmpfs (rw,nosuid,nodev,seclabel,mode=755)\n/dev/mapper/vg-root on /var/named/chroot/var/named type ext4 (rw,relatime,seclabel,data=ordered)\n{code}\n\nOk, this seems to be the chroot from named, what about the file:\n\n{code}\n# ls -l /var/named/chroot/etc/localtime\n-rw-r--r--. 0 root root 1892 Nov 4 22:14 /var/named/chroot/etc/localtime\n{code}\n\nLooks like the file got replaced and thus deleted.\n\nRestarting named-chroot, re-setup the chroot AND the file has a size again:\n\n{code}\n# ls -l /var/named/chroot/etc/localtime\n-rw-r--r--. 3 root root 1892 Jan 26 22:55 /var/named/chroot/etc/localtime\n{code}\n\nAnd now also the error is gone.\n\nSo there seem to have been an update that deleted the file in the chroot and thus the service needed to be restarted.\n\nHowever facter just tries to blindly get file stats from even deleted files. So maybe this should be checked before passing it down to the filesystem lib. At least it does not seem very descriptive if the error appears.", "epicLinkSummary": null, "estimate": "PT0S", "externalId": "60881", "fixedVersions": ["FACT 4.2.0"], "id": "60881", "issueType": "Bug", "key": "FACT-2928", "labels": ["community", "doc-reviewed"], "originalEstimate": "PT0S", "parent": null, "parentSummary": null, "priority": "Normal", "projectDescription": "

Welcome to your project

Describe your project here

Change the project description to include details about your project.

'\n{noformat}\n\nIf I'm not mistaken the error happens when /proc/cpuinfo reports a frequency of less then 1 GHz. I'll open a PR at github to address the issue.", "environment": "Linux, Ubuntu 20.04.1, puppet 7.3.0, facter 4.0.49", "epicLinkSummary": null, "estimate": "PT0S", "externalId": "61808", "fixedVersions": ["FACT 4.0.50"], "id": "61808", "issueType": "Bug", "key": "FACT-2927", "labels": ["doc_reviewed"], "originalEstimate": "PT0S", "parent": null, "parentSummary": null, "priority": "Normal", "projectDescription": "

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a020: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a019: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a018: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a017: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a016: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a015: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:15:in `' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a014: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a013: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a012: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:10:in `' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a011: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:13:in `' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a010: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options.rb:40:in `init' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a09: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options/config_file_options.rb:12:in `init' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a08: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options/config_file_options.rb:24:in `augment_all' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a07: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options/config_file_options.rb:93:in `augment_facts' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a06: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/options/config_file_options.rb:93:in `new' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a05: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:16:in `initialize' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a04: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:83:in `load_facts_ttls' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a03: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:83:in `each' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a02: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:84:in `block in load_facts_ttls' \n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a01: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:106:in `ttls_to_seconds' \n /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/config/fact_groups.rb:106:in `*': nil can't be coerced into Integer (TypeError)", "created": "2021-03-09T10:31:00.000000"}, {"author": "6007ea942a6b66006902c024", "body": "Hi [~accountid:618d77713ae523006917eb86]\u00a0,\n\n\u00a0\n\nGood catch! The failure you're seeing is because we didn't accept forms like 'day', only 'days' and it's not because of the JSON form (which is hocon validated). A pull request was opened to fix this issue.\n\n\u00a0\n\nThank you for reporting this!", "created": "2021-03-10T01:37:00.000000"}, {"author": "5abd613dd4cf3c56be24b70d", "body": "These changes were already released, we need a new ticket for this.", "created": "2021-03-10T02:07:00.000000"}, {"author": "6007ea942a6b66006902c024", "body": "I've created\u00a0created a new ticket for the reported problem: https://puppet.atlassian.net/browse/FACT-2960\u00a0", "created": "2021-03-10T02:48:00.000000"}], "components": [], "created": "2021-01-19T12:03:00.000000", "creator": "618d77713ae523006917eb86", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@6c6022a7"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "Method Found", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|o05yjs:"}, {"fieldName": "Release Notes", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Bug Fix"}, {"fieldName": "Release Notes Summary", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:textarea", "value": "Description of the problem: Facter fails when an invalid config file is provided.\n\nDescription of the fix: Log a warning message stating that the parsing of config file failed and continue retrieving facts with the default options."}, {"fieldName": "Story Points", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:float", "value": "2.0"}, {"fieldName": "[CHART] Date of First Response", "fieldType": "com.atlassian.jira.ext.charting:firstresponsedate", "value": "10/Mar/21"}, {"fieldName": "[CHART] Time in Status", "fieldType": "com.atlassian.jira.ext.charting:timeinstatus", "value": "10008_*:*_1_*:*_424555973_*|*_1_*:*_2_*:*_107842294_*|*_10007_*:*_1_*:*_161066917_*|*_3_*:*_1_*:*_4165142_*|*_10009_*:*_2_*:*_2825316_*|*_5_*:*_1_*:*_3573779188_*|*_6_*:*_1_*:*_0_*|*_10005_*:*_1_*:*_10072576"}], "description": "With facter 4 shipped with puppet 7.1 if the facter.conf file is invalid facter fails to load at all which prevents all subsequent puppet runs.\u00a0\n\n\u00a0\n\nThis means that instead of being able to fix the problem with a puppet run the administrator has to login to any affected server and fix the file by hand.\u00a0\u00a0\n\nWould it be possible to fail \"open\" if the file is invalid?\u00a0 Log an error and run with all defaults?\u00a0 This would at least allow puppet to fix the problem on a subsequent run.", "epicLinkSummary": null, "estimate": "PT0S", "externalId": "61807", "fixedVersions": ["FACT 4.0.50"], "id": "61807", "issueType": "Bug", "key": "FACT-2924", "labels": ["doc_reviewed"], "originalEstimate": "PT0S", "parent": null, "parentSummary": null, "priority": "Normal", "projectDescription": "

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

", "projectKey": "FACT", "projectLead": "70121:199f31c7-67c7-42b0-b148-18ad3a391ab0", "projectName": "Facter (Archived)", "projectType": "software", "projectUrl": null, "reporter": "623c094c9b54ec0068b13f06", "status": "Accepted", "statusCategory": "To Do", "statuscategorychangedate": "11/Mar/23 10:29 AM", "summary": "Random failing unit tests", "timeSpent": "PT0S", "updated": "2021-06-30T00:23:00.000000", "votes": "0", "watchers": []}, {"affectedVersions": [], "assignee": "5b9fcedc03b52466f05c4510", "attachments": [], "comments": [{"author": "5b9fcedc03b52466f05c4510", "body": "https://github.com/puppetlabs/facter/pull/2257", "created": "2021-01-15T03:20:00.000000"}], "components": [], "created": "2021-01-14T17:23:00.000000", "creator": "557058:91233464-4152-4228-81dd-172d43a52a03", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@5d02b2be"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "Method Found", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|o05w6o:"}, {"fieldName": "Release Notes", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Bug Fix"}, {"fieldName": "Release Notes Summary", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:textarea", "value": "Fixed a bug where facter was breaking when trying to add a debug message for the location where an aggregate facts is resolved from. This only happed for aggregate facts that return an array or hash, without having an aggregate block call."}, {"fieldName": "[CHART] Date of First Response", "fieldType": "com.atlassian.jira.ext.charting:firstresponsedate", "value": "15/Jan/21"}, {"fieldName": "[CHART] Time in Status", "fieldType": "com.atlassian.jira.ext.charting:timeinstatus", "value": "10008_*:*_1_*:*_234844629_*|*_1_*:*_1_*:*_46387002_*|*_5_*:*_1_*:*_0"}], "description": "Commit d48c237c added debugging but broke aggregate fact handling. To reproduce:\n\n{noformat}\n$ mkdir facts\n$ cat > facts/agg.rb < :aggregate) do\n chunk :first do\n ['foo']\n end\n\n chunk :second do\n ['bar']\n end\nend\nEND\n$ bx facter --custom-dir `pwd`/facts foo\nbundler: failed to load command: facter (/Users/josh/work/facter/.bundle/ruby/2.5.0/bin/facter)\nTraceback (most recent call last):\n\t39: from /usr/local/opt/rbenv/versions/2.5.8/bin/bundle:23:in `

'\n ...\n\t16: from /Users/josh/work/facter/lib/facter/framework/cli/cli.rb:114:in `query'\n\t15: from /Users/josh/work/facter/lib/facter.rb:414:in `to_user_output'\n\t14: from /Users/josh/work/facter/lib/facter.rb:473:in `resolve_facts_for_user_query'\n\t13: from /Users/josh/work/facter/lib/facter/framework/core/fact_manager.rb:25:in `resolve_facts'\n\t12: from /Users/josh/work/facter/lib/facter/framework/core/fact/external/external_fact_manager.rb:7:in `resolve_facts'\n\t11: from /Users/josh/work/facter/lib/facter/framework/core/fact/external/external_fact_manager.rb:19:in `external_facts'\n\t10: from /Users/josh/work/facter/lib/facter/framework/core/fact/external/external_fact_manager.rb:19:in `each'\n\t 9: from /Users/josh/work/facter/lib/facter/framework/core/fact/external/external_fact_manager.rb:21:in `block in external_facts'\n\t 8: from /Users/josh/work/facter/lib/facter/custom_facts/util/fact.rb:121:in `value'\n\t 7: from /Users/josh/work/facter/lib/facter/custom_facts/util/fact.rb:167:in `searching'\n\t 6: from /Users/josh/work/facter/lib/facter/custom_facts/util/fact.rb:124:in `block in value'\n\t 5: from /Users/josh/work/facter/lib/facter/framework/benchmarking/timer.rb:18:in `measure'\n\t 4: from /Users/josh/work/facter/lib/facter/custom_facts/util/fact.rb:125:in `block (2 levels) in value'\n\t 3: from /Users/josh/work/facter/lib/facter/custom_facts/util/fact.rb:199:in `find_first_real_value'\n\t 2: from /Users/josh/work/facter/lib/facter/custom_facts/util/fact.rb:199:in `each'\n\t 1: from /Users/josh/work/facter/lib/facter/custom_facts/util/fact.rb:208:in `block in find_first_real_value'\n/Users/josh/work/facter/lib/facter/custom_facts/util/fact.rb:217:in `log_fact_path': undefined method `source_location' for nil:NilClass (NoMethodError)\n{noformat}\n\nAlso I noticed that 4.x facter does not accept a relative custom dir:\n\n{noformat}\n$ bx facter --custom-dir facts foo\nExcluding facts from search path. Fact file paths must be an absolute directory\n{noformat}\n\nBut 3.x facter does, is the facter 4 behavior intentional?\n\n{noformat}\n[root@aural-heater ~]# facter --custom-dir facts/ foo\n[\n \"foo\",\n \"bar\"\n]\n{noformat}\n\nIt took me a little while to reproduce the problem because the [docs for aggregate facts|https://puppet.com/docs/puppet/7.1/custom_facts.html#aggregate_resolutions] show each {{chunk}} returning a string, but it needs to be an array or hash:\n", "epicLinkSummary": null, "estimate": "PT0S", "externalId": "63283", "fixedVersions": ["FACT 4.0.49"], "id": "63283", "issueType": "Bug", "key": "FACT-2919", "labels": [], "originalEstimate": "PT0S", "parent": null, "parentSummary": null, "priority": "Major", "projectDescription": "

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

", "projectKey": "FACT", "projectLead": "70121:199f31c7-67c7-42b0-b148-18ad3a391ab0", "projectName": "Facter (Archived)", "projectType": "software", "projectUrl": null, "reporter": "623c094c9b54ec0068b13f06", "status": "Accepted", "statusCategory": "To Do", "statuscategorychangedate": "11/Mar/23 10:29 AM", "summary": "Check validity of options inside the facter --help", "timeSpent": "PT0S", "updated": "2021-06-30T00:24:00.000000", "votes": "0", "watchers": []}, {"affectedVersions": [], "assignee": "623c094c9b54ec0068b13f06", "attachments": [], "comments": [], "components": [], "created": "2021-01-07T06:42:00.000000", "creator": "623c094c9b54ec0068b13f06", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": ["ghost"]}, {"fieldName": "Acceptance Criteria", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:textarea", "value": "Add the hocon option in OptionStore and update the unit tests for it. Also an acceptance would be nice to have."}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@62f2e7e7"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|o05haj:o"}, {"fieldName": "Release Notes", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Bug Fix"}, {"fieldName": "Release Notes Summary", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:textarea", "value": "Now the --hocon option functions as intended."}, {"fieldName": "[CHART] Time in Status", "fieldType": "com.atlassian.jira.ext.charting:timeinstatus", "value": "1_*:*_1_*:*_38787_*|*_3_*:*_1_*:*_24663298_*|*_10009_*:*_1_*:*_233397592_*|*_5_*:*_1_*:*_0_*|*_10005_*:*_1_*:*_71775330"}], "description": "Because the hocon option is missing from the OptionStore, when the --hocon option is used, facter throws an exception.\n\n", "epicLinkSummary": null, "estimate": "PT0S", "externalId": "63037", "fixedVersions": ["FACT 4.0.48"], "id": "63037", "issueType": "Bug", "key": "FACT-2909", "labels": ["doc_reviewed", "platform_7.2"], "originalEstimate": "PT0S", "parent": null, "parentSummary": null, "priority": "Normal", "projectDescription": "

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

", "projectKey": "FACT", "projectLead": "70121:199f31c7-67c7-42b0-b148-18ad3a391ab0", "projectName": "Facter (Archived)", "projectType": "software", "projectUrl": null, "reporter": "623c1489a1d81f0069d8e30a", "status": "Accepted", "statusCategory": "To Do", "statuscategorychangedate": "11/Mar/23 10:29 AM", "summary": "Add acceptance test to compare fact types between facter 3 and facter 4", "timeSpent": "PT0S", "updated": "2021-10-21T05:28:00.000000", "votes": "0", "watchers": []}, {"affectedVersions": [], "assignee": "623c1489a1d81f0069d8e30a", "attachments": [{"attacher": "623c1489a1d81f0069d8e30a", "created": "2020-11-27T08:22:00.000000", "name": "facter-apis.png", "uri": "https://puppet.atlassian.net/rest/api/3/attachment/content/14850"}], "comments": [{"author": "557058:9a0622ba-116b-4661-81b3-6a2a72bf7d68", "body": "I did some testing with the puppet 7 gem on Arch linux and undef facts are treated as undef:\n\n{code}\nbastelfreak@bastelfreak-ws /tmp/puppet7 $ bundle exec puppet apply test.pp \nWarning: Found multiple default providers for package: gem, pip, pip3, pip2", "created": "2020-11-24T11:43:00.000000"}, {"author": "557058:9a0622ba-116b-4661-81b3-6a2a72bf7d68", "body": "additional information:\nfacter is 4.0.46 on both boxes\n\nthe ubuntu setup:\n{code}\nroot@* ~ # facter --version\n4.0.46\nroot@* ~ # which facter\n/opt/puppetlabs/bin/facter\nroot@* ~ # \n{code}\n\nand the gem install:\n\n{code}\nbastelfreak@bastelfreak-ws /tmp/puppet7 $ bundle exec gem which facter\n/tmp/puppet7/.vendor/ruby/2.7.0/gems/facter-4.0.46/lib/facter.rb\nbastelfreak@bastelfreak-ws /tmp/puppet7 $ \n{code}", "created": "2020-11-24T11:52:00.000000"}, {"author": "557058:9a0622ba-116b-4661-81b3-6a2a72bf7d68", "body": "it's working properly on CentOS 7 with Puppet 7 rpms:\n{code}\nroot@* ~ # cat test.pp\n$var = $facts['THISDOESNOTEXISTHOPEFULLY'] ? {\n '' => 'empty string',\n undef => 'undef',\n default => $facts['foo'],\n}\n\nnotify { $var:}\nroot@* ~ #\nNotice: Compiled catalog for *s in environment production in 0.03 seconds\nNotice: undef\nNotice: /Stage[main]/Main/Notify[undef]/message: defined 'message' as 'undef'\nNotice: Applied catalog in 0.33 seconds\nroot@* ~ #\n{code}\n\nthe same works on ubuntu 16 as well:\n{code}\nroot@* ~ # puppet apply test2.pp \nNotice: Compiled catalog for * in environment production in 0.04 seconds\nNotice: undef\nNotice: /Stage[main]/Main/Notify[undef]/message: defined 'message' as 'undef'\nNotice: Applied catalog in 0.21 seconds\nroot@* ~ # cat test2.pp \n$var = $facts['THISDOESNOTEXISTHOPEFULLY'] ? {\n '' => 'empty string',\n undef => 'undef',\n default => $facts['foo'],\n}\n\nnotify { $var:}\nroot@* ~ # puppet --version\n7.0.0\nroot@* ~ # \n{code}\n\nso I guess something is wrong with the fact sach_passalgo I posted in the initial description.", "created": "2020-11-24T12:04:00.000000"}, {"author": "6007ea942a6b66006902c024", "body": "Hi [~accountid:557058:9a0622ba-116b-4661-81b3-6a2a72bf7d68]\u00a0,\n\n\u00a0\n\nI managed to reproduce the issue:\n\n\u00a0\n{code:java}\nNotice: Compiled catalog for closest-buffoon.delivery.puppetlabs.net in environment production in 0.02 seconds\nNotice: test\nNotice: /Stage[main]/Main/Notify[test]/message: defined 'message' as 'test'\nNotice: empty string\nNotice: /Stage[main]/Main/Notify[empty string]/message: defined 'message' as 'empty string'\nNotice: Applied catalog in 0.01 seconds\n{code}\nFacter 4 was reporting custom facts that return nil value and puppet reports them as empty strings (due to puppet json formatting).\n\n\u00a0\n\n\u00a0\n\nWe made a fix for this\u00a0 problem and the output is now as expected:\n{code:java}\nroot@closest-buffoon:~# /opt/puppetlabs/bin/puppet apply test.pp\nNotice: Compiled catalog for closest-buffoon.delivery.puppetlabs.net in environment production in 0.02 seconds\nNotice: test\nNotice: /Stage[main]/Main/Notify[test]/message: defined 'message' as 'test'\nNotice: undef\nNotice: /Stage[main]/Main/Notify[undef]/message: defined 'message' as 'undef'\nNotice: Applied catalog in 0.01 seconds\n{code}", "created": "2020-11-26T04:52:00.000000"}, {"author": "623c1489a1d81f0069d8e30a", "body": "Hi [~accountid:557058:9a0622ba-116b-4661-81b3-6a2a72bf7d68]\n\nPlease give https://github.com/puppetlabs/facter/pull/2200 a try and let me know if it works for you.\n", "created": "2020-11-27T08:07:00.000000"}, {"author": "557058:9a0622ba-116b-4661-81b3-6a2a72bf7d68", "body": "hey [~accountid:623c1489a1d81f0069d8e30a], thanks for the fix. I verified that it fixes this bug.", "created": "2020-11-30T09:36:00.000000"}, {"author": "557058:91233464-4152-4228-81dd-172d43a52a03", "body": "[~accountid:623c1489a1d81f0069d8e30a] Could you move this to the FACT project and update the PR's commit summary to reference the new ticket?", "created": "2020-11-30T10:25:00.000000"}, {"author": "557058:91233464-4152-4228-81dd-172d43a52a03", "body": "I went ahead and moved the issue to avoid confusion for new folks encountering the issue.", "created": "2020-12-01T17:59:00.000000"}, {"author": "623c1489a1d81f0069d8e30a", "body": "[~accountid:63d40628f6e1b543161789a7]\u00a0 thanks for moving this to FACTER! I changed the branch name [https://github.com/puppetlabs/facter/pull/2204]\u00a0 and the commit message.", "created": "2020-12-02T09:52:00.000000"}], "components": [], "created": "2020-11-24T09:17:00.000000", "creator": "557058:9a0622ba-116b-4661-81b3-6a2a72bf7d68", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": ["ghost"]}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@15691c81"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "Method Found", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|o05848:"}, {"fieldName": "Release Notes", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Bug Fix"}, {"fieldName": "Release Notes Summary", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:textarea", "value": "Exclude custom fact with nil value from `to_user_output`, `values` and `to_hash` ruby Facter API's. The custom facts with nil value as still returned by value, fact and [] API's\n"}, {"fieldName": "[CHART] Date of First Response", "fieldType": "com.atlassian.jira.ext.charting:firstresponsedate", "value": "26/Nov/20"}, {"fieldName": "[CHART] Time in Status", "fieldType": "com.atlassian.jira.ext.charting:timeinstatus", "value": "1_*:*_1_*:*_254849952_*|*_3_*:*_1_*:*_10231_*|*_10009_*:*_1_*:*_493820259_*|*_5_*:*_1_*:*_0"}], "description": "*Puppet Version:* 7.0.0\n*Puppet Server Version:* 6.14.1\n*OS Name/Version:* Ubuntu 16.04\n\nHi!\n* Sorry for the ugly issue title\n* this might be better as a facter issue, but I'm not sure\n\nI've the following fact:\n{code}\nFacter.add('sach_passalgo') do\n confine :osfamily => 'RedHat'\n confine { Facter::Core::Execution.which('authconfig') }\n\n setcode do\n authconfig_out = `authconfig --test`\n hash_algo = 'unknown'\n authconfig_out.each_line do |line|\n hash_algo = line.split(' ')[4] if line.include? 'password hashing'\n end\n hash_algo\n end\nend\n{code}\n\nI assume that this fact never exists on a Ubuntu/Debian system, because the fact is confined to osfamily RedHat. I expect `undef` as return value if I try to access this fact on a Debian node. This seems to be correct for Puppet 6:\n\n{code}\nnotify { \"test${facts['sach_passalgo']}\":}\n\n$var = $facts['sach_passalgo'] ? {\n undef => 'works',\n default => $facts['sach_passalgo'],\n}\n\nnotify { \"test1{$var}\":}\n{code}\n\nthis produces on puppet 6.14.0:\n{code}\nroot@* ~ # puppet apply test.pp \nNotice: Compiled catalog for * in environment production in 0.02 seconds\nNotice: test\nNotice: /Stage[main]/Main/Notify[test]/message: defined 'message' as 'test'\nNotice: works\nNotice: /Stage[main]/Main/Notify[test1works]/message: defined 'message' as 'test1works'\nNotice: Applied catalog in 0.27 seconds\nroot@* ~ # \n{code}\n\nnow with puppet 7:\n\n{code}\nroot@* ~ # puppet apply test.pp \nNotice: Compiled catalog for * in environment production in 0.04 seconds\nNotice: test\nNotice: /Stage[main]/Main/Notify[test]/message: defined 'message' as 'test'\nNotice: test1\nNotice: /Stage[main]/Main/Notify[test1]/message: defined 'message' as 'test1'\nNotice: Applied catalog in 0.21 seconds\nroot@* ~ # \n{code}\n\nnow I update the test code like this:\n\n{code}\nnotify { \"test${facts['sach_passalgo']}\":}\n\n$var = $facts['sach_passalgo'] ? {\n '' => 'empty string',\n undef => 'undef',\n default => $facts['sach_passalgo'],\n}\n\nnotify { $var:}\n{code}\n\nwhich produces the following output on puppet 7:\n\n{code}\nroot@* ~ # puppet apply test.pp \nNotice: Compiled catalog for * in environment production in 0.05 seconds\nNotice: test\nNotice: /Stage[main]/Main/Notify[test]/message: defined 'message' as 'test'\nNotice: empty string\nNotice: /Stage[main]/Main/Notify[empty string]/message: defined 'message' as 'empty string'\nNotice: Applied catalog in 0.28 seconds\nroot@* ~ # \n{code}\n\nA fact that was undef on Puppet 6 turned into empty string in Puppet 7?\n\n\n*Actual Behavior:*\nexpect that the fact is still undef\n\nlet me know if you need more debugging/testing or any information.", "epicLinkSummary": null, "estimate": "PT0S", "externalId": "63031", "fixedVersions": ["FACT 4.0.47"], "id": "63031", "issueType": "Bug", "key": "FACT-2881", "labels": ["doc_reviewed", "platform_7.1"], "originalEstimate": "PT0S", "parent": null, "parentSummary": null, "priority": "Normal", "projectDescription": "

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Describe your project here

Change the project description to include details about your project.

", "projectKey": "FACT", "projectLead": "70121:199f31c7-67c7-42b0-b148-18ad3a391ab0", "projectName": "Facter (Archived)", "projectType": "software", "projectUrl": null, "reporter": "623c1489a1d81f0069d8e30a", "status": "Accepted", "statusCategory": "To Do", "statuscategorychangedate": "11/Mar/23 10:29 AM", "summary": "Move all components from LegacyFacter module to Facter module", "timeSpent": "PT0S", "updated": "2021-10-20T02:56:00.000000", "votes": "0", "watchers": []}, {"affectedVersions": [], "assignee": null, "attachments": [], "comments": [], "components": [], "created": "2020-10-28T08:21:00.000000", "creator": "623c1489a1d81f0069d8e30a", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@386c0f5a"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "Epic Link", "fieldType": "com.pyxis.greenhopper.jira:gh-epic-link", "value": "PUP-11659"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|hzvq87:2i6000000i42090400j"}, {"fieldName": "Story Points", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:float", "value": "3.0"}, {"fieldName": "[CHART] Date of First Response", "fieldType": "com.atlassian.jira.ext.charting:firstresponsedate", "value": "10/Mar/21"}], "description": "all changes must keep backwards compatibility with existing API and configuration ", "epicLinkSummary": "Puppet Maintenance CY23 Q2", "estimate": "PT0S", "externalId": "62371", "fixedVersions": [], "id": "62371", "issueType": "Improvement", "key": "FACT-2848", "labels": ["platform_7.2"], "originalEstimate": "PT0S", "parent": "24608", "parentSummary": "Puppet Maintenance CY23 Q2", "priority": "Low (migrated)", "projectDescription": "

Welcome to your project

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Describe your project here

Change the project description to include details about your project.

", "projectKey": "FACT", "projectLead": "70121:199f31c7-67c7-42b0-b148-18ad3a391ab0", "projectName": "Facter (Archived)", "projectType": "software", "projectUrl": null, "reporter": "623c1489a1d81f0069d8e30a", "resolution": "Fixed", "resolutionDate": "2020-08-04T05:36:00.000000", "status": "Resolved", "statusCategory": "Done", "statuscategorychangedate": "11/Mar/23 10:29 AM", "summary": "networking facts don't work on EXADATA baremetal", "timeSpent": "PT0S", "updated": "2020-08-11T11:01:00.000000", "votes": "0", "watchers": []}, {"affectedVersions": [], "assignee": "623c1489a1d81f0069d8e30a", "attachments": [], "comments": [{"author": "623c1489a1d81f0069d8e30a", "body": "[~accountid:623a47aed32a94006a63c8b7] can you please provide the output of `lspci` command when you run in on `EXADATA baremetal`.", "created": "2020-07-30T05:04:00.000000"}, {"author": "623c1489a1d81f0069d8e30a", "body": "Also, [~accountid:623a47aed32a94006a63c8b7] could you please run\n{code}bundle exec facter --debug\n{code}\nwith the code from [FACT-2735 PR|https://github.com/IrimieBogdan/facter/tree/FACT-2735] and provide the output?\n\nThe code contains extra logging that could help us determine what is happening.", "created": "2020-07-30T05:44:00.000000"}, {"author": "623a47aed32a94006a63c8b7", "body": "[root@cgcldx0001 ~]# lspci\n00: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 PCI Express Root Port 2a (rev 04)\n00:02.2 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 2c (rev 04)\n00:03.0 PCI bridge: Intel Corporation Xeon 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.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 0 (rev 04)\n00:04.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 1 (rev 04)\n00:04.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 2 (rev 04)\n00:04.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 3 (rev 04)\n00:04.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 4 (rev 04)\n00:04.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 5 (rev 04)\n00:04.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 6 (rev 04)\n00:04.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 7 (rev 04)\n00:05.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 VTd/Memory Map/Misc (rev 04)\n00:05.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IIO RAS (rev 04)\n00:05.4 PIC: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IOAPIC (rev 04)\n00:11.0 PCI 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 USB2 Enhanced Host Controller #2 (rev 06)\n00:1c.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 1 (rev b6)\n00:1c.7 PCI bridge: Intel Corporation C600/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 (rev 06)\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-Port SATA AHCI Controller (rev 06)\n00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host Controller (rev 06)\n00:1f.6 Signal processing controller: Intel Corporation C600/X79 series chipset Thermal Management Controller (rev 06)\n20:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01)\n20:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01)\n30:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)\n30:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)\n40:00.0 InfiniBand: Mellanox Technologies MT27500 Family [ConnectX-3]\n50:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator] (rev 05)\n61:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 02)\n62:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 21)\n7f:0a.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 0 (rev 04)\n7f:0a.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 3 (rev 04)\n7f:0b.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 UBOX Registers (rev 04)\n7f:0b.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 UBOX Registers (rev 04)\n7f:0c.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\n7f:0c.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\n7f:0c.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\n7f:0d.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\n7f:0d.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\n7f:0d.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\n7f:0e.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 0 (rev 04)\n7f:0e.1 Performance counters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 0 (rev 04)\n7f:0f.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Target Address/Thermal Registers (rev 04)\n7f:0f.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 RAS Registers (rev 04)\n7f:0f.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)\n7f:0f.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)\n7f:0f.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)\n7f:0f.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)\n7f:10.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 0 (rev 04)\n7f:10.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 0 (rev 04)\n7f:10.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 1 (rev 04)\n7f:10.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 2 (rev 04)\n7f:10.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 3 (rev 04)\n7f:16.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 System Address Decoder (rev 04)\n7f:16.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Broadcast Registers (rev 04)\n7f:16.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Broadcast Registers (rev 04)\n7f:1c.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 1 (rev 04)\n7f:1c.1 Performance counters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 1 (rev 04)\n7f:1d.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Target Address/Thermal Registers (rev 04)\n7f:1d.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 RAS Registers (rev 04)\n7f:1d.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel Target Address Decoder Registers (rev 04)\n7f:1d.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel Target Address Decoder Registers (rev 04)\n7f:1d.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel Target Address Decoder Registers (rev 04)\n7f:1d.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel Target Address Decoder Registers (rev 04)\n7f:1e.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 Thermal Control 0 (rev 04)\n7f:1e.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 Thermal Control 1 (rev 04)\n7f:1e.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 ERROR Registers 0 (rev 04)\n7f:1e.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 ERROR Registers 1 (rev 04)\n7f:1e.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 Thermal Control 2 (rev 04)\n7f:1e.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 Thermal Control 3 (rev 04)\n7f:1e.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 ERROR Registers 2 (rev 04)\n7f:1e.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 ERROR Registers 3 (rev 04)\n80:00.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port in DMI2 Mode (rev 04)\n80:01.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 1a (rev 04)\n80:03.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 3a (rev 04)\n80:04.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 0 (rev 04)\n80:04.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 1 (rev 04)\n80:04.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 2 (rev 04)\n80:04.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 3 (rev 04)\n80:04.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 4 (rev 04)\n80:04.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 5 (rev 04)\n80:04.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 6 (rev 04)\n80:04.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 7 (rev 04)\n80:05.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 VTd/Memory Map/Misc (rev 04)\n80:05.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IIO RAS (rev 04)\n80:05.4 PIC: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IOAPIC (rev 04)\n88:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01)\n88:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01)\nff:0a.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 0 (rev 04)\nff:0a.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 3 (rev 04)\nff:0b.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 UBOX Registers (rev 04)\nff:0b.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 UBOX Registers (rev 04)\nff:0c.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\nff:0c.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\nff:0c.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\nff:0d.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\nff:0d.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\nff:0d.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\nff:0e.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 0 (rev 04)\nff:0e.1 Performance counters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 0 (rev 04)\nff:0f.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Target Address/Thermal Registers (rev 04)\nff:0f.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 RAS Registers (rev 04)\nff:0f.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)\nff:0f.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)\nff:0f.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)\nff:0f.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04)\nff:10.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 0 (rev 04)\nff:10.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 0 (rev 04)\nff:10.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 1 (rev 04)\nff:10.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 2 (rev 04)\nff:10.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 3 (rev 04)\nff:16.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 System Address Decoder (rev 04)\nff:16.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Broadcast Registers (rev 04)\nff:16.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Broadcast Registers (rev 04)\nff:1c.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 1 (rev 04)\nff:1c.1 Performance counters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 1 (rev 04)\nff:1d.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Target Address/Thermal Registers (rev 04)\nff:1d.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 RAS Registers (rev 04)\nff:1d.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel Target Address Decoder Registers (rev 04)\nff:1d.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel Target Address Decoder Registers (rev 04)\nff:1d.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel Target Address Decoder Registers (rev 04)\nff:1d.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel Target Address Decoder Registers (rev 04)\nff:1e.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 Thermal Control 0 (rev 04)\nff:1e.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 Thermal Control 1 (rev 04)\nff:1e.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 ERROR Registers 0 (rev 04)\nff:1e.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 ERROR Registers 1 (rev 04)\nff:1e.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 Thermal Control 2 (rev 04)\nff:1e.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 Thermal Control 3 (rev 04)\nff:1e.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 ERROR Registers 2 (rev 04)\nff:1e.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 ERROR Registers 3 (rev 04)\nYou have new mail in /var/spool/mail/root", "created": "2020-07-30T07:21:00.000000"}, {"author": "623c1489a1d81f0069d8e30a", "body": "[~accountid:623a47aed32a94006a63c8b7] thanks for the lspci output, it was really helpful in identifying why `virtual` fact returns the output of `lspci`. A fix was implemented on [FACT-2735|https://github.com/IrimieBogdan/facter/tree/FACT-2735]. Please give it a try and let me know if it works for you.", "created": "2020-07-31T05:51:00.000000"}, {"author": "623a47aed32a94006a63c8b7", "body": "That's great Bogdan. Will this fix (and the fix for FACT-2736) be in the next release (4.0.31)?\n\nI'd rather just wait for the next gem.", "created": "2020-07-31T06:05:00.000000"}, {"author": "623c1489a1d81f0069d8e30a", "body": "[~accountid:623a47aed32a94006a63c8b7]\u00a0 \n\n[FACT-2734|https://puppet.atlassian.net/browse/FACT-2734] is already released and you can test it with Facter [4.0.32|https://rubygems.org/gems/facter/versions/4.0.32].\n\n[FACT-2735|https://puppet.atlassian.net/browse/FACT-2735] has been merged in 4.x branch and will be available in the next release (4.0.33)\n\n[FACT-2736|https://puppet.atlassian.net/browse/FACT-2736] is experimental and only contain extra logging at the moment, we will improve it and probably it will be included in the 4.0.33 release as well. It does not contain the fix to the problem you reported. \n\nThe official releases on ruby-gems usually take between 1 and 2 weeks. If you want to test changes earlier and provide feedback in order to move faster, we can provide a private ruby gems repository that you can use to install the latest development version of Facter 4.", "created": "2020-08-03T08:44:00.000000"}], "components": [], "created": "2020-07-30T04:59:00.000000", "creator": "623c1489a1d81f0069d8e30a", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": ["ghost"]}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@15900b31"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|o03cn4:"}, {"fieldName": "Release Notes", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Not Needed"}, {"fieldName": "[CHART] Date of First Response", "fieldType": "com.atlassian.jira.ext.charting:firstresponsedate", "value": "30/Jul/20"}, {"fieldName": "[CHART] Time in Status", "fieldType": "com.atlassian.jira.ext.charting:timeinstatus", "value": "1_*:*_1_*:*_333730_*|*_3_*:*_2_*:*_5829433_*|*_10009_*:*_1_*:*_266547411_*|*_5_*:*_1_*:*_0_*|*_10005_*:*_1_*:*_83397523"}], "description": "On `EXADATA baremetal` running Oracle Linux\u00a0\n{code:java}\n 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}\n`virtual` fact returns\u00a0\n{code:java}\nvirtual: \"00:00.0 Host bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 DMI2\n(rev 04)\\n00:02.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI\nExpress Root Port 2a (rev 04)\\n00:02.2 PCI bridge: Intel Corporation Xeon E7 v2/Xeon\nE5 v2/Core i7 PCI Express Root Port 2c (rev 04)\\n00:03.0 PCI bridge: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 3a (rev 04)\\n00:03.2 PCI bridge:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port 3c (rev 04)\\n00:04.0\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach\nDMA Channel 0 (rev 04)\\n00:04.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon\nE5 v2/Core i7 Crystal Beach DMA Channel 1 (rev 04)\\n00:04.2 System peripheral: Intel\nCorporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 2 (rev 04)\\n00:04.3\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach\nDMA Channel 3 (rev 04)\\n00:04.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon\nE5 v2/Core i7 Crystal Beach DMA Channel 4 (rev 04)\\n00:04.5 System peripheral: Intel\nCorporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 5 (rev 04)\\n00:04.6\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach\nDMA Channel 6 (rev 04)\\n00:04.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon\nE5 v2/Core i7 Crystal Beach DMA Channel 7 (rev 04)\\n00:05.0 System peripheral: Intel\nCorporation Xeon E7 v2/Xeon E5 v2/Core i7 VTd/Memory Map/Misc (rev 04)\\n00:05.2\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IIO RAS (rev\n04)\\n00:05.4 PIC: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 IOAPIC (rev 04)\\n00:11.0\nPCI bridge: Intel Corporation C600/X79 series chipset PCI Express Virtual Root Port\n(rev 06)\\n00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2\nEnhanced Host Controller #2 (rev 06)\\n00:1c.0 PCI bridge: Intel Corporation C600/X79\nseries chipset PCI Express Root Port 1 (rev b6)\\n00:1c.7 PCI bridge: Intel Corporation\nC600/X79 series chipset PCI Express Root Port 8 (rev b6)\\n00:1d.0 USB controller:\nIntel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #1 (rev\n06)\\n00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC Controller\n(rev 06)\\n00:1f.2 SATA controller: Intel Corporation C600/X79 series chipset 6-Port\nSATA AHCI Controller (rev 06)\\n00:1f.3 SMBus: Intel Corporation C600/X79 series\nchipset SMBus Host Controller (rev 06)\\n00:1f.6 Signal processing controller: Intel\nCorporation C600/X79 series chipset Thermal Management Controller (rev 06)\\n20:00.0\nEthernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev\n01)\\n20:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit\nX540-AT2 (rev 01)\\n30:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit\nSFI/SFP+ Network Connection (rev 01)\\n30:00.1 Ethernet controller: Intel Corporation\n82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)\\n40:00.0 InfiniBand: Mellanox\nTechnologies MT27500 Family\u00a0[ConnectX-3]\\n50:00.0 RAID bus controller: LSI Logic\n/ Symbios Logic MegaRAID SAS 2108\u00a0[Liberator]\u00a0(rev 05)\\n61:00.0 PCI bridge: ASPEED\nTechnology, Inc. AST1150 PCI-to-PCI Bridge (rev 02)\\n62:00.0 VGA compatible controller:\nASPEED Technology, Inc. ASPEED Graphics Family (rev 21)\\n7f:0a.0 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 0 (rev 04)\\n7f:0a.3\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control\nUnit 3 (rev 04)\\n7f:0b.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5\nv2/Core i7 UBOX Registers (rev 04)\\n7f:0b.3 System peripheral: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 UBOX Registers (rev 04)\\n7f:0c.0 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\\n7f:0c.4\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers\n(rev 04)\\n7f:0c.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 Unicast Registers (rev 04)\\n7f:0d.0 System peripheral: Intel Corporation Xeon\nE7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\\n7f:0d.4 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\\n7f:0d.5\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers\n(rev 04)\\n7f:0e.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 Home Agent 0 (rev 04)\\n7f:0e.1 Performance counters: Intel Corporation Xeon E7\nv2/Xeon E5 v2/Core i7 Home Agent 0 (rev 04)\\n7f:0f.0 System peripheral: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Target Address/Thermal\nRegisters (rev 04)\\n7f:0f.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon\nE5 v2/Core i7 Integrated Memory Controller 0 RAS Registers (rev 04)\\n7f:0f.2 System\nperipheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller\n0 Channel Target Address Decoder Registers (rev 04)\\n7f:0f.3 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel\nTarget Address Decoder Registers (rev 04)\\n7f:0f.4 System peripheral: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address\nDecoder Registers (rev 04)\\n7f:0f.5 System peripheral: Intel Corporation Xeon E7\nv2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder\nRegisters (rev 04)\\n7f:10.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon\nE5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 0 (rev\n04)\\n7f:10.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7\nIntegrated Memory Controller 1 Channel 0-3 ERROR Registers 0 (rev 04)\\n7f:10.3 System\nperipheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller\n1 Channel 0-3 ERROR Registers 1 (rev 04)\\n7f:10.6 System peripheral: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers\n2 (rev 04)\\n7f:10.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 3 (rev 04)\\n7f:16.0\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 System Address\nDecoder (rev 04)\\n7f:16.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5\nv2/Core i7 Broadcast Registers (rev 04)\\n7f:16.2 System peripheral: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 Broadcast Registers (rev 04)\\n7f:1c.0 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 1 (rev 04)\\n7f:1c.1 Performance\ncounters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 1 (rev 04)\\n7f:1d.0\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory\nController 1 Target Address/Thermal Registers (rev 04)\\n7f:1d.1 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 RAS\nRegisters (rev 04)\\n7f:1d.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon\nE5 v2/Core i7 Integrated Memory Controller 1 Channel Target Address Decoder Registers\n(rev 04)\\n7f:1d.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 Integrated Memory Controller 1 Channel Target Address Decoder Registers (rev\n04)\\n7f:1d.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7\nIntegrated Memory Controller 1 Channel Target Address Decoder Registers (rev 04)\\n7f:1d.5\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory\nController 1 Channel Target Address Decoder Registers (rev 04)\\n7f:1e.0 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel\n0-3 Thermal Control 0 (rev 04)\\n7f:1e.1 System peripheral: Intel Corporation Xeon\nE7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 Thermal Control\n1 (rev 04)\\n7f:1e.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 Integrated Memory Controller 0 Channel 0-3 ERROR Registers 0 (rev 04)\\n7f:1e.3\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory\nController 0 Channel 0-3 ERROR Registers 1 (rev 04)\\n7f:1e.4 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel\n0-3 Thermal Control 2 (rev 04)\\n7f:1e.5 System peripheral: Intel Corporation Xeon\nE7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 Thermal Control\n3 (rev 04)\\n7f:1e.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 Integrated Memory Controller 0 Channel 0-3 ERROR Registers 2 (rev 04)\\n7f:1e.7\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory\nController 0 Channel 0-3 ERROR Registers 3 (rev 04)\\n80:00.0 PCI bridge: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port in DMI2 Mode (rev 04)\\n80:01.0\nPCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 PCI Express Root Port\n1a (rev 04)\\n80:03.0 PCI bridge: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7\nPCI Express Root Port 3a (rev 04)\\n80:04.0 System peripheral: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 0 (rev 04)\\n80:04.1 System\nperipheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel\n1 (rev 04)\\n80:04.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 Crystal Beach DMA Channel 2 (rev 04)\\n80:04.3 System peripheral: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 3 (rev 04)\\n80:04.4 System\nperipheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel\n4 (rev 04)\\n80:04.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 Crystal Beach DMA Channel 5 (rev 04)\\n80:04.6 System peripheral: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel 6 (rev 04)\\n80:04.7 System\nperipheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Crystal Beach DMA Channel\n7 (rev 04)\\n80:05.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 VTd/Memory Map/Misc (rev 04)\\n80:05.2 System peripheral: Intel Corporation Xeon\nE7 v2/Xeon E5 v2/Core i7 IIO RAS (rev 04)\\n80:05.4 PIC: Intel Corporation Xeon E7\nv2/Xeon E5 v2/Core i7 IOAPIC (rev 04)\\n88:00.0 Ethernet controller: Intel Corporation\nEthernet Controller 10-Gigabit X540-AT2 (rev 01)\\n88:00.1 Ethernet controller: Intel\nCorporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01)\\nff:0a.0 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control Unit 0 (rev 04)\\nff:0a.3\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Power Control\nUnit 3 (rev 04)\\nff:0b.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5\nv2/Core i7 UBOX Registers (rev 04)\\nff:0b.3 System peripheral: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 UBOX Registers (rev 04)\\nff:0c.0 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\\nff:0c.4\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers\n(rev 04)\\nff:0c.5 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 Unicast Registers (rev 04)\\nff:0d.0 System peripheral: Intel Corporation Xeon\nE7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\\nff:0d.4 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers (rev 04)\\nff:0d.5\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Unicast Registers\n(rev 04)\\nff:0e.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 Home Agent 0 (rev 04)\\nff:0e.1 Performance counters: Intel Corporation Xeon E7\nv2/Xeon E5 v2/Core i7 Home Agent 0 (rev 04)\\nff:0f.0 System peripheral: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Target Address/Thermal\nRegisters (rev 04)\\nff:0f.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon\nE5 v2/Core i7 Integrated Memory Controller 0 RAS Registers (rev 04)\\nff:0f.2 System\nperipheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller\n0 Channel Target Address Decoder Registers (rev 04)\\nff:0f.3 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel\nTarget Address Decoder Registers (rev 04)\\nff:0f.4 System peripheral: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address\nDecoder Registers (rev 04)\\nff:0f.5 System peripheral: Intel Corporation Xeon E7\nv2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder\nRegisters (rev 04)\\nff:10.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon\nE5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 Thermal Control 0 (rev\n04)\\nff:10.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7\nIntegrated Memory Controller 1 Channel 0-3 ERROR Registers 0 (rev 04)\\nff:10.3 System\nperipheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller\n1 Channel 0-3 ERROR Registers 1 (rev 04)\\nff:10.6 System peripheral: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers\n2 (rev 04)\\nff:10.7 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 Integrated Memory Controller 1 Channel 0-3 ERROR Registers 3 (rev 04)\\nff:16.0\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 System Address\nDecoder (rev 04)\\nff:16.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5\nv2/Core i7 Broadcast Registers (rev 04)\\nff:16.2 System peripheral: Intel Corporation\nXeon E7 v2/Xeon E5 v2/Core i7 Broadcast Registers (rev 04)\\nff:1c.0 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 1 (rev 04)\\nff:1c.1 Performance\ncounters: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Home Agent 1 (rev 04)\\nff:1d.0\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory\nController 1 Target Address/Thermal Registers (rev 04)\\nff:1d.1 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 1 RAS\nRegisters (rev 04)\\nff:1d.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon\nE5 v2/Core i7 Integrated Memory Controller 1 Channel Target Address Decoder Registers\n(rev 04)\\nff:1d.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 Integrated Memory Controller 1 Channel Target Address Decoder Registers (rev\n04)\\nff:1d.4 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7\nIntegrated Memory Controller 1 Channel Target Address Decoder Registers (rev 04)\\nff:1d.5\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory\nController 1 Channel Target Address Decoder Registers (rev 04)\\nff:1e.0 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel\n0-3 Thermal Control 0 (rev 04)\\nff:1e.1 System peripheral: Intel Corporation Xeon\nE7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 Thermal Control\n1 (rev 04)\\nff:1e.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 Integrated Memory Controller 0 Channel 0-3 ERROR Registers 0 (rev 04)\\nff:1e.3\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory\nController 0 Channel 0-3 ERROR Registers 1 (rev 04)\\nff:1e.4 System peripheral:\nIntel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel\n0-3 Thermal Control 2 (rev 04)\\nff:1e.5 System peripheral: Intel Corporation Xeon\nE7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel 0-3 Thermal Control\n3 (rev 04)\\nff:1e.6 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core\ni7 Integrated Memory Controller 0 Channel 0-3 ERROR Registers 2 (rev 04)\\nff:1e.7\nSystem peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory\nController 0 Channel 0-3 ERROR Registers 3 (rev 04)\" {code}\n\nThe output seams to come from `lspci` system command.", "epicLinkSummary": null, "estimate": "PT0S", "externalId": "62674", "fixedVersions": ["FACT 4.0.33"], "id": "62674", "issueType": "Bug", "key": "FACT-2735", "labels": [], "originalEstimate": "PT0S", "parent": null, "parentSummary": null, "priority": "Normal", "projectDescription": "

Welcome to your project

Welcome to your project

Describe your project here

Change the project description to include details about your project.

'{quote}\nwhere bin/facter contains:\n{quote}[root@cgcldx0001 tools]# cat facter/bin/facter\n#!/usr/bin/env /usr/local/peo/tools/ruby/bin/ruby\n# frozen_string_literal: true\n#\n# This file was generated by Bundler.\n#\n# The application 'facter' is installed as part of a gem, and\n# this file is here to facilitate running it.\n#\n\nrequire \"pathname\"\nENV[\"BUNDLE_GEMFILE\"] ||= File.expand_path(\"../../Gemfile\", Pathname.new(__FILE__).realpath)\nENV['FACTERLIB']\u00a0\u00a0\u00a0\u00a0\u00a0 ||= File.expand_path(\"../../lib/facter\",Pathname.new(__FILE__).realpath)\n\n$VERBOSE=nil\n\nrequire \"rubygems\"\nrequire \"bundler/setup\"\n\n#Monkey patch canonicalize() to support camelCase fact names\nrequire 'custom_facts/util/collection'\nclass LegacyFacter::Util::Collection\n\u00a0 def canonicalize(name)\n\u00a0\u00a0\u00a0 name.to_s.to_sym\n\u00a0 end\nend\n\n\nload Gem.bin_path(\"facter\", \"facter\"){quote}", "epicLinkSummary": "How can we better interact with the community", "estimate": "PT0S", "externalId": "62640", "fixedVersions": [], "id": "62640", "issueType": "Bug", "key": "FACT-2716", "labels": [], "originalEstimate": "PT0S", "parent": "61449", "parentSummary": "How can we better interact with the community", "priority": "Normal", "projectDescription": "

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Welcome to your project

Describe your project here

Change the project description to include details about your project.

'\n\u00a0 \u00a0 \u00a0 uneven-brink.delivery.puppetlabs.net (uneven-brink.delivery.puppetlabs.net) executed in 1.91 seconds\u00a0 \u00a0 \u00a0 Exited: 1Begin teardown\nuneven-brink.delivery.puppetlabs.net (uneven-brink.delivery.puppetlabs.net) 11:49:24$ rm -rf 'C:/cygwin64/tmp/custom_dir.gfJyUw/custom_fact.rb' 'C:/cygwin64/tmp/config_dir.xcWJdH'\nuneven-brink.delivery.puppetlabs.net (uneven-brink.delivery.puppetlabs.net) executed in 0.67 secondsEnd teardowntests/options/config_file/no_custom_facts_and_custom_dir.rb passed in 9.52 seconds", "created": "2020-02-26T02:49:00.000000"}], "components": [], "created": "2019-12-05T08:35:00.000000", "creator": "623c1489a1d81f0069d8e30a", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": ["ghost"]}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@1100b45d"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "Epic Link", "fieldType": "com.pyxis.greenhopper.jira:gh-epic-link", "value": "FACT-2154"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "Method Found", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|hzzpxt:"}, {"fieldName": "Release Notes", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Not Needed"}, {"fieldName": "[CHART] Date of First Response", "fieldType": "com.atlassian.jira.ext.charting:firstresponsedate", "value": "26/Feb/20"}, {"fieldName": "[CHART] Time in Status", "fieldType": "com.atlassian.jira.ext.charting:timeinstatus", "value": "1_*:*_3_*:*_1174633550_*|*_10007_*:*_1_*:*_91161173_*|*_3_*:*_1_*:*_3376_*|*_10009_*:*_1_*:*_168986493_*|*_5_*:*_2_*:*_5370316131_*|*_10006_*:*_2_*:*_345372968"}], "epicLinkSummary": "Fix integration tests on Windows", "estimate": "PT0S", "externalId": "61362", "fixedVersions": ["FACT 4.0.8.pre"], "id": "61362", "issueType": "Bug", "key": "FACT-2181", "labels": [], "originalEstimate": "PT0S", "parent": "62296", "parentSummary": "Fix integration tests on Windows", "priority": "Normal", "projectDescription": "

Welcome to your project

Welcome to your project

Describe your project here

Change the project description to include details about your project.

", "projectKey": "FACT", "projectLead": "70121:199f31c7-67c7-42b0-b148-18ad3a391ab0", "projectName": "Facter (Archived)", "projectType": "software", "projectUrl": null, "reporter": "557058:8c0b509e-479c-4593-81d1-6310cc97cca7", "status": "Accepted", "statusCategory": "To Do", "statuscategorychangedate": "11/Mar/23 10:29 AM", "summary": "Facts passed via environment variables not parsed as array", "timeSpent": "PT0S", "updated": "2023-03-03T10:42:00.000000", "votes": "0", "watchers": []}, {"affectedVersions": [], "assignee": "623c1489a1d81f0069d8e30a", "attachments": [], "comments": [], "components": [], "created": "2019-11-25T05:24:00.000000", "creator": "623c1489a1d81f0069d8e30a", "customFieldValues": [{"fieldName": "Sub-team", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": ["ghost"]}, {"fieldName": "Approvals", "fieldType": "com.atlassian.servicedesk.approvals-plugin:sd-approvals", "value": "com.atlassian.servicedesk.plugins.approvals.internal.customfield.ApprovalsCFValue@38b7120"}, {"fieldName": "Epic/Theme", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:labels", "value": []}, {"fieldName": "Capitalized?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Yes"}, {"fieldName": "Epic Link", "fieldType": "com.pyxis.greenhopper.jira:gh-epic-link", "value": "FACT-2001"}, {"fieldName": "People Involved", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multiuserpicker", "value": []}, {"fieldName": "Flagged", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes", "value": []}, {"fieldName": "Free ?", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons", "value": "Yes"}, {"fieldName": "QA Risk Assessment", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Needs Assessment"}, {"fieldName": "Rank", "fieldType": "com.pyxis.greenhopper.jira:gh-lexo-rank", "value": "0|hzynjj:"}, {"fieldName": "Release Notes", "fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:select", "value": "Not Needed"}, {"fieldName": "[CHART] Time in Status", "fieldType": "com.atlassian.jira.ext.charting:timeinstatus", "value": "1_*:*_1_*:*_15044_*|*_3_*:*_1_*:*_246667986_*|*_10009_*:*_1_*:*_97162232_*|*_5_*:*_1_*:*_0"}], "epicLinkSummary": "Prototype 4 should include OS detection and output format similar to the C++ facter", "estimate": "PT0S", "externalId": "62958", "fixedVersions": ["v0.0.11"], "id": "62958", "issueType": "Task", "key": "FACT-2137", "labels": [], "originalEstimate": "PT0S", "parent": "62349", "parentSummary": "Prototype 4 should include OS detection and output format similar to the C++ facter", "priority": "Normal", "projectDescription": "

Welcome to your project

Describe your project here

Change the project description to include details about your project.

Welcome to your project

Welcome to your project