Could you add more info please? I don't see the error that you've mentioned anywhere in foreman-debug log, where did you find the trace? According to the message, it seems that something is wrong with networking, like discovered interfaces are invalid in Foreman.

i get this error message when i highlight the newly discovered host and then click provision.
the discover was successful so i dont know how could the network will have problem.
thx

by the way the clients have network interface names as enp7s0f0, enp7s0f1, enp14s0f0 and enp14s0f1, not using typical network naming such as eth1 and eth2. just so you know. i dont know if that might be the problem.
thx

I discovered a host using the facts provided and it worked just fine with 1.8/3.0 discovery. The error message is weird, I cannot find it in Foreman code base. When do you see it? Does it block provisioning?

i now just find see that it has a invalid network interface there because i had an ip address change. i tried to delete that interface and it is not letting me. i tried to delete the whole proxy server and re-create and it wont let me either. i even tried to delete the whole organization all together so i can recreate it wont let me either. can you provide me a proper procedure on how to do any of that? or even to delete the whole foreman database so i can start from begining will work too.

thanks,

Another user hit this.

Can you guys describe properly how did you get there? I cannot reproduce on my systems. At what stage do you see this error?

Lukas Zapletal wrote:

Another user hit this.

Can you guys describe properly how did you get there? I cannot reproduce on my systems. At what stage do you see this error?

I am seeing this same issue as well. This is occurring on a "discovered" machine (Dell PowerEdge R320) using discovery image 2.1 and Foreman 1.8.2/discovery 3.0.0.

larry campbell wrote:

I am seeing this same issue as well. This is occurring on a "discovered" machine (Dell PowerEdge R320) using discovery image 2.1 and Foreman 1.8.2/discovery 3.0.0.

One thing to point out, if I just "Add Host" and tie the mac address into the interface, the machine deploys successfully. It seems there's some issue with the Facts that discovery is sending to Foreman that get lost / broken when the "provision" button is hit.

i got my issue resolved already. my problem was that the proxy server (also foreman server itself) was in a dual-home, so i have to edit the interface entries under the foreman host itself before it can provision other machines.

thanks for getting back to me anyway ;)

Can you elaborate on the changes you made? It might help me fix my problem (and identify where the "glitch" is)

tony zheng wrote:

i got my issue resolved already. my problem was that the proxy server (also foreman server itself) was in a dual-home, so i have to edit the interface entries under the foreman host itself before it can provision other machines.

is your foreman server (or the proxy server) dual homed? if yes, you might want to check under host properties for the NICs to make sure they have proper ip addresses assigned and correct primary and provisional interface set.