Dominic Cleal said that I should file a bug for the bellow issue and that it looks like a regression from 1.4.0 due to #2270.

I am doing a test setup of Foreman 1.4.1-2 in EC2.

I am getting the following error when attempting to provision a new EC2 host.

Failed to get IP for grrr.ec2.internal: undefined method `public_ip_addresses' for #<Fog::Compute::AWS::Server:0x000000087ae3f8>

I am unclear how Foreman gets the IP address in this case, but this looks like it may be a code problem.

Logs have:
Adding Compute instance for grrr.ec2.internal

waiting for instance to acquire ip address
Failed to get IP for grrr.ec2.internal: undefined method `public_ip_addresses' for #<Fog::Compute::AWS::Server:0x000000087ae3f8>/usr/share/foreman/app/models/concerns/orchestration/compute.rb:121:in `block in setComputeIP'

RELEASE: CentOS release 6.4 (Final)
  FOREMAN: 1.4.1
     RUBY: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
   PUPPET: 3.4.3

foreman-debug-mcDIR.tar.xz

CODE:
foreman-selinux-1.4.0-1.el6.noarch
foreman-compute-1.4.1-2.el6.noarch
foreman-release-1.4.1-2.el6.noarch
foreman-proxy-1.4.1-1.el6.noarch
foreman-postgresql-1.4.1-2.el6.noarch
ruby193-rubygem-fog-1.19.0-1.el6.noarch
rubygem-hammer_cli_foreman-0.0.18-1.el6.noarch
rubygem-foreman_api-0.1.11-1.el6.noarch
foreman-installer-1.4.1-1.el6.noarch
foreman-1.4.1-2.el6.noarch
foreman-cli-1.4.1-2.el6.noarch