[FACT-1936] facter -p segfaults with facts that call open-uri.open Created: 2019/07/11 Updated: 2019/09/12 Resolved: 2019/08/12
|Affects Version/s:||FACT 3.12.5, FACT 3.13.3, FACT 3.14.2|
|Fix Version/s:||FACT 3.12.z, FACT 3.13.z|
|Reporter:||Thomas Kishel||Assignee:||Gabriel Nagy|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Sprint:||NW - 2019-08-07, NW - 2019-08-21|
|Method Found:||Needs Assessment|
|Release Notes:||Not Needed|
|Release Notes Summary:|| Ruby versions starting with 2.5 have changed how the Windows sockets are started, requiring a call to an additional function for starting them.
Not having this call causes segmentation faults when querying custom facts that use Windows Sockets with Ruby versions 2.5 and higher (i.e. custom facts that make HTTP requests).
|QA Risk Assessment:||Needs Assessment|
Puppet Version: 6.0.9
This custom fact succeeds on Linux but segfaults on Windows ... but only when calling facter -p not with puppet facts or puppet agent -t
(Same segfault occurs if you use Net::HTTP.get(URI.parse('https://api.ipify.org?format=json')) instead of open(url).read)
|Comment by Jean Bond [ 2019/09/11 ]|
I just happened upon this ticket while researching another one; can anyone let me know what version of Facter this went into? No release note has been published for it because there isn't a specific fix version on it.
|Comment by Gabriel Nagy [ 2019/09/12 ]|
Jean Bond the investigation for this ticket was done on Facter, but the fix was actually on a different project (Leatherman /
|Comment by Jean Bond [ 2019/09/12 ]|
Fair enough Gabriel Nagy. It's my mistake anyway, because the docs tab clearly says "not needed". Apologies for the noise!