For the sake of documentation:
It happened because I reinstalled foreman, and I did not delete old
foreman-* security key from ec2.
Solution for me was
Delete old foreman-* security key and recreate a compute resource.
···
On Tuesday, April 9, 2013 10:25:47 PM UTC-7, Dmitry Kireev wrote:
>
> Hi,
>
> I'm using up foreman, and it was working, but after certain rounds of
> playing around with it ec2 provisioning stopped working. I can see my EC2
> instances list. When creating a new ec2 host, I can fill out my form, and
> even click "submit", but nothing happens after that. "*Settings up
> compute instance*" fails
>
> Foreman logs show the following:
> *Parameters: {}*
> *Rolling back due to a problem: Settings up compute instance fqdn.name.com
> 1 failed fqdn.name.comsetCompute*
> *
> *
> Is there any place where I can enable debug logging for foreman-ec2?
> I would appreciate any ideas as well.
>
> Thank you.
>