Problems provisioning hosts in EC2

Support
1

Hello,

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&#39; for #&lt;Fog::Compute::AWS::Server:0x000000087ae3f8&gt;/usr/share/foreman/app/models/concerns/orchestration/compute.rb:121:inblock 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

Thanks so much for any thoughts.

Lance

2

This looks like a regression from 1.4.0 due to #2270. Please file a bug
in redmine:

http://projects.theforeman.org/projects/foreman/issues/new

··· -- Dominic Cleal Red Hat Engineering

On 07/03/14 20:20, Lance Reed wrote:

Hello,

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:inblock 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

Thanks so much for any thoughts.

Lance

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

3

Done:
http://projects.theforeman.org/issues/4616

Thanks very much for your help!

L.

··· On Monday, March 10, 2014 4:25:02 AM UTC-4, Dominic Cleal wrote: > > This looks like a regression from 1.4.0 due to #2270. Please file a bug > in redmine: > > http://projects.theforeman.org/projects/foreman/issues/new > > -- > Dominic Cleal > Red Hat Engineering > > >
4

I've added a patch to the ticket - if you have the capacity to test
it, that would be much appreciated :slight_smile:

Greg

··· On 10 March 2014 15:21, Lance Reed wrote: > Done: > http://projects.theforeman.org/issues/4616 > > Thanks very much for your help!
5

Thanks Greg!

A quick preliminary test has been successful on two attempts!
I will continue to test in more detail (I want to test public vs private etc.).
Initially this looks to work.
I can followup on the Bug itseslf with more details once I am done testing.
http://projects.theforeman.org/issues/4616

Thanks so much for the quick response and turnaround!

Cheers,

Lance

··· On Mon, Mar 10, 2014 at 12:44 PM, Greg Sutcliffe wrote: > On 10 March 2014 15:21, Lance Reed wrote: >> Done: >> http://projects.theforeman.org/issues/4616 >> >> Thanks very much for your help! > > I've added a patch to the ticket - if you have the capacity to test > it, that would be much appreciated :) > > Greg > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.
6

> Thanks Greg!
>
> A quick preliminary test has been successful on two attempts!

That's good to hear :slight_smile:

> I will continue to test in more detail (I want to test public vs private etc.).
> Initially this looks to work.
> I can followup on the Bug itseslf with more details once I am done testing.
> Bug #4616: Problems provisioning hosts in EC2 with 1.4.1-2 - Foreman
>
> Thanks so much for the quick response and turnaround!

No worries, it was me that broke it :slight_smile:

··· On 10 March 2014 17:10, Lance Reed wrote: