Problem provisioning EC2 instance

I'm very new to Foreman and have spent the last couple of days setting it
up and playing around with the interface. I like what I've found so far,
and I'm looking forward to integrating it into our processes.

However, I have run into a blocker. I've installed AWS as a compute
resource and I'm trying to create host in EC2. I've filled out all the
pertinent info, except I can't select an operating system from the drop
down list. In Provisioning -> Operating Systems I have Ubuntu 12.04 in the
list, as I've configured the EC2 ENC script and have registered an EC2
instance with Foreman, so there is an operating system there. I also
tried creating another operating system also called Ubuntu 12.04, but the
New Host page still didn't have any operating systems listed.
Unfortunately, I'm unable to to provision a new host because it tells me I
require an operating system.

One other issue is that it tells me I need a provisioning template assigned
in order to create the node. However, I did create a finish template and
assigned it to the host group to which I'm assigning this new node. I also
linked the same template to the Ubuntu 12.03 operating system that is
configured in Foreman, yet on the operating system page on the new host
form, when I click "resolve" next to provisioning templates, it tells me no
templates are configured.

As I said I'm really new to this so I may have missed something obvious.
Can anyone point me in the right direction here?

Kind regards,
Guy

Hello Guy

did you associate the template in the Association tab?

Jim

··· On 14 June 2013 00:20, Guy Knights wrote:

I’m very new to Foreman and have spent the last couple of days setting it
up and playing around with the interface. I like what I’ve found so far,
and I’m looking forward to integrating it into our processes.

However, I have run into a blocker. I’ve installed AWS as a compute
resource and I’m trying to create host in EC2. I’ve filled out all the
pertinent info, except I can’t select an operating system from the drop
down list. In Provisioning -> Operating Systems I have Ubuntu 12.04 in the
list, as I’ve configured the EC2 ENC script and have registered an EC2
instance with Foreman, so there is an operating system there. I also
tried creating another operating system also called Ubuntu 12.04, but the
New Host page still didn’t have any operating systems listed.
Unfortunately, I’m unable to to provision a new host because it tells me I
require an operating system.

One other issue is that it tells me I need a provisioning template
assigned in order to create the node. However, I did create a finish
template and assigned it to the host group to which I’m assigning this new
node. I also linked the same template to the Ubuntu 12.03 operating system
that is configured in Foreman, yet on the operating system page on the new
host form, when I click “resolve” next to provisioning templates, it tells
me no templates are configured.

As I said I’m really new to this so I may have missed something obvious.
Can anyone point me in the right direction here?

Kind regards,
Guy


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/groups/opt_out.

Hi Jim,

Yes, the template is associated with both an operating system and with a
hostgroup and environment.

Thanks,
Guy

··· On Friday, 14 June 2013 02:01:29 UTC-7, Paradoxbound wrote: > > Hello Guy > > did you associate the template in the Association tab? > > Jim > > > On 14 June 2013 00:20, Guy Knights <g...@eastsidegamestudio.com > > wrote: > >> I'm very new to Foreman and have spent the last couple of days setting it >> up and playing around with the interface. I like what I've found so far, >> and I'm looking forward to integrating it into our processes. >> >> However, I have run into a blocker. I've installed AWS as a compute >> resource and I'm trying to create host in EC2. I've filled out all the >> pertinent info, except I can't select an operating system from the drop >> down list. In Provisioning -> Operating Systems I have Ubuntu 12.04 in the >> list, as I've configured the EC2 ENC script and have registered an EC2 >> instance with Foreman, so there *is* an operating system there. I also >> tried creating another operating system also called Ubuntu 12.04, but the >> New Host page still didn't have any operating systems listed. >> Unfortunately, I'm unable to to provision a new host because it tells me I >> require an operating system. >> >> One other issue is that it tells me I need a provisioning template >> assigned in order to create the node. However, I did create a finish >> template and assigned it to the host group to which I'm assigning this new >> node. I also linked the same template to the Ubuntu 12.03 operating system >> that is configured in Foreman, yet on the operating system page on the new >> host form, when I click "resolve" next to provisioning templates, it tells >> me no templates are configured. >> >> As I said I'm really new to this so I may have missed something obvious. >> Can anyone point me in the right direction here? >> >> Kind regards, >> Guy >> >> -- >> 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-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >

Hi Guy,

If you re-edit your operating system and go to the final tab, is there a
default template set there, or is the combobox blank?

Regards,
Greg

Hi Greg,

Yep, the template I want to apply is set there as "final".

Guy

··· On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote: > > Hi Guy, > > If you re-edit your operating system and go to the final tab, is there a > default template set there, or is the combobox blank? > > Regards, > Greg >

Just bumping this to see if it brings any new suggestions as I haven't been
able to resolve it yet.

··· On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote: > > Hi Greg, > > Yep, the template I want to apply is set there as "final". > > Guy > > On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote: >> >> Hi Guy, >> >> If you re-edit your operating system and go to the final tab, is there a >> default template set there, or is the combobox blank? >> >> Regards, >> Greg >> >

I will be adding some more AWS accounts to our 1.1 Foreman install today. I
will try and capture as much of the process for you as I can and build a
couple of test instances. I basically bumbled through Ohad's blog post and
it eventually worked.

Jim

··· On 20 June 2013 01:23, Guy Knights wrote:

Just bumping this to see if it brings any new suggestions as I haven’t
been able to resolve it yet.

On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote:

Hi Greg,

Yep, the template I want to apply is set there as “final”.

Guy

On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote:

Hi Guy,

If you re-edit your operating system and go to the final tab, is there a
default template set there, or is the combobox blank?

Regards,
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/groups/opt_out.

That would be really helpful, thanks Jim.

··· On Thursday, 20 June 2013 00:43:33 UTC-7, Paradoxbound wrote: > > I will be adding some more AWS accounts to our 1.1 Foreman install today. > I will try and capture as much of the process for you as I can and build a > couple of test instances. I basically bumbled through Ohad's blog post and > it eventually worked. > > Jim > > > On 20 June 2013 01:23, Guy Knights <g...@eastsidegamestudio.com > > wrote: > >> Just bumping this to see if it brings any new suggestions as I haven't >> been able to resolve it yet. >> >> >> On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote: >>> >>> Hi Greg, >>> >>> Yep, the template I want to apply is set there as "final". >>> >>> Guy >>> >>> On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote: >>>> >>>> Hi Guy, >>>> >>>> If you re-edit your operating system and go to the final tab, is there >>>> a default template set there, or is the combobox blank? >>>> >>>> Regards, >>>> 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-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >

I worked out what the problem was here. I had to edit the operating system
in Foreman and set the architecture to x86_64. Once I did that, I was able
to select an operating system after selecting an architecture in the new
host provisioning form.

I did run into another issue though; once I went through and provisioned a
new host, the Foreman page hung after I hit submit. I left it for about a
minute and eventually closed the page and restarted the web server.
However, I checked the EC2 console and the new instance had been created so
I'm not sure what happened. Any ideas?

··· On Thursday, 20 June 2013 16:13:32 UTC-7, Guy Knights wrote: > > That would be really helpful, thanks Jim. > > On Thursday, 20 June 2013 00:43:33 UTC-7, Paradoxbound wrote: >> >> I will be adding some more AWS accounts to our 1.1 Foreman install today. >> I will try and capture as much of the process for you as I can and build a >> couple of test instances. I basically bumbled through Ohad's blog post and >> it eventually worked. >> >> Jim >> >> >> On 20 June 2013 01:23, Guy Knights wrote: >> >>> Just bumping this to see if it brings any new suggestions as I haven't >>> been able to resolve it yet. >>> >>> >>> On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote: >>>> >>>> Hi Greg, >>>> >>>> Yep, the template I want to apply is set there as "final". >>>> >>>> Guy >>>> >>>> On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote: >>>>> >>>>> Hi Guy, >>>>> >>>>> If you re-edit your operating system and go to the final tab, is there >>>>> a default template set there, or is the combobox blank? >>>>> >>>>> Regards, >>>>> 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-user...@googlegroups.com. >>> To post to this group, send email to forema...@googlegroups.com. >>> Visit this group at http://groups.google.com/group/foreman-users. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >>

> I worked out what the problem was here. I had to edit the operating system
> in Foreman and set the architecture to x86_64. Once I did that, I was able
> to select an operating system after selecting an architecture in the new
> host provisioning form.
>
> I did run into another issue though; once I went through and provisioned a
> new host, the Foreman page hung after I hit submit. I left it for about a
> minute and eventually closed the page and restarted the web server.
> However, I checked the EC2 console and the new instance had been created so
> I'm not sure what happened. Any ideas?
>

are you using webrick? the progress bar only works if you have something
that can server multiple foreman connections (such as passenger).

Ohad

··· On Wed, Jun 26, 2013 at 3:49 AM, Guy Knights wrote:

On Thursday, 20 June 2013 16:13:32 UTC-7, Guy Knights wrote:

That would be really helpful, thanks Jim.

On Thursday, 20 June 2013 00:43:33 UTC-7, Paradoxbound wrote:

I will be adding some more AWS accounts to our 1.1 Foreman install
today. I will try and capture as much of the process for you as I can and
build a couple of test instances. I basically bumbled through Ohad’s blog
post and it eventually worked.

Jim

On 20 June 2013 01:23, Guy Knights g...@eastsidegamestudio.com wrote:

Just bumping this to see if it brings any new suggestions as I haven’t
been able to resolve it yet.

On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote:

Hi Greg,

Yep, the template I want to apply is set there as “final”.

Guy

On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote:

Hi Guy,

If you re-edit your operating system and go to the final tab, is
there a default template set there, or is the combobox blank?

Regards,
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-user…@googlegroups.**com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/**group/foreman-usershttp://groups.google.com/group/foreman-users
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.


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/groups/opt_out.

No, I'm using passenger. It's not like the progress bar just doesn't show,
the entire page hangs (submit button is depressed, "working" cursor icon is
displayed) until I restart the web server. I can't even close the page and
reopen it as it just hangs. The server does get provisioned pretty much
straight away though.

··· On Wednesday, 26 June 2013 00:00:25 UTC-7, ohad wrote: > > > > On Wed, Jun 26, 2013 at 3:49 AM, Guy Knights <g...@eastsidegamestudio.com > > wrote: > >> I worked out what the problem was here. I had to edit the operating >> system in Foreman and set the architecture to x86_64. Once I did that, I >> was able to select an operating system after selecting an architecture in >> the new host provisioning form. >> >> I did run into another issue though; once I went through and provisioned >> a new host, the Foreman page hung after I hit submit. I left it for about a >> minute and eventually closed the page and restarted the web server. >> However, I checked the EC2 console and the new instance had been created so >> I'm not sure what happened. Any ideas? >> > > are you using webrick? the progress bar only works if you have something > that can server multiple foreman connections (such as passenger). > > Ohad > >> >> On Thursday, 20 June 2013 16:13:32 UTC-7, Guy Knights wrote: >>> >>> That would be really helpful, thanks Jim. >>> >>> On Thursday, 20 June 2013 00:43:33 UTC-7, Paradoxbound wrote: >>>> >>>> I will be adding some more AWS accounts to our 1.1 Foreman install >>>> today. I will try and capture as much of the process for you as I can and >>>> build a couple of test instances. I basically bumbled through Ohad's blog >>>> post and it eventually worked. >>>> >>>> Jim >>>> >>>> >>>> On 20 June 2013 01:23, Guy Knights wrote: >>>> >>>>> Just bumping this to see if it brings any new suggestions as I haven't >>>>> been able to resolve it yet. >>>>> >>>>> >>>>> On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote: >>>>>> >>>>>> Hi Greg, >>>>>> >>>>>> Yep, the template I want to apply is set there as "final". >>>>>> >>>>>> Guy >>>>>> >>>>>> On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote: >>>>>>> >>>>>>> Hi Guy, >>>>>>> >>>>>>> If you re-edit your operating system and go to the final tab, is >>>>>>> there a default template set there, or is the combobox blank? >>>>>>> >>>>>>> Regards, >>>>>>> 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-user...@googlegroups.**com. >>>>> To post to this group, send email to forema...@googlegroups.com. >>>>> Visit this group at http://groups.google.com/**group/foreman-users >>>>> . >>>>> For more options, visit https://groups.google.com/**groups/opt_out >>>>> . >>>>> >>>>> >>>>> >>>> >>>> -- >> 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-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >

> No, I'm using passenger. It's not like the progress bar just doesn't show,
> the entire page hangs (submit button is depressed, "working" cursor icon is
> displayed) until I restart the web server. I can't even close the page and
> reopen it as it just hangs. The server does get provisioned pretty much
> straight away though.

Do you see anything your apache logs? (or error logs).

Is this 1.1? can you try again with 1.2?

thanks,
Ohad

··· On Wed, Jun 26, 2013 at 8:02 PM, Guy Knights wrote:

On Wednesday, 26 June 2013 00:00:25 UTC-7, ohad wrote:

On Wed, Jun 26, 2013 at 3:49 AM, Guy Knights <g...@eastsidegamestudio.com >> > wrote:

I worked out what the problem was here. I had to edit the operating
system in Foreman and set the architecture to x86_64. Once I did that, I
was able to select an operating system after selecting an architecture in
the new host provisioning form.

I did run into another issue though; once I went through and provisioned
a new host, the Foreman page hung after I hit submit. I left it for about a
minute and eventually closed the page and restarted the web server.
However, I checked the EC2 console and the new instance had been created so
I’m not sure what happened. Any ideas?

are you using webrick? the progress bar only works if you have something
that can server multiple foreman connections (such as passenger).

Ohad

On Thursday, 20 June 2013 16:13:32 UTC-7, Guy Knights wrote:

That would be really helpful, thanks Jim.

On Thursday, 20 June 2013 00:43:33 UTC-7, Paradoxbound wrote:

I will be adding some more AWS accounts to our 1.1 Foreman install
today. I will try and capture as much of the process for you as I can and
build a couple of test instances. I basically bumbled through Ohad’s blog
post and it eventually worked.

Jim

On 20 June 2013 01:23, Guy Knights g...@eastsidegamestudio.comwrote:

Just bumping this to see if it brings any new suggestions as I
haven’t been able to resolve it yet.

On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote:

Hi Greg,

Yep, the template I want to apply is set there as “final”.

Guy

On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote:

Hi Guy,

If you re-edit your operating system and go to the final tab, is
there a default template set there, or is the combobox blank?

Regards,
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-user…@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-usershttp://groups.google.com/group/foreman-users
.
For more options, visit https://groups.google.com/groups/opt_outhttps://groups.google.com/groups/opt_out
.


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-user…@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com
.
Visit this group at http://groups.google.com/**group/foreman-usershttp://groups.google.com/group/foreman-users
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.


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/groups/opt_out.

It is, actually. I'll give 1.2 a go and see if that changes things.

Thanks Ohad

··· On Wednesday, 26 June 2013 12:19:52 UTC-7, ohad wrote: > > > > On Wed, Jun 26, 2013 at 8:02 PM, Guy Knights <g...@eastsidegamestudio.com > > wrote: > >> No, I'm using passenger. It's not like the progress bar just doesn't >> show, the entire page hangs (submit button is depressed, "working" cursor >> icon is displayed) until I restart the web server. I can't even close the >> page and reopen it as it just hangs. The server does get provisioned pretty >> much straight away though. > > > Do you see anything your apache logs? (or error logs). > > Is this 1.1? can you try again with 1.2? > > thanks, > Ohad > >> >> On Wednesday, 26 June 2013 00:00:25 UTC-7, ohad wrote: >> >>> >>> >>> On Wed, Jun 26, 2013 at 3:49 AM, Guy Knights < >>> g...@eastsidegamestudio.com> wrote: >>> >>>> I worked out what the problem was here. I had to edit the operating >>>> system in Foreman and set the architecture to x86_64. Once I did that, I >>>> was able to select an operating system after selecting an architecture in >>>> the new host provisioning form. >>>> >>>> I did run into another issue though; once I went through and >>>> provisioned a new host, the Foreman page hung after I hit submit. I left it >>>> for about a minute and eventually closed the page and restarted the web >>>> server. However, I checked the EC2 console and the new instance had been >>>> created so I'm not sure what happened. Any ideas? >>>> >>> >>> are you using webrick? the progress bar only works if you have something >>> that can server multiple foreman connections (such as passenger). >>> >>> Ohad >>> >>>> >>>> On Thursday, 20 June 2013 16:13:32 UTC-7, Guy Knights wrote: >>>>> >>>>> That would be really helpful, thanks Jim. >>>>> >>>>> On Thursday, 20 June 2013 00:43:33 UTC-7, Paradoxbound wrote: >>>>>> >>>>>> I will be adding some more AWS accounts to our 1.1 Foreman install >>>>>> today. I will try and capture as much of the process for you as I can and >>>>>> build a couple of test instances. I basically bumbled through Ohad's blog >>>>>> post and it eventually worked. >>>>>> >>>>>> Jim >>>>>> >>>>>> >>>>>> On 20 June 2013 01:23, Guy Knights wrote: >>>>>> >>>>>>> Just bumping this to see if it brings any new suggestions as I >>>>>>> haven't been able to resolve it yet. >>>>>>> >>>>>>> >>>>>>> On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote: >>>>>>>> >>>>>>>> Hi Greg, >>>>>>>> >>>>>>>> Yep, the template I want to apply is set there as "final". >>>>>>>> >>>>>>>> Guy >>>>>>>> >>>>>>>> On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote: >>>>>>>>> >>>>>>>>> Hi Guy, >>>>>>>>> >>>>>>>>> If you re-edit your operating system and go to the final tab, is >>>>>>>>> there a default template set there, or is the combobox blank? >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> 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-user...@googlegroups.**c**om. >>>>>>> To post to this group, send email to forema...@googlegroups.com. >>>>>>> Visit this group at http://groups.google.com/**group**/foreman-users >>>>>>> . >>>>>>> For more options, visit https://groups.google.com/**grou**ps/opt_out >>>>>>> . >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>> 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-user...@**googlegroups.com. >>>> To post to this group, send email to forema...@googlegroups.com**. >>>> Visit this group at http://groups.google.com/**group/foreman-users >>>> . >>>> For more options, visit https://groups.google.com/**groups/opt_out >>>> . >>>> >>>> >>>> >>> >>> -- >> 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-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >

Actually, I haven't yet upgraded to 1.2 as I did some further investigation
and set the logging mode to debug in foreman-proxy/settings.yaml. I'm now
getting some more info when I try to provision a new node. In the foreman
production.log, I gets to a point where it keeps outputting the following
text into the log, over and over:

Started GET "/tasks/07773504-c911-413e-9730-6bb63e6154e3" for
184.71.162.106 at Fri Jun 28 17:26:13 +0000 2013
Processing by TasksController#show as
Parameters: {"id"=>"07773504-c911-413e-9730-6bb63e6154e3"}
User Load (0.4ms) SELECT "users".* FROM "users" WHERE "users"."id" = 1
LIMIT 1
Setting current user thread-local variable to admin
Rendered tasks/_list.rhtml (0.8ms)
Completed 200 OK in 4ms (Views: 1.4ms | ActiveRecord: 0.7ms)

This corresponds to a progress bar on the web gui, which I had either never
noticed before or hadn't been showing up before. It appears above the new
host provisioning form, and gets to "running - Waiting for <instance name>
to come online" where it just hangs (see attached screenshot). Even after I
see that the instance is "running" in the AWS console, this progress bar
doesn't change, and the text block above just continually keeps getting
output to the log file.

So that being the case, does this indicate where the problem might lie?

Thanks,
Guy

··· On Wednesday, 26 June 2013 12:21:36 UTC-7, Guy Knights wrote: > > It is, actually. I'll give 1.2 a go and see if that changes things. > > Thanks Ohad > > On Wednesday, 26 June 2013 12:19:52 UTC-7, ohad wrote: >> >> >> >> On Wed, Jun 26, 2013 at 8:02 PM, Guy Knights > > wrote: >> >>> No, I'm using passenger. It's not like the progress bar just doesn't >>> show, the entire page hangs (submit button is depressed, "working" cursor >>> icon is displayed) until I restart the web server. I can't even close the >>> page and reopen it as it just hangs. The server does get provisioned pretty >>> much straight away though. >> >> >> Do you see anything your apache logs? (or error logs). >> >> Is this 1.1? can you try again with 1.2? >> >> thanks, >> Ohad >> >>> >>> On Wednesday, 26 June 2013 00:00:25 UTC-7, ohad wrote: >>> >>>> >>>> >>>> On Wed, Jun 26, 2013 at 3:49 AM, Guy Knights < >>>> g...@eastsidegamestudio.com> wrote: >>>> >>>>> I worked out what the problem was here. I had to edit the operating >>>>> system in Foreman and set the architecture to x86_64. Once I did that, I >>>>> was able to select an operating system after selecting an architecture in >>>>> the new host provisioning form. >>>>> >>>>> I did run into another issue though; once I went through and >>>>> provisioned a new host, the Foreman page hung after I hit submit. I left it >>>>> for about a minute and eventually closed the page and restarted the web >>>>> server. However, I checked the EC2 console and the new instance had been >>>>> created so I'm not sure what happened. Any ideas? >>>>> >>>> >>>> are you using webrick? the progress bar only works if you have >>>> something that can server multiple foreman connections (such as passenger). >>>> >>>> Ohad >>>> >>>>> >>>>> On Thursday, 20 June 2013 16:13:32 UTC-7, Guy Knights wrote: >>>>>> >>>>>> That would be really helpful, thanks Jim. >>>>>> >>>>>> On Thursday, 20 June 2013 00:43:33 UTC-7, Paradoxbound wrote: >>>>>>> >>>>>>> I will be adding some more AWS accounts to our 1.1 Foreman install >>>>>>> today. I will try and capture as much of the process for you as I can and >>>>>>> build a couple of test instances. I basically bumbled through Ohad's blog >>>>>>> post and it eventually worked. >>>>>>> >>>>>>> Jim >>>>>>> >>>>>>> >>>>>>> On 20 June 2013 01:23, Guy Knights wrote: >>>>>>> >>>>>>>> Just bumping this to see if it brings any new suggestions as I >>>>>>>> haven't been able to resolve it yet. >>>>>>>> >>>>>>>> >>>>>>>> On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote: >>>>>>>>> >>>>>>>>> Hi Greg, >>>>>>>>> >>>>>>>>> Yep, the template I want to apply is set there as "final". >>>>>>>>> >>>>>>>>> Guy >>>>>>>>> >>>>>>>>> On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote: >>>>>>>>>> >>>>>>>>>> Hi Guy, >>>>>>>>>> >>>>>>>>>> If you re-edit your operating system and go to the final tab, is >>>>>>>>>> there a default template set there, or is the combobox blank? >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> 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-user...@googlegroups.**c**om. >>>>>>>> To post to this group, send email to forema...@googlegroups.com. >>>>>>>> Visit this group at http://groups.google.com/**group** >>>>>>>> /foreman-users . >>>>>>>> For more options, visit https://groups.google.com/**grou** >>>>>>>> ps/opt_out . >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>> 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-user...@**googlegroups.com. >>>>> To post to this group, send email to forema...@googlegroups.com**. >>>>> Visit this group at http://groups.google.com/**group/foreman-users >>>>> . >>>>> For more options, visit https://groups.google.com/**groups/opt_out >>>>> . >>>>> >>>>> >>>>> >>>> >>>> -- >>> 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-user...@googlegroups.com. >>> To post to this group, send email to forema...@googlegroups.com. >>> Visit this group at http://groups.google.com/group/foreman-users. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >>

> Actually, I haven't yet upgraded to 1.2 as I did some further
> investigation and set the logging mode to debug in
> foreman-proxy/settings.yaml. I'm now getting some more info when I try to
> provision a new node. In the foreman production.log, I gets to a point
> where it keeps outputting the following text into the log, over and over:
>
> Started GET "/tasks/07773504-c911-413e-9730-6bb63e6154e3" for
> 184.71.162.106 at Fri Jun 28 17:26:13 +0000 2013
> Processing by TasksController#show as
> Parameters: {"id"=>"07773504-c911-413e-9730-6bb63e6154e3"}
> User Load (0.4ms) SELECT "users".* FROM "users" WHERE "users"."id" = 1
> LIMIT 1
> Setting current user thread-local variable to admin
> Rendered tasks/_list.rhtml (0.8ms)
> Completed 200 OK in 4ms (Views: 1.4ms | ActiveRecord: 0.7ms)
>
> This corresponds to a progress bar on the web gui, which I had either
> never noticed before or hadn't been showing up before. It appears above the
> new host provisioning form, and gets to "running - Waiting for <instance
> > to come online" where it just hangs (see attached screenshot). Even
> after I see that the instance is "running" in the AWS console, this
> progress bar doesn't change, and the text block above just continually
> keeps getting output to the log file.
>
> So that being the case, does this indicate where the problem might lie?
>
I see… I assume you are running foreman inside EC2, or that at least the
public ip address is not reachable by foreman?

Ohad

··· On Fri, Jun 28, 2013 at 8:35 PM, Guy Knights wrote:

Thanks,
Guy

On Wednesday, 26 June 2013 12:21:36 UTC-7, Guy Knights wrote:

It is, actually. I’ll give 1.2 a go and see if that changes things.

Thanks Ohad

On Wednesday, 26 June 2013 12:19:52 UTC-7, ohad wrote:

On Wed, Jun 26, 2013 at 8:02 PM, Guy Knights < >>> g...@eastsidegamestudio.com> wrote:

No, I’m using passenger. It’s not like the progress bar just doesn’t
show, the entire page hangs (submit button is depressed, “working” cursor
icon is displayed) until I restart the web server. I can’t even close the
page and reopen it as it just hangs. The server does get provisioned pretty
much straight away though.

Do you see anything your apache logs? (or error logs).

Is this 1.1? can you try again with 1.2?

thanks,
Ohad

On Wednesday, 26 June 2013 00:00:25 UTC-7, ohad wrote:

On Wed, Jun 26, 2013 at 3:49 AM, Guy Knights < >>>>> g...@eastsidegamestudio.com> wrote:

I worked out what the problem was here. I had to edit the operating
system in Foreman and set the architecture to x86_64. Once I did that, I
was able to select an operating system after selecting an architecture in
the new host provisioning form.

I did run into another issue though; once I went through and
provisioned a new host, the Foreman page hung after I hit submit. I left it
for about a minute and eventually closed the page and restarted the web
server. However, I checked the EC2 console and the new instance had been
created so I’m not sure what happened. Any ideas?

are you using webrick? the progress bar only works if you have
something that can server multiple foreman connections (such as passenger).

Ohad

On Thursday, 20 June 2013 16:13:32 UTC-7, Guy Knights wrote:

That would be really helpful, thanks Jim.

On Thursday, 20 June 2013 00:43:33 UTC-7, Paradoxbound wrote:

I will be adding some more AWS accounts to our 1.1 Foreman install
today. I will try and capture as much of the process for you as I can and
build a couple of test instances. I basically bumbled through Ohad’s blog
post and it eventually worked.

Jim

On 20 June 2013 01:23, Guy Knights g...@eastsidegamestudio.comwrote:

Just bumping this to see if it brings any new suggestions as I
haven’t been able to resolve it yet.

On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote:

Hi Greg,

Yep, the template I want to apply is set there as “final”.

Guy

On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote:

Hi Guy,

If you re-edit your operating system and go to the final tab, is
there a default template set there, or is the combobox blank?

Regards,
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-user…@googlegroups.**com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group

/foreman-users http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/grou

ps/opt_out https://groups.google.com/groups/opt_out.


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-user…@**googlegroups.com.
To post to this group, send email to forema...@googlegroups.com
.
Visit this group at http://groups.google.com/group/foreman-usershttp://groups.google.com/group/foreman-users
.
For more options, visit https://groups.google.com/groups/opt_outhttps://groups.google.com/groups/opt_out
.


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-user…@googlegroups.**com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/**group/foreman-usershttp://groups.google.com/group/foreman-users
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.


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/groups/opt_out.

Yes, my Foreman instance is running from within EC2. It's part of the
default security group, and every instance I've been trying to create is
also a member of the default security group so theoretically the foreman
server should be able contact these new instances.

Just out of interest, what exactly is happening at this point? Is the
foreman server trying to connect via SSH? It doesn't appear so, according
to the screenshot I attached, but I was curious as I don't think it will be
able to SSH once it does get to that point because I 'm not yet sure how
the keys are supposed to get onto the new servers. If it is supposed to
be connecting via SSH at this point, then that could be the cause of the
problem although I would expect it to return an error of some kind saying
so if that were the case.

Thanks for your help so far,
Guy

··· On Sunday, 30 June 2013 01:51:48 UTC-7, ohad wrote: > > > > On Fri, Jun 28, 2013 at 8:35 PM, Guy Knights <g...@eastsidegamestudio.com > > wrote: > >> Actually, I haven't yet upgraded to 1.2 as I did some further >> investigation and set the logging mode to debug in >> foreman-proxy/settings.yaml. I'm now getting some more info when I try to >> provision a new node. In the foreman production.log, I gets to a point >> where it keeps outputting the following text into the log, over and over: >> >> Started GET "/tasks/07773504-c911-413e-9730-6bb63e6154e3" for >> 184.71.162.106 at Fri Jun 28 17:26:13 +0000 2013 >> Processing by TasksController#show as >> Parameters: {"id"=>"07773504-c911-413e-9730-6bb63e6154e3"} >> User Load (0.4ms) SELECT "users".* FROM "users" WHERE "users"."id" = 1 >> LIMIT 1 >> Setting current user thread-local variable to admin >> Rendered tasks/_list.rhtml (0.8ms) >> Completed 200 OK in 4ms (Views: 1.4ms | ActiveRecord: 0.7ms) >> >> This corresponds to a progress bar on the web gui, which I had either >> never noticed before or hadn't been showing up before. It appears above the >> new host provisioning form, and gets to "running - Waiting for > > to come online" where it just hangs (see attached screenshot). Even >> after I see that the instance is "running" in the AWS console, this >> progress bar doesn't change, and the text block above just continually >> keeps getting output to the log file. >> >> So that being the case, does this indicate where the problem might lie? >> > I see.. I assume you are running foreman inside EC2, or that at least the > public ip address is not reachable by foreman? > > Ohad > >> >> Thanks, >> Guy >> >> On Wednesday, 26 June 2013 12:21:36 UTC-7, Guy Knights wrote: >>> >>> It is, actually. I'll give 1.2 a go and see if that changes things. >>> >>> Thanks Ohad >>> >>> On Wednesday, 26 June 2013 12:19:52 UTC-7, ohad wrote: >>>> >>>> >>>> >>>> On Wed, Jun 26, 2013 at 8:02 PM, Guy Knights < >>>> g...@eastsidegamestudio.com> wrote: >>>> >>>>> No, I'm using passenger. It's not like the progress bar just doesn't >>>>> show, the entire page hangs (submit button is depressed, "working" cursor >>>>> icon is displayed) until I restart the web server. I can't even close the >>>>> page and reopen it as it just hangs. The server does get provisioned pretty >>>>> much straight away though. >>>> >>>> >>>> Do you see anything your apache logs? (or error logs). >>>> >>>> Is this 1.1? can you try again with 1.2? >>>> >>>> thanks, >>>> Ohad >>>> >>>>> >>>>> On Wednesday, 26 June 2013 00:00:25 UTC-7, ohad wrote: >>>>> >>>>>> >>>>>> >>>>>> On Wed, Jun 26, 2013 at 3:49 AM, Guy Knights < >>>>>> g...@eastsidegamestudio.com> wrote: >>>>>> >>>>>>> I worked out what the problem was here. I had to edit the operating >>>>>>> system in Foreman and set the architecture to x86_64. Once I did that, I >>>>>>> was able to select an operating system after selecting an architecture in >>>>>>> the new host provisioning form. >>>>>>> >>>>>>> I did run into another issue though; once I went through and >>>>>>> provisioned a new host, the Foreman page hung after I hit submit. I left it >>>>>>> for about a minute and eventually closed the page and restarted the web >>>>>>> server. However, I checked the EC2 console and the new instance had been >>>>>>> created so I'm not sure what happened. Any ideas? >>>>>>> >>>>>> >>>>>> are you using webrick? the progress bar only works if you have >>>>>> something that can server multiple foreman connections (such as passenger). >>>>>> >>>>>> Ohad >>>>>> >>>>>>> >>>>>>> On Thursday, 20 June 2013 16:13:32 UTC-7, Guy Knights wrote: >>>>>>>> >>>>>>>> That would be really helpful, thanks Jim. >>>>>>>> >>>>>>>> On Thursday, 20 June 2013 00:43:33 UTC-7, Paradoxbound wrote: >>>>>>>>> >>>>>>>>> I will be adding some more AWS accounts to our 1.1 Foreman install >>>>>>>>> today. I will try and capture as much of the process for you as I can and >>>>>>>>> build a couple of test instances. I basically bumbled through Ohad's blog >>>>>>>>> post and it eventually worked. >>>>>>>>> >>>>>>>>> Jim >>>>>>>>> >>>>>>>>> >>>>>>>>> On 20 June 2013 01:23, Guy Knights wrote: >>>>>>>>> >>>>>>>>>> Just bumping this to see if it brings any new suggestions as I >>>>>>>>>> haven't been able to resolve it yet. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote: >>>>>>>>>>> >>>>>>>>>>> Hi Greg, >>>>>>>>>>> >>>>>>>>>>> Yep, the template I want to apply is set there as "final". >>>>>>>>>>> >>>>>>>>>>> Guy >>>>>>>>>>> >>>>>>>>>>> On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote: >>>>>>>>>>>> >>>>>>>>>>>> Hi Guy, >>>>>>>>>>>> >>>>>>>>>>>> If you re-edit your operating system and go to the final tab, >>>>>>>>>>>> is there a default template set there, or is the combobox blank? >>>>>>>>>>>> >>>>>>>>>>>> Regards, >>>>>>>>>>>> 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-user...@googlegroups.**c****om. >>>>>>>>>> To post to this group, send email to forema...@googlegroups.com. >>>>>>>>>> Visit this group at http://groups.google.com/**group**** >>>>>>>>>> /foreman-users . >>>>>>>>>> For more options, visit https://groups.google.com/**grou**** >>>>>>>>>> ps/opt_out . >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>> 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-user...@**googlegroups.**com. >>>>>>> To post to this group, send email to forema...@googlegroups.com**. >>>>>>> Visit this group at http://groups.google.com/**group**/foreman-users >>>>>>> . >>>>>>> For more options, visit https://groups.google.com/**grou**ps/opt_out >>>>>>> . >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>> 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-user...@googlegroups.**com. >>>>> To post to this group, send email to forema...@googlegroups.com. >>>>> Visit this group at http://groups.google.com/**group/foreman-users >>>>> . >>>>> For more options, visit https://groups.google.com/**groups/opt_out >>>>> . >>>>> >>>>> >>>>> >>>> >>>> -- >> 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-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >

> Yes, my Foreman instance is running from within EC2. It's part of the
> default security group, and every instance I've been trying to create is
> also a member of the default security group so theoretically the foreman
> server should be able contact these new instances.
>
> Just out of interest, what exactly is happening at this point? Is the
> foreman server trying to connect via SSH? It doesn't appear so, according
> to the screenshot I attached, but I was curious as I don't think it will be
> able to SSH once it does get to that point because I 'm not yet sure how
> the keys are supposed to get onto the new servers. If it is supposed to
> be connecting via SSH at this point, then that could be the cause of the
> problem although I would expect it to return an error of some kind saying
> so if that were the case.
>
> I think there are two different issues here.

first, foreman by defaults tries to reach out via the public ip address,
not sure if thats being blocked by something.
secondly, foreman does try to ssh to the instance, when you created the
compute resource, a new key pair was created at ec2 console (you could find
it under foreman-<uuid> in your ec2 console.
using this key pair, foreman uploads a script (the output of the generated
template) and execute it on that system.

Ohad

··· On Mon, Jul 1, 2013 at 8:33 PM, Guy Knights wrote:

Thanks for your help so far,
Guy

On Sunday, 30 June 2013 01:51:48 UTC-7, ohad wrote:

On Fri, Jun 28, 2013 at 8:35 PM, Guy Knights <g...@eastsidegamestudio.com >> > wrote:

Actually, I haven’t yet upgraded to 1.2 as I did some further
investigation and set the logging mode to debug in
foreman-proxy/settings.yaml. I’m now getting some more info when I try to
provision a new node. In the foreman production.log, I gets to a point
where it keeps outputting the following text into the log, over and over:

Started GET “/tasks/07773504-c911-413e-**9730-6bb63e6154e3” for
184.71.162.106 at Fri Jun 28 17:26:13 +0000 2013
Processing by TasksController#show as
Parameters: {“id”=>"07773504-c911-413e-*9730-6bb63e6154e3"}
User Load (0.4ms) SELECT “users”.
FROM “users” WHERE “users”.“id” =
1 LIMIT 1
Setting current user thread-local variable to admin
Rendered tasks/_list.rhtml (0.8ms)
Completed 200 OK in 4ms (Views: 1.4ms | ActiveRecord: 0.7ms)

This corresponds to a progress bar on the web gui, which I had either
never noticed before or hadn’t been showing up before. It appears above the
new host provisioning form, and gets to "running - Waiting for <instance

to come online" where it just hangs (see attached screenshot). Even
after I see that the instance is “running” in the AWS console, this
progress bar doesn’t change, and the text block above just continually
keeps getting output to the log file.

So that being the case, does this indicate where the problem might lie?

I see… I assume you are running foreman inside EC2, or that at least the
public ip address is not reachable by foreman?

Ohad

Thanks,
Guy

On Wednesday, 26 June 2013 12:21:36 UTC-7, Guy Knights wrote:

It is, actually. I’ll give 1.2 a go and see if that changes things.

Thanks Ohad

On Wednesday, 26 June 2013 12:19:52 UTC-7, ohad wrote:

On Wed, Jun 26, 2013 at 8:02 PM, Guy Knights < >>>>> g...@eastsidegamestudio.com> wrote:

No, I’m using passenger. It’s not like the progress bar just doesn’t
show, the entire page hangs (submit button is depressed, “working” cursor
icon is displayed) until I restart the web server. I can’t even close the
page and reopen it as it just hangs. The server does get provisioned pretty
much straight away though.

Do you see anything your apache logs? (or error logs).

Is this 1.1? can you try again with 1.2?

thanks,
Ohad

On Wednesday, 26 June 2013 00:00:25 UTC-7, ohad wrote:

On Wed, Jun 26, 2013 at 3:49 AM, Guy Knights < >>>>>>> g...@eastsidegamestudio.com> wrote:

I worked out what the problem was here. I had to edit the operating
system in Foreman and set the architecture to x86_64. Once I did that, I
was able to select an operating system after selecting an architecture in
the new host provisioning form.

I did run into another issue though; once I went through and
provisioned a new host, the Foreman page hung after I hit submit. I left it
for about a minute and eventually closed the page and restarted the web
server. However, I checked the EC2 console and the new instance had been
created so I’m not sure what happened. Any ideas?

are you using webrick? the progress bar only works if you have
something that can server multiple foreman connections (such as passenger).

Ohad

On Thursday, 20 June 2013 16:13:32 UTC-7, Guy Knights wrote:

That would be really helpful, thanks Jim.

On Thursday, 20 June 2013 00:43:33 UTC-7, Paradoxbound wrote:

I will be adding some more AWS accounts to our 1.1 Foreman
install today. I will try and capture as much of the process for you as I
can and build a couple of test instances. I basically bumbled through
Ohad’s blog post and it eventually worked.

Jim

On 20 June 2013 01:23, Guy Knights g...@eastsidegamestudio.comwrote:

Just bumping this to see if it brings any new suggestions as I
haven’t been able to resolve it yet.

On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote:

Hi Greg,

Yep, the template I want to apply is set there as “final”.

Guy

On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote:

Hi Guy,

If you re-edit your operating system and go to the final tab,
is there a default template set there, or is the combobox blank?

Regards,
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-user…@googlegroups.c****om.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group****
/foreman-users http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/grou****
ps/opt_out https://groups.google.com/groups/opt_out.


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-user…@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com
.
Visit this group at http://groups.google.com/group**
/foreman-users http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/grou**
ps/opt_out https://groups.google.com/groups/opt_out.


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-user…@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-usershttp://groups.google.com/group/foreman-users
.
For more options, visit https://groups.google.com/groups/opt_outhttps://groups.google.com/groups/opt_out
.


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-user…@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com
.
Visit this group at http://groups.google.com/**group/foreman-usershttp://groups.google.com/group/foreman-users
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.


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/groups/opt_out.

I had a problem with Rackspace cloud with a public and private IP address,
I don't know if it is a similar problem I editied the Apache foremam.conf
file and replaced the hard coded IP address with a * and Foreman worked.

You should ensure your Firewall allows systems to connect to 8140, you
might also want to consider using VPCs to manage group of servers.

Jim

··· On 2 July 2013 07:21, Ohad Levy wrote:

On Mon, Jul 1, 2013 at 8:33 PM, Guy Knights guy@eastsidegamestudio.comwrote:

Yes, my Foreman instance is running from within EC2. It’s part of the
default security group, and every instance I’ve been trying to create is
also a member of the default security group so theoretically the foreman
server should be able contact these new instances.

Just out of interest, what exactly is happening at this point? Is the
foreman server trying to connect via SSH? It doesn’t appear so, according
to the screenshot I attached, but I was curious as I don’t think it will be
able to SSH once it does get to that point because I 'm not yet sure how
the keys are supposed to get onto the new servers. If it is supposed to
be connecting via SSH at this point, then that could be the cause of the
problem although I would expect it to return an error of some kind saying
so if that were the case.

I think there are two different issues here.

first, foreman by defaults tries to reach out via the public ip address,
not sure if thats being blocked by something.
secondly, foreman does try to ssh to the instance, when you created the
compute resource, a new key pair was created at ec2 console (you could find
it under foreman- in your ec2 console.
using this key pair, foreman uploads a script (the output of the generated
template) and execute it on that system.

Ohad

Thanks for your help so far,
Guy

On Sunday, 30 June 2013 01:51:48 UTC-7, ohad wrote:

On Fri, Jun 28, 2013 at 8:35 PM, Guy Knights < >>> g...@eastsidegamestudio.com> wrote:

Actually, I haven’t yet upgraded to 1.2 as I did some further
investigation and set the logging mode to debug in
foreman-proxy/settings.yaml. I’m now getting some more info when I try to
provision a new node. In the foreman production.log, I gets to a point
where it keeps outputting the following text into the log, over and over:

Started GET “/tasks/07773504-c911-413e-**9730-6bb63e6154e3” for
184.71.162.106 at Fri Jun 28 17:26:13 +0000 2013
Processing by TasksController#show as
Parameters: {“id”=>"07773504-c911-413e-*9730-6bb63e6154e3"}
User Load (0.4ms) SELECT “users”.
FROM “users” WHERE “users”.“id” =
1 LIMIT 1
Setting current user thread-local variable to admin
Rendered tasks/_list.rhtml (0.8ms)
Completed 200 OK in 4ms (Views: 1.4ms | ActiveRecord: 0.7ms)

This corresponds to a progress bar on the web gui, which I had either
never noticed before or hadn’t been showing up before. It appears above the
new host provisioning form, and gets to "running - Waiting for <instance

to come online" where it just hangs (see attached screenshot). Even
after I see that the instance is “running” in the AWS console, this
progress bar doesn’t change, and the text block above just continually
keeps getting output to the log file.

So that being the case, does this indicate where the problem might lie?

I see… I assume you are running foreman inside EC2, or that at least
the public ip address is not reachable by foreman?

Ohad

Thanks,
Guy

On Wednesday, 26 June 2013 12:21:36 UTC-7, Guy Knights wrote:

It is, actually. I’ll give 1.2 a go and see if that changes things.

Thanks Ohad

On Wednesday, 26 June 2013 12:19:52 UTC-7, ohad wrote:

On Wed, Jun 26, 2013 at 8:02 PM, Guy Knights < >>>>>> g...@eastsidegamestudio.com> wrote:

No, I’m using passenger. It’s not like the progress bar just doesn’t
show, the entire page hangs (submit button is depressed, “working” cursor
icon is displayed) until I restart the web server. I can’t even close the
page and reopen it as it just hangs. The server does get provisioned pretty
much straight away though.

Do you see anything your apache logs? (or error logs).

Is this 1.1? can you try again with 1.2?

thanks,
Ohad

On Wednesday, 26 June 2013 00:00:25 UTC-7, ohad wrote:

On Wed, Jun 26, 2013 at 3:49 AM, Guy Knights < >>>>>>>> g...@eastsidegamestudio.com> wrote:

I worked out what the problem was here. I had to edit the
operating system in Foreman and set the architecture to x86_64. Once I did
that, I was able to select an operating system after selecting an
architecture in the new host provisioning form.

I did run into another issue though; once I went through and
provisioned a new host, the Foreman page hung after I hit submit. I left it
for about a minute and eventually closed the page and restarted the web
server. However, I checked the EC2 console and the new instance had been
created so I’m not sure what happened. Any ideas?

are you using webrick? the progress bar only works if you have
something that can server multiple foreman connections (such as passenger).

Ohad

On Thursday, 20 June 2013 16:13:32 UTC-7, Guy Knights wrote:

That would be really helpful, thanks Jim.

On Thursday, 20 June 2013 00:43:33 UTC-7, Paradoxbound wrote:

I will be adding some more AWS accounts to our 1.1 Foreman
install today. I will try and capture as much of the process for you as I
can and build a couple of test instances. I basically bumbled through
Ohad’s blog post and it eventually worked.

Jim

On 20 June 2013 01:23, Guy Knights g...@eastsidegamestudio.comwrote:

Just bumping this to see if it brings any new suggestions as I
haven’t been able to resolve it yet.

On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote:

Hi Greg,

Yep, the template I want to apply is set there as “final”.

Guy

On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote:

Hi Guy,

If you re-edit your operating system and go to the final tab,
is there a default template set there, or is the combobox blank?

Regards,
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-user…@googlegroups.c****om.
To post to this group, send email to forema...@googlegroups.com
.
Visit this group at http://groups.google.com/group****
/foreman-users http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/grou****
ps/opt_out https://groups.google.com/groups/opt_out.


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-user…@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com
.
Visit this group at http://groups.google.com/group**
/foreman-users http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/grou**
ps/opt_out https://groups.google.com/groups/opt_out.


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-user…@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-usershttp://groups.google.com/group/foreman-users
.
For more options, visit https://groups.google.com/groups/opt_outhttps://groups.google.com/groups/opt_out
.


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-user…@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com
.
Visit this group at http://groups.google.com/**group/foreman-usershttp://groups.google.com/group/foreman-users
.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.


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/groups/opt_out.


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/groups/opt_out.

Hmm…when you say reach out via the public IP address, what protocol does
it use? Does it reach out via SSH, or is trying to connect via some other
method?

Also, I was aware of the foreman key pair that gets created, however I'm
not sure how the public key gets onto the actual instances. Am I supposed
to create an AMI that already has the public key added to authorized_keys
in some predefined account?

Thanks for all your help,
Guy

··· On Monday, 1 July 2013 23:21:31 UTC-7, ohad wrote: > > > > On Mon, Jul 1, 2013 at 8:33 PM, Guy Knights <g...@eastsidegamestudio.com > > wrote: > >> Yes, my Foreman instance is running from within EC2. It's part of the >> default security group, and every instance I've been trying to create is >> also a member of the default security group so theoretically the foreman >> server should be able contact these new instances. >> >> Just out of interest, what exactly is happening at this point? Is the >> foreman server trying to connect via SSH? It doesn't appear so, according >> to the screenshot I attached, but I was curious as I don't think it will be >> able to SSH once it does get to that point because I 'm not yet sure how >> the keys are supposed to get onto the new servers. If it *is* supposed to >> be connecting via SSH at this point, then that could be the cause of the >> problem although I would expect it to return an error of some kind saying >> so if that were the case. >> >> I think there are two different issues here. > > first, foreman by defaults tries to reach out via the public ip address, > not sure if thats being blocked by something. > secondly, foreman does try to ssh to the instance, when you created the > compute resource, a new key pair was created at ec2 console (you could find > it under foreman- in your ec2 console. > using this key pair, foreman uploads a script (the output of the generated > template) and execute it on that system. > > Ohad > > >> Thanks for your help so far, >> Guy >> >> On Sunday, 30 June 2013 01:51:48 UTC-7, ohad wrote: >> >>> >>> >>> On Fri, Jun 28, 2013 at 8:35 PM, Guy Knights < >>> g...@eastsidegamestudio.com> wrote: >>> >>>> Actually, I haven't yet upgraded to 1.2 as I did some further >>>> investigation and set the logging mode to debug in >>>> foreman-proxy/settings.yaml. I'm now getting some more info when I try to >>>> provision a new node. In the foreman production.log, I gets to a point >>>> where it keeps outputting the following text into the log, over and over: >>>> >>>> Started GET "/tasks/07773504-c911-413e-**9730-6bb63e6154e3" for >>>> 184.71.162.106 at Fri Jun 28 17:26:13 +0000 2013 >>>> Processing by TasksController#show as >>>> Parameters: {"id"=>"07773504-c911-413e-**9730-6bb63e6154e3"} >>>> User Load (0.4ms) SELECT "users".* FROM "users" WHERE "users"."id" = >>>> 1 LIMIT 1 >>>> Setting current user thread-local variable to admin >>>> Rendered tasks/_list.rhtml (0.8ms) >>>> Completed 200 OK in 4ms (Views: 1.4ms | ActiveRecord: 0.7ms) >>>> >>>> This corresponds to a progress bar on the web gui, which I had either >>>> never noticed before or hadn't been showing up before. It appears above the >>>> new host provisioning form, and gets to "running - Waiting for >>> > to come online" where it just hangs (see attached screenshot). Even >>>> after I see that the instance is "running" in the AWS console, this >>>> progress bar doesn't change, and the text block above just continually >>>> keeps getting output to the log file. >>>> >>>> So that being the case, does this indicate where the problem might lie? >>>> >>> I see.. I assume you are running foreman inside EC2, or that at least >>> the public ip address is not reachable by foreman? >>> >>> Ohad >>> >>>> >>>> Thanks, >>>> Guy >>>> >>>> On Wednesday, 26 June 2013 12:21:36 UTC-7, Guy Knights wrote: >>>>> >>>>> It is, actually. I'll give 1.2 a go and see if that changes things. >>>>> >>>>> Thanks Ohad >>>>> >>>>> On Wednesday, 26 June 2013 12:19:52 UTC-7, ohad wrote: >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Jun 26, 2013 at 8:02 PM, Guy Knights < >>>>>> g...@eastsidegamestudio.com> wrote: >>>>>> >>>>>>> No, I'm using passenger. It's not like the progress bar just doesn't >>>>>>> show, the entire page hangs (submit button is depressed, "working" cursor >>>>>>> icon is displayed) until I restart the web server. I can't even close the >>>>>>> page and reopen it as it just hangs. The server does get provisioned pretty >>>>>>> much straight away though. >>>>>> >>>>>> >>>>>> Do you see anything your apache logs? (or error logs). >>>>>> >>>>>> Is this 1.1? can you try again with 1.2? >>>>>> >>>>>> thanks, >>>>>> Ohad >>>>>> >>>>>>> >>>>>>> On Wednesday, 26 June 2013 00:00:25 UTC-7, ohad wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Jun 26, 2013 at 3:49 AM, Guy Knights < >>>>>>>> g...@eastsidegamestudio.com> wrote: >>>>>>>> >>>>>>>>> I worked out what the problem was here. I had to edit the >>>>>>>>> operating system in Foreman and set the architecture to x86_64. Once I did >>>>>>>>> that, I was able to select an operating system after selecting an >>>>>>>>> architecture in the new host provisioning form. >>>>>>>>> >>>>>>>>> I did run into another issue though; once I went through and >>>>>>>>> provisioned a new host, the Foreman page hung after I hit submit. I left it >>>>>>>>> for about a minute and eventually closed the page and restarted the web >>>>>>>>> server. However, I checked the EC2 console and the new instance had been >>>>>>>>> created so I'm not sure what happened. Any ideas? >>>>>>>>> >>>>>>>> >>>>>>>> are you using webrick? the progress bar only works if you have >>>>>>>> something that can server multiple foreman connections (such as passenger). >>>>>>>> >>>>>>>> Ohad >>>>>>>> >>>>>>>>> >>>>>>>>> On Thursday, 20 June 2013 16:13:32 UTC-7, Guy Knights wrote: >>>>>>>>>> >>>>>>>>>> That would be really helpful, thanks Jim. >>>>>>>>>> >>>>>>>>>> On Thursday, 20 June 2013 00:43:33 UTC-7, Paradoxbound wrote: >>>>>>>>>>> >>>>>>>>>>> I will be adding some more AWS accounts to our 1.1 Foreman >>>>>>>>>>> install today. I will try and capture as much of the process for you as I >>>>>>>>>>> can and build a couple of test instances. I basically bumbled through >>>>>>>>>>> Ohad's blog post and it eventually worked. >>>>>>>>>>> >>>>>>>>>>> Jim >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 20 June 2013 01:23, Guy Knights wrote: >>>>>>>>>>> >>>>>>>>>>>> Just bumping this to see if it brings any new suggestions as I >>>>>>>>>>>> haven't been able to resolve it yet. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Hi Greg, >>>>>>>>>>>>> >>>>>>>>>>>>> Yep, the template I want to apply is set there as "final". >>>>>>>>>>>>> >>>>>>>>>>>>> Guy >>>>>>>>>>>>> >>>>>>>>>>>>> On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Guy, >>>>>>>>>>>>>> >>>>>>>>>>>>>> If you re-edit your operating system and go to the final tab, >>>>>>>>>>>>>> is there a default template set there, or is the combobox blank? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>> 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-user...@googlegroups.**c******om. >>>>>>>>>>>> To post to this group, send email to forema...@googlegroups.com >>>>>>>>>>>> . >>>>>>>>>>>> Visit this group at http://groups.google.com/**group****** >>>>>>>>>>>> /foreman-users . >>>>>>>>>>>> For more options, visit https://groups.google.com/**grou****** >>>>>>>>>>>> ps/opt_out . >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>> 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-user...@**googlegroups.**c**om. >>>>>>>>> To post to this group, send email to forema...@googlegroups.com**. >>>>>>>>> Visit this group at http://groups.google.com/**group**** >>>>>>>>> /foreman-users . >>>>>>>>> For more options, visit https://groups.google.com/**grou**** >>>>>>>>> ps/opt_out . >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>> 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-user...@googlegroups.**c**om. >>>>>>> To post to this group, send email to forema...@googlegroups.com. >>>>>>> Visit this group at http://groups.google.com/**group**/foreman-users >>>>>>> . >>>>>>> For more options, visit https://groups.google.com/**grou**ps/opt_out >>>>>>> . >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>> 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-user...@**googlegroups.com. >>>> To post to this group, send email to forema...@googlegroups.com**. >>>> Visit this group at http://groups.google.com/**group/foreman-users >>>> . >>>> For more options, visit https://groups.google.com/**groups/opt_out >>>> . >>>> >>>> >>>> >>> >>> -- >> 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-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >

My apache conf already uses * instead of hard coded IPs, and my instances
are able to connect to port 8140 on the puppet master (which is also my
foreman server) as I can manually fire up instances and run puppet
successfully. I'll look into VPCs though, as I haven't yet played with that
option. Is there any specific reason why using a VPC instead might help
this particular issue, though?

Thank you,
Guy

··· On Tuesday, 2 July 2013 00:32:33 UTC-7, Paradoxbound wrote: > > I had a problem with Rackspace cloud with a public and private IP address, > I don't know if it is a similar problem I editied the Apache foremam.conf > file and replaced the hard coded IP address with a * and Foreman worked. > > You should ensure your Firewall allows systems to connect to 8140, you > might also want to consider using VPCs to manage group of servers. > > Jim > > > On 2 July 2013 07:21, Ohad Levy <ohad...@gmail.com > wrote: > >> >> >> On Mon, Jul 1, 2013 at 8:33 PM, Guy Knights <g...@eastsidegamestudio.com >> > wrote: >> >>> Yes, my Foreman instance is running from within EC2. It's part of the >>> default security group, and every instance I've been trying to create is >>> also a member of the default security group so theoretically the foreman >>> server should be able contact these new instances. >>> >>> Just out of interest, what exactly is happening at this point? Is the >>> foreman server trying to connect via SSH? It doesn't appear so, according >>> to the screenshot I attached, but I was curious as I don't think it will be >>> able to SSH once it does get to that point because I 'm not yet sure how >>> the keys are supposed to get onto the new servers. If it *is* supposed to >>> be connecting via SSH at this point, then that could be the cause of the >>> problem although I would expect it to return an error of some kind saying >>> so if that were the case. >>> >>> I think there are two different issues here. >> >> first, foreman by defaults tries to reach out via the public ip address, >> not sure if thats being blocked by something. >> secondly, foreman does try to ssh to the instance, when you created the >> compute resource, a new key pair was created at ec2 console (you could find >> it under foreman- in your ec2 console. >> using this key pair, foreman uploads a script (the output of the >> generated template) and execute it on that system. >> >> Ohad >> >> >>> Thanks for your help so far, >>> Guy >>> >>> On Sunday, 30 June 2013 01:51:48 UTC-7, ohad wrote: >>> >>>> >>>> >>>> On Fri, Jun 28, 2013 at 8:35 PM, Guy Knights < >>>> g...@eastsidegamestudio.com> wrote: >>>> >>>>> Actually, I haven't yet upgraded to 1.2 as I did some further >>>>> investigation and set the logging mode to debug in >>>>> foreman-proxy/settings.yaml. I'm now getting some more info when I try to >>>>> provision a new node. In the foreman production.log, I gets to a point >>>>> where it keeps outputting the following text into the log, over and over: >>>>> >>>>> Started GET "/tasks/07773504-c911-413e-**9730-6bb63e6154e3" for >>>>> 184.71.162.106 at Fri Jun 28 17:26:13 +0000 2013 >>>>> Processing by TasksController#show as >>>>> Parameters: {"id"=>"07773504-c911-413e-**9730-6bb63e6154e3"} >>>>> User Load (0.4ms) SELECT "users".* FROM "users" WHERE "users"."id" >>>>> = 1 LIMIT 1 >>>>> Setting current user thread-local variable to admin >>>>> Rendered tasks/_list.rhtml (0.8ms) >>>>> Completed 200 OK in 4ms (Views: 1.4ms | ActiveRecord: 0.7ms) >>>>> >>>>> This corresponds to a progress bar on the web gui, which I had either >>>>> never noticed before or hadn't been showing up before. It appears above the >>>>> new host provisioning form, and gets to "running - Waiting for >>>> > to come online" where it just hangs (see attached screenshot). Even >>>>> after I see that the instance is "running" in the AWS console, this >>>>> progress bar doesn't change, and the text block above just continually >>>>> keeps getting output to the log file. >>>>> >>>>> So that being the case, does this indicate where the problem might lie? >>>>> >>>> I see.. I assume you are running foreman inside EC2, or that at least >>>> the public ip address is not reachable by foreman? >>>> >>>> Ohad >>>> >>>>> >>>>> Thanks, >>>>> Guy >>>>> >>>>> On Wednesday, 26 June 2013 12:21:36 UTC-7, Guy Knights wrote: >>>>>> >>>>>> It is, actually. I'll give 1.2 a go and see if that changes things. >>>>>> >>>>>> Thanks Ohad >>>>>> >>>>>> On Wednesday, 26 June 2013 12:19:52 UTC-7, ohad wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Jun 26, 2013 at 8:02 PM, Guy Knights < >>>>>>> g...@eastsidegamestudio.com> wrote: >>>>>>> >>>>>>>> No, I'm using passenger. It's not like the progress bar just >>>>>>>> doesn't show, the entire page hangs (submit button is depressed, "working" >>>>>>>> cursor icon is displayed) until I restart the web server. I can't even >>>>>>>> close the page and reopen it as it just hangs. The server does get >>>>>>>> provisioned pretty much straight away though. >>>>>>> >>>>>>> >>>>>>> Do you see anything your apache logs? (or error logs). >>>>>>> >>>>>>> Is this 1.1? can you try again with 1.2? >>>>>>> >>>>>>> thanks, >>>>>>> Ohad >>>>>>> >>>>>>>> >>>>>>>> On Wednesday, 26 June 2013 00:00:25 UTC-7, ohad wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Jun 26, 2013 at 3:49 AM, Guy Knights < >>>>>>>>> g...@eastsidegamestudio.com> wrote: >>>>>>>>> >>>>>>>>>> I worked out what the problem was here. I had to edit the >>>>>>>>>> operating system in Foreman and set the architecture to x86_64. Once I did >>>>>>>>>> that, I was able to select an operating system after selecting an >>>>>>>>>> architecture in the new host provisioning form. >>>>>>>>>> >>>>>>>>>> I did run into another issue though; once I went through and >>>>>>>>>> provisioned a new host, the Foreman page hung after I hit submit. I left it >>>>>>>>>> for about a minute and eventually closed the page and restarted the web >>>>>>>>>> server. However, I checked the EC2 console and the new instance had been >>>>>>>>>> created so I'm not sure what happened. Any ideas? >>>>>>>>>> >>>>>>>>> >>>>>>>>> are you using webrick? the progress bar only works if you have >>>>>>>>> something that can server multiple foreman connections (such as passenger). >>>>>>>>> >>>>>>>>> Ohad >>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thursday, 20 June 2013 16:13:32 UTC-7, Guy Knights wrote: >>>>>>>>>>> >>>>>>>>>>> That would be really helpful, thanks Jim. >>>>>>>>>>> >>>>>>>>>>> On Thursday, 20 June 2013 00:43:33 UTC-7, Paradoxbound wrote: >>>>>>>>>>>> >>>>>>>>>>>> I will be adding some more AWS accounts to our 1.1 Foreman >>>>>>>>>>>> install today. I will try and capture as much of the process for you as I >>>>>>>>>>>> can and build a couple of test instances. I basically bumbled through >>>>>>>>>>>> Ohad's blog post and it eventually worked. >>>>>>>>>>>> >>>>>>>>>>>> Jim >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 20 June 2013 01:23, Guy Knights >>>>>>>>>>> > wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Just bumping this to see if it brings any new suggestions as I >>>>>>>>>>>>> haven't been able to resolve it yet. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Friday, 14 June 2013 15:34:13 UTC-7, Guy Knights wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Greg, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Yep, the template I want to apply is set there as "final". >>>>>>>>>>>>>> >>>>>>>>>>>>>> Guy >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Friday, 14 June 2013 13:34:05 UTC-7, Greg Sutcliffe wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Guy, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> If you re-edit your operating system and go to the final >>>>>>>>>>>>>>> tab, is there a default template set there, or is the combobox blank? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>> 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-user...@googlegroups.**c******om. >>>>>>>>>>>>> To post to this group, send email to >>>>>>>>>>>>> forema...@googlegroups.com. >>>>>>>>>>>>> Visit this group at http://groups.google.com/**group****** >>>>>>>>>>>>> /foreman-users . >>>>>>>>>>>>> For more options, visit https://groups.google.com/**grou****** >>>>>>>>>>>>> ps/opt_out . >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>> 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-user...@**googlegroups.**c**om. >>>>>>>>>> To post to this group, send email to forema...@googlegroups.com** >>>>>>>>>> . >>>>>>>>>> Visit this group at http://groups.google.com/**group**** >>>>>>>>>> /foreman-users . >>>>>>>>>> For more options, visit https://groups.google.com/**grou**** >>>>>>>>>> ps/opt_out . >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>> 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-user...@googlegroups.**c**om. >>>>>>>> To post to this group, send email to forema...@googlegroups.com. >>>>>>>> Visit this group at http://groups.google.com/**group** >>>>>>>> /foreman-users . >>>>>>>> For more options, visit https://groups.google.com/**grou** >>>>>>>> ps/opt_out . >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>> 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-user...@**googlegroups.com. >>>>> To post to this group, send email to forema...@googlegroups.com**. >>>>> Visit this group at http://groups.google.com/**group/foreman-users >>>>> . >>>>> For more options, visit https://groups.google.com/**groups/opt_out >>>>> . >>>>> >>>>> >>>>> >>>> >>>> -- >>> 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-user...@googlegroups.com . >>> To post to this group, send email to forema...@googlegroups.com >>> . >>> Visit this group at http://groups.google.com/group/foreman-users. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> -- >> 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-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >