Impossible to add a new Provisionning on an other network

Hi everybody

I created a new subnet because I need to install some host on it. But, when
I try to set up the provisionning, I have this error: Failed to save: Host
has already been taken

I have no idea why Foreman do this error because I don't have any duplicate
MAC Adress or IP

Can you help me ?

Thx a lot

Quentin Lenglet

Not without more context, check production.log and find what exactly
is wrong. This might be name clash, make sure you name your host with
an unique name or DNS name as well.

LZ

··· On Tue, May 23, 2017 at 12:07 PM, Quentin lenglet wrote: > Hi everybody > > I created a new subnet because I need to install some host on it. But, when > I try to set up the provisionning, I have this error: Failed to save: Host > has already been taken > > I have no idea why Foreman do this error because I don't have any duplicate > MAC Adress or IP > > Can you help me ? > > Thx a lot > > Quentin Lenglet > > -- > 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

Hi and thx for your answer

The big problem is that i have this only message. I check all the mac
address and i don't have any who are equals.
In fact, I have already a provionning which works perfectly. Now i want to
add a new one to an other subnet.
I have a second interface into this network and i have the error message
only in the log.

Thx again for any help

Later

Quentin Lenglet

Hi,

Somebody has been already in this situation ?

Thx for any answers

Cheer

Quentin Lenglet

i have the same issue before i check if y
the dhcp configuration in the proxy was enable also check if the url on the
foreman-proxy and the trusted hosts are correct

··· On Monday, May 29, 2017 at 10:44:13 AM UTC+2, Quentin lenglet wrote: > > Hi, > > > Somebody has been already in this situation ? > > Thx for any answers > > Cheer > > Quentin Lenglet >