Jira (FACT-3127) EC2 Metadata Broken with Facter 2.5.4 - Works Fine in 2.5.1

[Grave Digga (Jira)]

Grave Digga created an issue

Facter / FACT-3127 EC2 Metadata Broken with Facter 2.5.4 - Works Fine in 2.5.1 Issue Type: Bug Affects Versions: FACT 4.2.5 Assignee: Mihai Buzgau Components: CLI, Community Created: 2022/06/17 12:44 AM Environment: Mozilla/5.0 (iPhone; CPU iPhone OS 15_5 like Mac OS X) AppleWebKit/605.1.15 (k html, like Gecko) Version/15.5 Mobile/15E148 Safari/604.1 Fix Versions: FACT 3.14.22 Priority: Critical Reporter: Grave Digga Facter at version 2.5.4 can no longer read and display facts from EC2 Metadata in AWS.  This has been breaking our puppet runs across Puppet and Dev environments, as on bootstrap we're automatically pulling the latest in the 2.x series.    Facter @ 2.5.4 [root@ip-10-3-2-87 log]# facter | grep ec2 serialnumber => ec23a2bd-0a32-7111-8ee9-ecd6038d22d0 Facter @ 2.5.1 [root@ip-10-3-2-85 vkumase]# facter | grep ec2   domain => ec2.internal   ec2_ami_id => ami-923b64e8   ec2_ami_launch_index => 0   ec2_ami_manifest_path => (unknown)   ec2_block_device_mapping_ami => /dev/xvda   ec2_block_device_mapping_ebs1 => xvdcz   ec2_block_device_mapping_root => /dev/xvda   ec2_events_maintenance_history => []   ec2_events_maintenance_scheduled => []   ec2_hostname => ip-10-3-2-85   ec2_iam_info_0 => {   ec2_iam_info_1 =>   "Code" : "Success",   ec2_iam_info_2 =>   "LastUpdated" : "2019-07-17T15:54:48Z", This will break all Puppet modules that are using EC2 metadata as a fact in older puppet installations.  Add Comment

This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)