Problems provisioning first server from foreman

I am new to foreman and having trouble provisioning my first server using
it.

I am using Foreman 1.6.1 on a clean install of CentOS 6.5 (64 bit).

The install process seemed to go without error using the puppet installer.

I have setup the provisioning configuration. It told me to run the
following command which I did,

foreman-installer
–enable-foreman-proxy
–foreman-proxy-tftp=true
–foreman-proxy-tftp-servername=172.16.50.250
–foreman-proxy-dhcp=true
–foreman-proxy-dhcp-interface=eth0
–foreman-proxy-dhcp-gateway=172.16.50.254
–foreman-proxy-dhcp-range=" "
–foreman-proxy-dhcp-nameservers="172.16.10.10,172.16.10.14"
–foreman-proxy-dns=true
–foreman-proxy-dns-interface=eth0
–foreman-proxy-dns-zone=erased.com
–foreman-proxy-dns-reverse=50.16.172.in-addr.arpa
–foreman-proxy-dns-forwarders=172.16.50.14
–foreman-proxy-dns-forwarders=172.16.10.10
–foreman-proxy-foreman-base-url=https://mel-prov01.erased.com
–foreman-proxy-oauth-consumer-key=erased
–foreman-proxy-oauth-consumer-secret=erased

When I ran this the dhcp server failed to start because their were no values for the range in /etc/dhcp/dhcpd.conf so I commented them out and it started ok.

/etc/foreman-proxy/dhcp.yml is:

··· --- # Enable DHCP management :enabled: true # valid vendors: # - isc # - native_ms (Microsoft native implementation) # - virsh (simple implementation for libvirt) :dhcp_vendor: isc :dhcp_config: /etc/dhcp/dhcpd.conf :dhcp_leases: /var/lib/dhcpd/dhcpd.leases #:dhcp_key_name: secret_key_name #:dhcp_key_secret: secret_key

ls -al /etc/dhcp/
total 28
drwxr-xr-x. 3 foreman-proxy foreman-proxy 4096 Oct 14 20:39 .
drwxr-xr-x. 66 root root 4096 Oct 14 22:04 …
drwxr-xr-x. 2 root root 4096 Nov 23 2013 dhclient.d
-rw-r–r--. 1 root root 87 Oct 14 00:25 dhclient-eth0.conf
-rw-r–r--. 1 root root 193 Nov 23 2013 dhcpd6.conf
-rw-r–r--. 1 foreman-proxy foreman-proxy 710 Oct 14 18:41 dhcpd.conf
-rw-r–r--. 1 root root 20 Oct 14 18:11 dhcpd.hosts

I want to provision Centos on vsphere virtual machine using PXE boot.

The problem is that the smart-proxy is not responding to the dhcp request.
But dhcpd is running.

/var/log/messages contains:
Oct 14 22:09:28 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 via
eth0: network 172.16.50.0/24: no free leases
Oct 14 22:09:30 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 via
eth0: network 172.16.50.0/24: no free leases
Oct 14 22:09:34 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 via
eth0: network 172.16.50.0/24: no free leases
Oct 14 22:09:42 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 via
eth0: network 172.16.50.0/24: no free leases
Oct 14 22:09:46 mel-prov01 dhcpd: DHCPINFORM from 172.16.50.107 via eth0:
not authoritative for subnet 172.16.50.0
Oct 14 22:09:58 mel-prov01 dhcpd: DHCPINFORM from 172.16.50.108 via eth0:
not authoritative for subnet 172.16.50.0

Where is Foreman supposed to put the MAC address and the IP address?

Any idea on what is going wrong?

thanks

Well as you didn't specify a range of dhcp addresses, there are no ip's
for dhcpd to assign. The foreman uses dynamic ip assignment. It's just
as the error says "no free leases".

So fill in a range in --foreman-proxy-dhcp-range=" " and everything will
be fine…

Kind regards,

Jorick Astrego
Netbulae

Met vriendelijke groet, With kind regards,
Jorick Astrego

Netbulae Virtualization Experts

··· On 10/14/2014 05:25 AM, gaumann@indoaustinvestments.com wrote: > I am new to foreman and having trouble provisioning my first server > using it. > > I am using Foreman 1.6.1 on a clean install of CentOS 6.5 (64 bit). > > The install process seemed to go without error using the puppet installer. > > I have setup the provisioning configuration. It told me to run the > following command which I did, > foreman-installer \ > --enable-foreman-proxy \ > --foreman-proxy-tftp=true \ > --foreman-proxy-tftp-servername=172.16.50.250 \ > --foreman-proxy-dhcp=true \ > --foreman-proxy-dhcp-interface=eth0 \ > --foreman-proxy-dhcp-gateway=172.16.50.254 \ > --foreman-proxy-dhcp-range=" " \ > --foreman-proxy-dhcp-nameservers="172.16.10.10,172.16.10.14" \ > --foreman-proxy-dns=true \ > --foreman-proxy-dns-interface=eth0 \ > --foreman-proxy-dns-zone=erased.com \ > --foreman-proxy-dns-reverse=50.16.172.in-addr.arpa \ > --foreman-proxy-dns-forwarders=172.16.50.14 \ > --foreman-proxy-dns-forwarders=172.16.10.10 \ > --foreman-proxy-foreman-base-url=https://mel-prov01.erased.com \ > --foreman-proxy-oauth-consumer-key=erased \ > --foreman-proxy-oauth-consumer-secret=erased > > When I ran this the dhcp server failed to start because their were no values for the range in /etc/dhcp/dhcpd.conf so I commented them out and it started ok. > > /etc/foreman-proxy/dhcp.yml is: > --- > # Enable DHCP management > :enabled: true > # valid vendors: > # - isc > # - native_ms (Microsoft native implementation) > # - virsh (simple implementation for libvirt) > :dhcp_vendor: isc > :dhcp_config: /etc/dhcp/dhcpd.conf > :dhcp_leases: /var/lib/dhcpd/dhcpd.leases > #:dhcp_key_name: secret_key_name > #:dhcp_key_secret: secret_key > > ls -al /etc/dhcp/ > total 28 > drwxr-xr-x. 3 foreman-proxy foreman-proxy 4096 Oct 14 20:39 . > drwxr-xr-x. 66 root root 4096 Oct 14 22:04 .. > drwxr-xr-x. 2 root root 4096 Nov 23 2013 dhclient.d > -rw-r--r--. 1 root root 87 Oct 14 00:25 dhclient-eth0.conf > -rw-r--r--. 1 root root 193 Nov 23 2013 dhcpd6.conf > -rw-r--r--. 1 foreman-proxy foreman-proxy 710 Oct 14 18:41 dhcpd.conf > -rw-r--r--. 1 root root 20 Oct 14 18:11 dhcpd.hosts > > I want to provision Centos on vsphere virtual machine using PXE boot. > > The problem is that the smart-proxy is not responding to the dhcp > request. But dhcpd is running. > > /var/log/messages contains: > Oct 14 22:09:28 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 > via eth0: network 172.16.50.0/24: no free leases > Oct 14 22:09:30 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 > via eth0: network 172.16.50.0/24: no free leases > Oct 14 22:09:34 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 > via eth0: network 172.16.50.0/24: no free leases > Oct 14 22:09:42 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 > via eth0: network 172.16.50.0/24: no free leases > Oct 14 22:09:46 mel-prov01 dhcpd: DHCPINFORM from 172.16.50.107 via > eth0: not authoritative for subnet 172.16.50.0 > Oct 14 22:09:58 mel-prov01 dhcpd: DHCPINFORM from 172.16.50.108 via > eth0: not authoritative for subnet 172.16.50.0 > > Where is Foreman supposed to put the MAC address and the IP address? > > Any idea on what is going wrong? > > thanks > ----------------
Tel: 053 20 30 270 	info@netbulae.eu 	Staalsteden 4-3A 	KvK 08198180
Fax: 053 20 30 271 	www.netbulae.eu 	7547 TA Enschede 	BTW NL821234584B01

>
>
>
> I am new to foreman and having trouble provisioning my first server using
> it.
>
> I am using Foreman 1.6.1 on a clean install of CentOS 6.5 (64 bit).
>
> The install process seemed to go without error using the puppet installer.
>
> I have setup the provisioning configuration. It told me to run the
> following command which I did,
>
> foreman-installer
> --enable-foreman-proxy
> --foreman-proxy-tftp=true
> --foreman-proxy-tftp-servername=172.16.50.250
> --foreman-proxy-dhcp=true
> --foreman-proxy-dhcp-interface=eth0
> --foreman-proxy-dhcp-gateway=172.16.50.254
> --foreman-proxy-dhcp-range=" "
> --foreman-proxy-dhcp-nameservers="172.16.10.10,172.16.10.14"
> --foreman-proxy-dns=true
> --foreman-proxy-dns-interface=eth0
> --foreman-proxy-dns-zone=erased.com
> --foreman-proxy-dns-reverse=50.16.172.in-addr.arpa
> --foreman-proxy-dns-forwarders=172.16.50.14
> --foreman-proxy-dns-forwarders=172.16.10.10
> --foreman-proxy-foreman-base-url=https://mel-prov01.erased.com
> --foreman-proxy-oauth-consumer-key=erased
> --foreman-proxy-oauth-consumer-secret=erased
> When I ran this the dhcp server failed to start because their were no values for the range in /etc/dhcp/dhcpd.conf so I commented them out and it started ok.
>
> /etc/foreman-proxy/dhcp.yml is:
> —
> # Enable DHCP management
> :enabled: true
> # valid vendors:
> # - isc
> # - native_ms (Microsoft native implementation)
> # - virsh (simple implementation for libvirt)
> :dhcp_vendor: isc
> :dhcp_config: /etc/dhcp/dhcpd.conf
> :dhcp_leases: /var/lib/dhcpd/dhcpd.leases
> #:dhcp_key_name: secret_key_name
> #:dhcp_key_secret: secret_key
>
> ls -al /etc/dhcp/
> total 28
> drwxr-xr-x. 3 foreman-proxy foreman-proxy 4096 Oct 14 20:39 .
> drwxr-xr-x. 66 root root 4096 Oct 14 22:04 …
> drwxr-xr-x. 2 root root 4096 Nov 23 2013 dhclient.d
> -rw-r–r--. 1 root root 87 Oct 14 00:25 dhclient-eth0.conf
> -rw-r–r--. 1 root root 193 Nov 23 2013 dhcpd6.conf
> -rw-r–r--. 1 foreman-proxy foreman-proxy 710 Oct 14 18:41 dhcpd.conf
> -rw-r–r--. 1 root root 20 Oct 14 18:11 dhcpd.hosts
>
> I want to provision Centos on vsphere virtual machine using PXE boot.
>
> The problem is that the smart-proxy is not responding to the dhcp request.
> But dhcpd is running.
>
> /var/log/messages contains:
> Oct 14 22:09:28 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 via
> eth0: network 172.16.50.0/24: no free leases
> Oct 14 22:09:30 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 via
> eth0: network 172.16.50.0/24: no free leases
> Oct 14 22:09:34 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 via
> eth0: network 172.16.50.0/24: no free leases
> Oct 14 22:09:42 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 via
> eth0: network 172.16.50.0/24: no free leases
> Oct 14 22:09:46 mel-prov01 dhcpd: DHCPINFORM from 172.16.50.107 via eth0:
> not authoritative for subnet 172.16.50.0
> Oct 14 22:09:58 mel-prov01 dhcpd: DHCPINFORM from 172.16.50.108 via eth0:
> not authoritative for subnet 172.16.50.0
>
> Where is Foreman supposed to put the MAC address and the IP address?
>
> Any idea on what is going wrong?
>
> thanks
>
> Well as you didn't specify a range of dhcp addresses, there are no ip's
> for dhcpd to assign. The foreman uses dynamic ip assignment. It's just as
> the error says "no free leases".
>
> So fill in a range in --foreman-proxy-dhcp-range=" " and everything will
> be fine…
>

When I did this it created a pool of leases. However I was trying to avoid
this. I would prefer to only provide DHCP to specific MAC addresses. As
Foreman asks for the MAC address of the system to be provisioned I assumed
it would make use of that. But I guess it is not currently possible.

··· On Tuesday, 14 October 2014 19:34:02 UTC+11, Jorick Astrego wrote: > On 10/14/2014 05:25 AM, gau...@indoaustinvestments.com > wrote:

Kind regards,

Jorick Astrego
Netbulae

Met vriendelijke groet, With kind regards,
Jorick Astrego

*Netbulae Virtualization Experts *

Tel: 053 20 30 270 in...@netbulae.eu <javascript:> Staalsteden 4-3A KvK
08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW
NL821234584B01

Perhaps I'm missing something here. You do not need to have a range/pool
configured in the dhcp server, only a subnet with appropriate options for
PXE booting. Inside Foreman, each Subnet object can be assigned a range
with the "Start of IP Range" and "End of IP Range" fields. This will allow
either you to specify the IP or Foreman to auto-pick it. Foreman will pass
the static lease to the DHCP server and you should be good to go.

We do not allow any dynamic DHCP leases on data center subnets, so here's
an example of how our functional foreman/dhcp server looks:

allow booting;
allow bootp;
option option-128 code 128 = string;
option option-129 code 129 = text;
next-server 10.10.1.20;
filename "pxelinux.0";

subnet 10.0.10.0 subnet mask 255.255.255.0 {
option routers 10.0.10.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 10.10.1.10, 10.11.1.10;
}

Is that what you're looking for? I didn't use the Foreman installer to
setup my dhcp server though.

··· On Wednesday, October 15, 2014 1:14:04 AM UTC-4, gau...@indoaustinvestments.com wrote: > > > > On Tuesday, 14 October 2014 19:34:02 UTC+11, Jorick Astrego wrote: >> >> >> On 10/14/2014 05:25 AM, gau...@indoaustinvestments.com wrote: >> >> I am new to foreman and having trouble provisioning my first server using >> it. >> >> I am using Foreman 1.6.1 on a clean install of CentOS 6.5 (64 bit). >> >> The install process seemed to go without error using the puppet installer. >> >> I have setup the provisioning configuration. It told me to run the >> following command which I did, >> >> foreman-installer \ >> --enable-foreman-proxy \ >> --foreman-proxy-tftp=true \ >> --foreman-proxy-tftp-servername=172.16.50.250 \ >> --foreman-proxy-dhcp=true \ >> --foreman-proxy-dhcp-interface=eth0 \ >> --foreman-proxy-dhcp-gateway=172.16.50.254 \ >> --foreman-proxy-dhcp-range=" " \ >> --foreman-proxy-dhcp-nameservers="172.16.10.10,172.16.10.14" \ >> --foreman-proxy-dns=true \ >> --foreman-proxy-dns-interface=eth0 \ >> --foreman-proxy-dns-zone=erased.com \ >> --foreman-proxy-dns-reverse=50.16.172.in-addr.arpa \ >> --foreman-proxy-dns-forwarders=172.16.50.14 \ >> --foreman-proxy-dns-forwarders=172.16.10.10 \ >> --foreman-proxy-foreman-base-url=https://mel-prov01.erased.com \ >> --foreman-proxy-oauth-consumer-key=erased \ >> --foreman-proxy-oauth-consumer-secret=erased >> When I ran this the dhcp server failed to start because their were no values for the range in /etc/dhcp/dhcpd.conf so I commented them out and it started ok. >> >> /etc/foreman-proxy/dhcp.yml is: >> --- >> # Enable DHCP management >> :enabled: true >> # valid vendors: >> # - isc >> # - native_ms (Microsoft native implementation) >> # - virsh (simple implementation for libvirt) >> :dhcp_vendor: isc >> :dhcp_config: /etc/dhcp/dhcpd.conf >> :dhcp_leases: /var/lib/dhcpd/dhcpd.leases >> #:dhcp_key_name: secret_key_name >> #:dhcp_key_secret: secret_key >> >> ls -al /etc/dhcp/ >> total 28 >> drwxr-xr-x. 3 foreman-proxy foreman-proxy 4096 Oct 14 20:39 . >> drwxr-xr-x. 66 root root 4096 Oct 14 22:04 .. >> drwxr-xr-x. 2 root root 4096 Nov 23 2013 dhclient.d >> -rw-r--r--. 1 root root 87 Oct 14 00:25 dhclient-eth0.conf >> -rw-r--r--. 1 root root 193 Nov 23 2013 dhcpd6.conf >> -rw-r--r--. 1 foreman-proxy foreman-proxy 710 Oct 14 18:41 dhcpd.conf >> -rw-r--r--. 1 root root 20 Oct 14 18:11 dhcpd.hosts >> >> I want to provision Centos on vsphere virtual machine using PXE boot. >> >> The problem is that the smart-proxy is not responding to the dhcp >> request. But dhcpd is running. >> >> /var/log/messages contains: >> Oct 14 22:09:28 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 via >> eth0: network 172.16.50.0/24: no free leases >> Oct 14 22:09:30 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 via >> eth0: network 172.16.50.0/24: no free leases >> Oct 14 22:09:34 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 via >> eth0: network 172.16.50.0/24: no free leases >> Oct 14 22:09:42 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 via >> eth0: network 172.16.50.0/24: no free leases >> Oct 14 22:09:46 mel-prov01 dhcpd: DHCPINFORM from 172.16.50.107 via eth0: >> not authoritative for subnet 172.16.50.0 >> Oct 14 22:09:58 mel-prov01 dhcpd: DHCPINFORM from 172.16.50.108 via eth0: >> not authoritative for subnet 172.16.50.0 >> >> Where is Foreman supposed to put the MAC address and the IP address? >> >> Any idea on what is going wrong? >> >> thanks >> >> Well as you didn't specify a range of dhcp addresses, there are no ip's >> for dhcpd to assign. The foreman uses dynamic ip assignment. It's just as >> the error says "no free leases". >> >> So fill in a range in --foreman-proxy-dhcp-range=" " and everything will >> be fine.... >> > > When I did this it created a pool of leases. However I was trying to avoid > this. I would prefer to only provide DHCP to specific MAC addresses. As > Foreman asks for the MAC address of the system to be provisioned I assumed > it would make use of that. But I guess it is not currently possible. > >> >> Kind regards, >> >> Jorick Astrego >> Netbulae >> >> >> >> Met vriendelijke groet, With kind regards, >> Jorick Astrego >> >> *Netbulae Virtualization Experts * >> ------------------------------ >> Tel: 053 20 30 270 in...@netbulae.eu Staalsteden 4-3A KvK 08198180 Fax: >> 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01 >> ------------------------------ >> >>

Make use of classes and match against the MAC address pool that you use.
I use such a construct to assign only dhcp leases to oVirt MAC addresses.

Joop

··· On 15-10-2014 7:14, gaumann@indoaustinvestments.com wrote: > > > When I did this it created a pool of leases. However I was trying to > avoid this. I would prefer to only provide DHCP to specific MAC > addresses. As Foreman asks for the MAC address of the system to be > provisioned I assumed it would make use of that. But I guess it is not > currently possible. >

Currently I have a DIY provisioning system, i.e. manual setup of dhcp
server, tftp server and http serving of repositories. But it is a lot of
work to manage it so I want to switch to The Foreman. My problem is I don't
know how to configure something resembling my current setup in Foreman
rather than manually editing the dhcpd.conf file. I have included relevant
bits of my dhcpd.conf file from my DIY setup below:
allow booting;
allow bootp;

Standard configuration directives…

option domain-name "erased.com";
option broadcast-address 172.16.50.255;
option domain-name-servers 172.16.10.10, 172.16.10.14;
option routers 172.16.50.254;
max-lease-time 86400;

subnet 172.16.50.0 netmask 255.255.255.0 {
pool {
max-lease-time 86400;
range 172.16.50.100 172.16.50.120;
allow unknown-clients;
}
}

Group the PXE bootable hosts together

group {
# PXE-specific configuration directives…
next-server 172.16.50.3;
filename "pxelinux.0";
deny unknown-clients;

# You need an entry like this for every host
# unless you&#39;re using dynamic addresses
host test-1 {
    hardware ethernet 00:25:90:4f:18:2e;
    fixed-address 172.16.50.14;
}

host test-2 {
    hardware ethernet 00:25:90:4f:18:2f;
    fixed-address 172.16.50.15;
}

}

This services DHCP requests from both servers that I want to PXE boot.
Servers only get PXE boot information if I have specified their MAC
address. I also need to serve DHCP leases to other servers in the subnet
from a pool. These should not get PXE boot information in the DHCP
response. Note that the IP addresses used for PXE booting the test-1 and 2
servers are not in the pool and once these servers are stood up they will
be setup with static IP addresses and not use the DHCP server.

So my questions are can I configure this in Foreman 1.6.1 through the web
interface or do I need to edit the dhcpd.conf file manually? If I can set
it up through the GUI how do I do it as it isn't jumping out at me.

Joop's answer above to user classes sounds like it might be what I want but
as I am new to Foreman I need a bit more detail.

thanks to those who have taken the time to respond
Greg

··· On Thursday, 16 October 2014 01:02:14 UTC+11, Sean Alderman wrote: > > Perhaps I'm missing something here. You do not need to have a range/pool > configured in the dhcp server, only a subnet with appropriate options for > PXE booting. Inside Foreman, each Subnet object can be assigned a range > with the "Start of IP Range" and "End of IP Range" fields. This will allow > either you to specify the IP or Foreman to auto-pick it. Foreman will pass > the static lease to the DHCP server and you should be good to go. > > We do not allow any dynamic DHCP leases on data center subnets, so here's > an example of how our functional foreman/dhcp server looks: > > allow booting; > allow bootp; > option option-128 code 128 = string; > option option-129 code 129 = text; > next-server 10.10.1.20; > filename "pxelinux.0"; > > subnet 10.0.10.0 subnet mask 255.255.255.0 { > option routers 10.0.10.1; > option subnet-mask 255.255.255.0; > option domain-name-servers 10.10.1.10, 10.11.1.10; > } > > Is that what you're looking for? I didn't use the Foreman installer to > setup my dhcp server though. > > On Wednesday, October 15, 2014 1:14:04 AM UTC-4, > gau...@indoaustinvestments.com wrote: >> >> >> >> On Tuesday, 14 October 2014 19:34:02 UTC+11, Jorick Astrego wrote: >>> >>> >>> On 10/14/2014 05:25 AM, gau...@indoaustinvestments.com wrote: >>> >>> I am new to foreman and having trouble provisioning my first server >>> using it. >>> >>> I am using Foreman 1.6.1 on a clean install of CentOS 6.5 (64 bit). >>> >>> The install process seemed to go without error using the puppet >>> installer. >>> >>> I have setup the provisioning configuration. It told me to run the >>> following command which I did, >>> >>> foreman-installer \ >>> --enable-foreman-proxy \ >>> --foreman-proxy-tftp=true \ >>> --foreman-proxy-tftp-servername=172.16.50.250 \ >>> --foreman-proxy-dhcp=true \ >>> --foreman-proxy-dhcp-interface=eth0 \ >>> --foreman-proxy-dhcp-gateway=172.16.50.254 \ >>> --foreman-proxy-dhcp-range=" " \ >>> --foreman-proxy-dhcp-nameservers="172.16.10.10,172.16.10.14" \ >>> --foreman-proxy-dns=true \ >>> --foreman-proxy-dns-interface=eth0 \ >>> --foreman-proxy-dns-zone=erased.com \ >>> --foreman-proxy-dns-reverse=50.16.172.in-addr.arpa \ >>> --foreman-proxy-dns-forwarders=172.16.50.14 \ >>> --foreman-proxy-dns-forwarders=172.16.10.10 \ >>> --foreman-proxy-foreman-base-url=https://mel-prov01.erased.com \ >>> --foreman-proxy-oauth-consumer-key=erased \ >>> --foreman-proxy-oauth-consumer-secret=erased >>> When I ran this the dhcp server failed to start because their were no values for the range in /etc/dhcp/dhcpd.conf so I commented them out and it started ok. >>> >>> /etc/foreman-proxy/dhcp.yml is: >>> --- >>> # Enable DHCP management >>> :enabled: true >>> # valid vendors: >>> # - isc >>> # - native_ms (Microsoft native implementation) >>> # - virsh (simple implementation for libvirt) >>> :dhcp_vendor: isc >>> :dhcp_config: /etc/dhcp/dhcpd.conf >>> :dhcp_leases: /var/lib/dhcpd/dhcpd.leases >>> #:dhcp_key_name: secret_key_name >>> #:dhcp_key_secret: secret_key >>> >>> ls -al /etc/dhcp/ >>> total 28 >>> drwxr-xr-x. 3 foreman-proxy foreman-proxy 4096 Oct 14 20:39 . >>> drwxr-xr-x. 66 root root 4096 Oct 14 22:04 .. >>> drwxr-xr-x. 2 root root 4096 Nov 23 2013 dhclient.d >>> -rw-r--r--. 1 root root 87 Oct 14 00:25 dhclient-eth0.conf >>> -rw-r--r--. 1 root root 193 Nov 23 2013 dhcpd6.conf >>> -rw-r--r--. 1 foreman-proxy foreman-proxy 710 Oct 14 18:41 dhcpd.conf >>> -rw-r--r--. 1 root root 20 Oct 14 18:11 dhcpd.hosts >>> >>> I want to provision Centos on vsphere virtual machine using PXE boot. >>> >>> The problem is that the smart-proxy is not responding to the dhcp >>> request. But dhcpd is running. >>> >>> /var/log/messages contains: >>> Oct 14 22:09:28 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 >>> via eth0: network 172.16.50.0/24: no free leases >>> Oct 14 22:09:30 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 >>> via eth0: network 172.16.50.0/24: no free leases >>> Oct 14 22:09:34 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 >>> via eth0: network 172.16.50.0/24: no free leases >>> Oct 14 22:09:42 mel-prov01 dhcpd: DHCPDISCOVER from 00:50:56:ba:30:84 >>> via eth0: network 172.16.50.0/24: no free leases >>> Oct 14 22:09:46 mel-prov01 dhcpd: DHCPINFORM from 172.16.50.107 via >>> eth0: not authoritative for subnet 172.16.50.0 >>> Oct 14 22:09:58 mel-prov01 dhcpd: DHCPINFORM from 172.16.50.108 via >>> eth0: not authoritative for subnet 172.16.50.0 >>> >>> Where is Foreman supposed to put the MAC address and the IP address? >>> >>> Any idea on what is going wrong? >>> >>> thanks >>> >>> Well as you didn't specify a range of dhcp addresses, there are no ip's >>> for dhcpd to assign. The foreman uses dynamic ip assignment. It's just as >>> the error says "no free leases". >>> >>> So fill in a range in --foreman-proxy-dhcp-range=" " and everything will >>> be fine.... >>> >> >> When I did this it created a pool of leases. However I was trying to >> avoid this. I would prefer to only provide DHCP to specific MAC addresses. >> As Foreman asks for the MAC address of the system to be provisioned I >> assumed it would make use of that. But I guess it is not currently possible. >> >>> >>> Kind regards, >>> >>> Jorick Astrego >>> Netbulae >>> >>> >>> >>> Met vriendelijke groet, With kind regards, >>> Jorick Astrego >>> >>> *Netbulae Virtualization Experts * >>> ------------------------------ >>> Tel: 053 20 30 270 in...@netbulae.eu Staalsteden 4-3A KvK 08198180 Fax: >>> 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01 >>> ------------------------------ >>> >>>

interface are puppet classes and I suspect they are not what I want as it
seems to me puppet doesn't come into the picture until after the OS is
installed. Can you be a bit more specific about how to set this up.

thanks
Greg

··· On Wednesday, 15 October 2014 18:18:13 UTC+11, jvandewege wrote: > > On 15-10-2014 7:14, gau...@indoaustinvestments.com wrote: > > > > > > When I did this it created a pool of leases. However I was trying to > > avoid this. I would prefer to only provide DHCP to specific MAC > > addresses. As Foreman asks for the MAC address of the system to be > > provisioned I assumed it would make use of that. But I guess it is not > > currently possible. > > > Make use of classes and match against the MAC address pool that you use. > I use such a construct to assign only dhcp leases to oVirt MAC addresses. > > This may be what I want. The only classes I can find in the Foreman web