Uploaded image for project: 'Facter'
  1. Facter
  2. FACT-1268

ec2 facter timeout of 200 milliseconds is too short

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: FACT 3.7.0
    • Component/s: None
    • Environment:

      amazon aws

    • Template:
    • Team:
      Dumpling
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Timeout for retrieving ec2 facts has been increased from 200ms to 600ms.

      Description

      After stepping up to facter 3 we see the ec2_resolver regularly timing out:

      (Facter) Connection timed out after 200 milliseconds
      (Facter) Closing connection 47
      (Facter) EC2 metadata request failed: Timeout was reached
      

      This happens most of the time when the instance is booting/provisioning itself for the first time.

      We never saw this in version 2 of facter as the time-out of 0.2 seconds was only used for testing reachability to the meta data server and that was even retried 3 times before it failed.

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Unassigned
                Reporter:
                steven.aerts Steven Aerts
              • Votes:
                1 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: