Jira (FACT-2988) Facter takes 20+ seconds on Windows due to azure metadata query

Gheorghe Popescu (Jira) Wed, 17 Mar 2021 00:40:08 -0700

Title: Message Title

The EC2 fact is resolved only if hypervisor is AWS.

About the AZ metadata, i think something is funky with the http client on Windows, and it does not respect the set timeouts.
The following snippet can be used to reproduce the issue:

require 'net/http'

require 'uri'

require 'benchmark'

url = "">URI.parse("http://169.254.169.254/metadata/instance?api-version=2020-09-01")

http = Net::HTTP.new(url.host, url.port)

http.read_timeout = 1

http.open_timeout = 1

p Benchmark.realtime {

  begin

    resp = http.start() { |http| http.get(url.path) }

  rescue Net::OpenTimeout => e

    puts e.message

end

Another thing, the errors are different, `Net::OpenTimeout` on Windows after 20 seconds, even though `open_timeout` is set to 5, `Errno::ENETUNREACH` on linux and the connection is closed immediately .

Add Comment

This message was sent by Atlassian Jira

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.391392.1615942373000.168081.1615966800037%40Atlassian.JIRA.

Jira (FACT-2988) Facter takes 20+ seconds on Windows due to azure metadata query

Reply via email to