nic 1 = management setup via dhclient with working dns
nic 2 = foreman provisioning network 172.16.1.0/24
I followed docs as closely as I could and had no errors, provisioned using
the 'provisioning' wizard, after following docs on how to setup pxe master.
I see a dhcpd process which is configured correctly on the right subnet.
Tcpdumps on provisioning interface show client requesting dhcp, but no
answers forthcoming from the discovery server (foreman).
When I 'type in' the mac, the provisioner discovers the host and then fails
to install the os (I tried default centos). Is it the dual homed setup? I
didn't setup a default gateway, assuming that the provisioner would take
care of all necessary forwarding.
···
On Sunday, January 3, 2016 at 11:19:17 PM UTC-5, Thomas Munn wrote:
>
> I have uploaded a debug for the developers:
>
> http://debugs.theforeman.org/foreman-debug-QlILi.tar.xz
>
> My setup is as follows:
>
> (testing in vmware lab for now)
>
> nic 1 = management setup via dhclient with working dns
> nic 2 = foreman provisioning network 172.16.1.0/24
>
> I followed docs as closely as I could and had no errors, provisioned using
> the 'provisioning' wizard, after following docs on how to setup pxe master.
> I see a dhcpd process which is configured correctly on the right subnet.
>
> Tcpdumps on provisioning interface show client requesting dhcp, but no
> answers forthcoming from the discovery server (foreman).
>
> When I 'type in' the mac, the provisioner discovers the host and then
> fails to install the os (I tried default centos). Is it the dual homed
> setup? I didn't setup a default gateway, assuming that the provisioner
> would take care of all necessary forwarding.
>
> Any faqs on how do a dual homed setup?
>
> Thomas
>
>
>
I also tried 'hard coding' the ip address of the foreman server in the
settings for foreman server/http assist.
···
On Sunday, January 3, 2016 at 11:19:17 PM UTC-5, Thomas Munn wrote:
>
> I have uploaded a debug for the developers:
>
> http://debugs.theforeman.org/foreman-debug-QlILi.tar.xz
>
> My setup is as follows:
>
> (testing in vmware lab for now)
>
> nic 1 = management setup via dhclient with working dns
> nic 2 = foreman provisioning network 172.16.1.0/24
>
> I followed docs as closely as I could and had no errors, provisioned using
> the 'provisioning' wizard, after following docs on how to setup pxe master.
> I see a dhcpd process which is configured correctly on the right subnet.
>
> Tcpdumps on provisioning interface show client requesting dhcp, but no
> answers forthcoming from the discovery server (foreman).
>
> When I 'type in' the mac, the provisioner discovers the host and then
> fails to install the os (I tried default centos). Is it the dual homed
> setup? I didn't setup a default gateway, assuming that the provisioner
> would take care of all necessary forwarding.
>
> Any faqs on how do a dual homed setup?
>
> Thomas
>
>
>
Actually the thing I was concerned about was the DHCP features with
discovery. I did get a lease (since I had assumed the entire /24 was
available in the gui) when I specifically entered a mac address in the
'host' option. Was not aware that I had to reserve a specific range if I
dedicated the entire net to dhcp… I will try it your way to see what
happens. Thanks for the help. Things get a little muddled when you are
doing troubleshooting at 0100!
Thomas
···
On Sunday, January 3, 2016 at 11:19:17 PM UTC-5, Thomas Munn wrote:
nic 1 = management setup via dhclient with working dns
nic 2 = foreman provisioning network 172.16.1.0/24
I followed docs as closely as I could and had no errors, provisioned using
the ‘provisioning’ wizard, after following docs on how to setup pxe master.
I see a dhcpd process which is configured correctly on the right subnet.
Tcpdumps on provisioning interface show client requesting dhcp, but no
answers forthcoming from the discovery server (foreman).
When I ‘type in’ the mac, the provisioner discovers the host and then
fails to install the os (I tried default centos). Is it the dual homed
setup? I didn’t setup a default gateway, assuming that the provisioner
would take care of all necessary forwarding.
> nic 1 = management setup via dhclient with working dns
> nic 2 = foreman provisioning network 172.16.1.0/24
>
> I followed docs as closely as I could and had no errors, provisioned using
> the 'provisioning' wizard, after following docs on how to setup pxe master.
> I see a dhcpd process which is configured correctly on the right subnet.
>
> Tcpdumps on provisioning interface show client requesting dhcp, but no
> answers forthcoming from the discovery server (foreman).
>
> When I 'type in' the mac, the provisioner discovers the host and then fails
> to install the os (I tried default centos). Is it the dual homed setup? I
> didn't setup a default gateway, assuming that the provisioner would take
> care of all necessary forwarding.
to be honest, I don't actually understand your workflow. Having issues
when discovering a host, or when provisioning a (discovered?) host?
Anyway, quick investigation of your DHCP server configuration:
You have DHCPDARGS=" eno33554960" in the sysconfig, is this the correct
interface to listen on? Maybe missing another?
You nave no pool allocated in the 172.16.1.0 subnet! DHCP will never
return a lease with this setup.
Our installer contains all the necessary option to correctly setup a
DHCP service:
It looks like you are running into an asymetric routing issue, traffic
coming in through nic1 but being routed out through nic2. I ran into this
same issue as well with a similar setup as yours.
