Finished unattend installation callback failed, 409 possible Loop

Support
1

Hi,

when I install a new machine, the whole procedure runs fine. Get its files
from tftp, runs installation but during callback it failes.

<https://lh3.googleusercontent.com/-CE4nzgWANeI/WDWFfD-xHKI/AAAAAAAAP7o/FFK-ySR2-jI4zNcCDFp6cxVdvKG0EyLyQCLcB/s1600/failed_callback.jpg>

When I set in the foreman settings
"Update IP from built request" = true it doesn't work

But with false it works, but every Host get added with IPAddress Name
instead of given hostname. So I got double entries in the List.
Also the added hosts with IPAddress Names are not manged or associated.
After time just the IPAddressed ones get updated for "Last report"
Informations

In my foreman Log I can find this :

2016-11-23 12:39:41 [app] [I] Completed 409 Conflict in 1931ms
(ActiveRecord: 28.6ms)

What can I do? Have no clue to fix this.

<https://lh3.googleusercontent.com/-VKI5JJxolCg/WDWFxt6_OkI/AAAAAAAAP7s/tKV71PuLXjAZSM4pzWBtsKs6-PVopdUhgCLcB/s1600/double_entries.jpg>
Thanks a lot,

Tom

2

Further more, if I run

puppet agent --test

on one of that doubled machines, it pushes the report to the IPAddress
named ones.

3

Hello,

I think you explained it, when update_ip_from_built is set, then Foreman
makes attempt to change the provisioning IP address to the one that was
reported from. If you are not using NAT, this will work as expected, unless
there is an IP address in Foreman database already defined for any
interface. Than, that's a conflict. Use search interface to find such an IP.

··· On Wed, Nov 23, 2016 at 1:32 PM, Tom K. wrote:

Further more, if I run

puppet agent --test

on one of that doubled machines, it pushes the report to the IPAddress
named ones.

–
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 https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–
Later,
Lukas @lzap Zapletal

4

Ok, I think I understand.
But what do you mean with " Use search interface to find such an IP."

– Tom

··· Am Mittwoch, 23. November 2016 14:17:19 UTC+1 schrieb Lukas Zapletal: > > Hello, > > I think you explained it, when update_ip_from_built is set, then Foreman > makes attempt to change the provisioning IP address to the one that was > reported from. If you are not using NAT, this will work as expected, unless > there is an IP address in Foreman database already defined for *any* > interface. Than, that's a conflict. Use search interface to find such an IP. > > On Wed, Nov 23, 2016 at 1:32 PM, Tom K. <t...@to3.de > wrote: > >> Further more, if I run >> >> puppet agent --test >> >> on one of that doubled machines, it pushes the report to the IPAddress >> named ones. >> >> >> -- >> 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 https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Later, > Lukas @lzap Zapletal >