i3.metal instances aren’t $virtual as far as puppet is concerned, so there is a problem where facter doesn’t populate ec2_metadata on i3.metal instances as a result. If we force the facter virtual fact to be kvm, then puppet can run just fine on that instance type.
i3.metal instances aren’t {{$virtual}} as far as puppet is concerned, so there is a problem where facter doesn’t populate {{ec2_metadata}} on i3.metal instances as a result. If we force the facter {{virtual}} fact to be kvm, then puppet can run just fine on that instance type.
Looks like the fix for us would be to roll forward then:
mckern ~ $ dpkg -l | grep puppet
ii puppet-agent 1.8.3-1jessie amd64 The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective.
Sorry about that Ryan McKern. Facter (& co) ownership was transferred to our team sometime last year, and this ticket seems to have slipped through the cracks of JIRA.