Hi,
We are currently using foreman 1.1 to launch ec2 instances into vpc.
To get this working, we have applied the following patches:
https://github.com/rvrignaud/foreman/commit/d4d546fcb9d443d4a6d0793fdef2a36ed423f84c
—> VPC support
In our current setup we are trying to include DNS into foreman-proxy.
We have become aware of the following bug which describe pretty much the
problem we are facing.
Is there a workaround or a fix to this issue?
Regards.
> Hi,
>
> We are currently using foreman 1.1 to launch ec2 instances into vpc.
> To get this working, we have applied the following patches:
>
>
> https://github.com/rvrignaud/foreman/commit/d4d546fcb9d443d4a6d0793fdef2a36ed423f84c---> VPC support
> https://github.com/theforeman/foreman/pull/409<https://github.com/theforeman/foreman/pull/409/files>
+ name.present? and ip.present? and !subnet.nil? and subnet.dhcp? and
> managed? and capabilities.include?(:build)
/files <https://github.com/theforeman/foreman/pull/409/files>
> ----> IAM support
>
> In our current setup we are trying to include DNS into foreman-proxy.
> We have become aware of the following bug which describe pretty much the
> problem we are facing.
> Bug #2325: No A record created in domain when provisioning an ec2 vm - Foreman
>
> Is there a workaround or a fix to this issue?
>
yes, just undo the chnage is written in the ticket, we'll ensure we'll fix
it for 1.2
Ohad
Regards.
–
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.