Foreman 1.4.1 problem provisioning micro instance AWS

Support
1

'm having trouble provisioning instances in the Amazon VPC with foreman.

After connecting to the foreman aws, create the OS (Ubuntu LTS 12.04.03),
and configure the x64 architectures.

I created the image using the default ubuntu aim: ami-59a4a230
http://cloud-images.ubuntu.com/releases/precise/release/

Time when creating an instance happens the error below:

Completed 200 OK in 12.2ms (Views: 3.0ms | ActiveRecord: 1.3ms)
Rolling back due to a problem: Set up compute instance
rrrrrr.domain.amazon 2 failed rrrrrr.domain.amazonsetCompute
Failed to save:

2

Are you getting those messages in production.log?
Does foreman fail to create the instance nearly immediately after you click
submit?

I ask because it sounds like the same problem I have creating instances on
Google Compute Engine using foreman

··· On Wednesday, February 26, 2014 3:46:16 AM UTC, Eduardo Terzella wrote: > > 'm having trouble provisioning instances in the Amazon VPC with foreman. > > After connecting to the foreman aws, create the OS (Ubuntu LTS 12.04.03), > and configure the x64 architectures. > > I created the image using the default ubuntu aim: ami-59a4a230 > http://cloud-images.ubuntu.com/releases/precise/release/ > > Time when creating an instance happens the error below: > > Completed 200 OK in 12.2ms (Views: 3.0ms | ActiveRecord: 1.3ms) > *Rolling back due to a problem: Set up compute instance > rrrrrr.domain.amazon 2 failed rrrrrr.domain.amazonsetCompute* > Failed to save: >
3

These must be different issues, Foreman orchestrates lot's of things
during host creation and if anything fails, it rolls back.

Are there any more details like ruby stacktrace in logs? This says
really nothing.

LZ

··· > > Completed 200 OK in 12.2ms (Views: 3.0ms | ActiveRecord: 1.3ms) > > *Rolling back due to a problem: Set up compute instance > > rrrrrr.domain.amazon 2 failed rrrrrr.domain.amazonsetCompute* > > Failed to save: -- Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

4

Are there particular logs in which those ruby stacktraces should be stored
in?

··· On Wednesday, February 26, 2014 2:21:23 PM UTC, Lukas Zapletal wrote: > > These must be different issues, Foreman orchestrates lot's of things > during host creation and if anything fails, it rolls back. > > Are there any more details like ruby stacktrace in logs? This says > really nothing. > > LZ > > > > Completed 200 OK in 12.2ms (Views: 3.0ms | ActiveRecord: 1.3ms) > > > *Rolling back due to a problem: Set up compute instance > > > rrrrrr.domain.amazon 2 failed > rrrrrr.domain.amazonsetCompute* > > > Failed to save: > -- > Later, > > Lukas "lzap" Zapletal > irc: lzap #theforeman >
5

> Are there particular logs in which those ruby stacktraces should be stored
> in?

If you don't see any details bellow this line:

> > > > Rolling back due to a problem: Set up compute instance
> > > > rrrrrr.domain.amazon 2 failed
> > rrrrrr.domain.amazonsetCompute

Than it's a bug, we should show all important exceptions in the
production.log :frowning:

I have no GCE instance to test against, someone else?

··· -- Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman