Subnet not found

Thanks for the clarification. Has there been much interest in managing this
component dynamically or am I the first? After manually adding the subnet,
I achieve the desired result. This does however limit the ability to be
ready to go after adding a new subnet. In a service provider environment,
we have many subnets and I was hopeful that Foreman would take care of this
work in part of maintaining the subnet definitions.

Regards,
James

··· On Wednesday, June 12, 2013 12:08:08 AM UTC-4, ja...@atlanticmetro.net wrote: > > Hello all, > > I am looking for some help with getting Foreman's DHCP linkage > functioning. I've got a fresh Ubuntu precise box with foreman installed > using the release candidate. I used the deb package method with 'precise > rc', and then ran through the foreman install in quick and simple 'yes' > mode. > > > I have the foreman-proxy set up for dhcp and ISC DHCP installed and > running. I have a basic subnet declaration to allow dhcpd to actually > start. Its my understanding that foreman will use omshell/omapi to interact > with DHCPd to add Subnets that are defined within foreman to DHCP. Whenever > making any changes modifications to a host's subnet setting, I'm getting > log entries with failures. I've got a dhcp helper set up on different > subnet pointing through to this box. I see the DHCP request hit the box but > there is no scope for it to issue PXE boot. > > Log File (production.log): > > Failed to fetch a free IP from our proxy: 404 Resource Not Found: Subnet > 208.78.27.0 not found > > foreman-proxy.log > D, [2013-06-11T23:56:04.025315 #2368] DEBUG -- : Reading config file > /etc/dhcp/dhcpd.conf > D, [2013-06-11T23:56:04.025649 #2368] DEBUG -- : Loading subnets for > 127.0.0.1 > D, [2013-06-11T23:56:04.025903 #2368] DEBUG -- : Added > 10.250.50.0/255.255.255.0 to 127.0.0.1 > E, [2013-06-11T23:56:04.026293 #2368] ERROR -- : Subnet 208.78.27.0 not > found > > When defining subnets and such, there are no odd log events > > Config: > > dhcpd.conf > > omapi-port 7911; > key omapi_key { > algorithm HMAC-MD5; > secret ""; > }; > omapi-key omapi_key; > ddns-update-style interim; > ignore client-updates; > authoritative; > allow booting; > allow bootp; > option domain-name "amc.local"; > option domain-name-servers 10.250.50.134, 208.78.27.4; > default-lease-time 600; > max-lease-time 7200; > log-facility local7; > > # eth0 subnet > subnet 10.250.50.0 netmask 255.255.255.0 { > } > > > foreman-proxy.conf dhcp section > :dhcp: true > :dhcp_vendor: isc > :dhcp_config: /etc/dhcp/dhcpd.conf > :dhcp_leases: /var/lib/dhcp/dhcpd.leases > > :dhcp_key_name: omapi-key > :dhcp_key_secret: "" > :omapi_key: "" > > ** note, I wasnt able to find a clear answer on which of these methods is > proper for the omapi key so I have both defined > > Any ideas welcome. Thanks >

>
> Thanks for the clarification. Has there been much interest in managing
> this component dynamically or am I the first? After manually adding the
> subnet, I achieve the desired result. This does however limit the ability
> to be ready to go after adding a new subnet. In a service provider
> environment, we have many subnets and I was hopeful that Foreman would take
> care of this work in part of maintaining the subnet definitions.

A few people use foreman api within puppet (like [1]) so they could put
down the relevant zone settings,

Ohad

[1]

··· On Thu, Jun 13, 2013 at 12:12 AM, wrote:

Regards,
James

On Wednesday, June 12, 2013 12:08:08 AM UTC-4, ja…@atlanticmetro.netwrote:

Hello all,

I am looking for some help with getting Foreman’s DHCP linkage
functioning. I’ve got a fresh Ubuntu precise box with foreman installed
using the release candidate. I used the deb package method with ‘precise
rc’, and then ran through the foreman install in quick and simple ‘yes’
mode.

I have the foreman-proxy set up for dhcp and ISC DHCP installed and
running. I have a basic subnet declaration to allow dhcpd to actually
start. Its my understanding that foreman will use omshell/omapi to interact
with DHCPd to add Subnets that are defined within foreman to DHCP. Whenever
making any changes modifications to a host’s subnet setting, I’m getting
log entries with failures. I’ve got a dhcp helper set up on different
subnet pointing through to this box. I see the DHCP request hit the box but
there is no scope for it to issue PXE boot.

Log File (production.log):

Failed to fetch a free IP from our proxy: 404 Resource Not Found: Subnet
208.78.27.0 not found

foreman-proxy.log
D, [2013-06-11T23:56:04.025315 #2368] DEBUG – : Reading config file
/etc/dhcp/dhcpd.conf
D, [2013-06-11T23:56:04.025649 #2368] DEBUG – : Loading subnets for
127.0.0.1
D, [2013-06-11T23:56:04.025903 #2368] DEBUG – : Added
10.250.50.0/255.255.255.0 to 127.0.0.1
E, [2013-06-11T23:56:04.026293 #2368] ERROR – : Subnet 208.78.27.0 not
found

When defining subnets and such, there are no odd log events

Config:

dhcpd.conf

omapi-port 7911;
key omapi_key {
algorithm HMAC-MD5;
secret “”;
};
omapi-key omapi_key;
ddns-update-style interim;
ignore client-updates;
authoritative;
allow booting;
allow bootp;
option domain-name “amc.local”;
option domain-name-servers 10.250.50.134, 208.78.27.4;
default-lease-time 600;
max-lease-time 7200;
log-facility local7;

eth0 subnet

subnet 10.250.50.0 netmask 255.255.255.0 {
}

foreman-proxy.conf dhcp section
:dhcp: true
:dhcp_vendor: isc
:dhcp_config: /etc/dhcp/dhcpd.conf
:dhcp_leases: /var/lib/dhcp/dhcpd.leases

:dhcp_key_name: omapi-key
:dhcp_key_secret: “”
:omapi_key: “”

** note, I wasnt able to find a clear answer on which of these methods is
proper for the omapi key so I have both defined

Any ideas welcome. Thanks


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 http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

You could build on top of the dhcp module we supply, as the module
provides a defined type for a pool:

I suspect you'd need to create a new function based on the foreman()
function (which is in the puppet-foreman module), but it could then call
create_resources() in Puppet to create new dhcp::pool resources, which
would automatically add new sections to dhcpd.conf.

Patches would be very welcome to the installer if you're up for tackling
this.

··· On 13/06/13 02:46, Ohad Levy wrote: > > > On Thu, Jun 13, 2013 at 12:12 AM, > wrote: > > > Thanks for the clarification. Has there been much interest in > managing this component dynamically or am I the first? After > manually adding the subnet, I achieve the desired result. This does > however limit the ability to be ready to go after adding a new > subnet. In a service provider environment, we have many subnets and > I was hopeful that Foreman would take care of this work in part of > maintaining the subnet definitions. > > > A few people use foreman api within puppet (like [1]) so they could put > down the relevant zone settings, > > Ohad > > [1] > http://blog.theforeman.org/2012/01/getting-foreman-search-results-into.html


Dominic Cleal
Red Hat Engineering