Smart_Proxy : Unable to find the DHCP configuration or lease files

Hi All,

iam new to foreman , configured external dhcp server under smart_proxy (
instructions followed from
ISC DHCP - Smart Proxy - Foreman)
Foreman is not suggesting the ip address while creating the vm and also not
able to provision with tftp.

please find the following smart_proxy settings and error messages, kindly
suggest.

[root@foreman ~]# more /etc/foreman-proxy/settings.yml |grep ^:
:ssl_ca_file: /var/lib/puppet/ssl/certs/ca.pem
:ssl_certificate: /var/lib/puppet/ssl/certs/foreman.uk.specsavers.com.pem
:ssl_private_key:
/var/lib/puppet/ssl/private_keys/foreman.uk.specsavers.com.pem
:daemon: true
:daemon_pid: /var/run/foreman-proxy/foreman-proxy.pid
:port: 8443
:tftp: true
:tftproot: /var/lib/tftpboot/
:dhcp: true
:dhcp_vendor: isc
:dhcp_config: /etc/dhcpd.conf
:dhcp_leases: /var/lib/dhcpd/dhcpd.leases
:puppetca: true
:ssldir: /var/lib/puppet/ssl
:puppetdir: /etc/puppet
:puppet: true
:puppet_conf: /etc/puppet/puppet.conf
:log_file: /var/log/foreman-proxy/proxy.log

E, [2013-07-29T23:27:53.253261 #24749] ERROR – : Unable to find the DHCP
configuration or lease files

Hi,

foreman-proxy user not existed on dhcp server, from the server side we have
global read permissions for two files.

quick question, is the dhcp server should run on foreman server ?

Regards,
Mahesh K

··· On Tuesday, July 30, 2013 4:43:48 PM UTC+1, mahesh k wrote: > > Hi All, > > iam new to foreman , configured external dhcp server under smart_proxy ( > instructions followed from > http://projects.theforeman.org/projects/smart-proxy/wiki/ISC_DHCP) > Foreman is not suggesting the ip address while creating the vm and also > not able to provision with tftp. > > please find the following smart_proxy settings and error messages, kindly > suggest. > > [root@foreman ~]# more /etc/foreman-proxy/settings.yml |grep ^: > :ssl_ca_file: /var/lib/puppet/ssl/certs/ca.pem > :ssl_certificate: /var/lib/puppet/ssl/certs/foreman.uk.specsavers.com.pem > :ssl_private_key: > /var/lib/puppet/ssl/private_keys/foreman.uk.specsavers.com.pem > :daemon: true > :daemon_pid: /var/run/foreman-proxy/foreman-proxy.pid > :port: 8443 > :tftp: true > :tftproot: /var/lib/tftpboot/ > :dhcp: true > :dhcp_vendor: isc > :dhcp_config: /etc/dhcpd.conf > :dhcp_leases: /var/lib/dhcpd/dhcpd.leases > :puppetca: true > :ssldir: /var/lib/puppet/ssl > :puppetdir: /etc/puppet > :puppet: true > :puppet_conf: /etc/puppet/puppet.conf > :log_file: /var/log/foreman-proxy/proxy.log > > > *E, [2013-07-29T23:27:53.253261 #24749] ERROR -- : Unable to find the > DHCP configuration or lease files* > >

What are permissions on the files and directories, including all
parent directories, of the files referenced in dhcp_config and
dhcp_leases? Ensure that the foreman-proxy user can read them.

··· On 30/07/13 16:43, mahesh k wrote: > :dhcp_config: /etc/dhcpd.conf > :dhcp_leases: /var/lib/dhcpd/dhcpd.leases > :puppetca: true > :ssldir: /var/lib/puppet/ssl > :puppetdir: /etc/puppet > :puppet: true > :puppet_conf: /etc/puppet/puppet.conf > :log_file: /var/log/foreman-proxy/proxy.log > > > *E, [2013-07-29T23:27:53.253261 #24749] ERROR -- : Unable to find the > DHCP configuration or lease files*


Dominic Cleal
Red Hat Engineering

Hi all,

We are planning to implement foreman with rhev, we are able to provision
the box by using the rhev templates, but ip and the host name is diff than
what we are giving in the foreman portal.

We are already having dhcp server in our network, can i use the same dhcp
server for provisioning ? if yes, can someone please provide the steps to
add dhcp service in foreman-proxy.

We are planning to prevision the server by using rhev template (base os )
and planning to apply the additional software's with puppet. Hope this can
be done with foreman, please suggest.

Regards.
Mahesh K

> Hi all,
>
> We are planning to implement foreman with rhev, we are able to provision
> the box by using the rhev templates, but ip and the host name is diff than
> what we are giving in the foreman portal.
>
I could assume that you either have one of the following

  • the network in foreman and in rhev do not match.
  • you are booting off the template instead of pxe booting… if you boot
    via the template, it really depends on what inside the template.

>
>
> We are already having dhcp server in our network, can i use the same dhcp
> server for provisioning ? if yes, can someone please provide the steps to
> add dhcp service in foreman-proxy.
>
did you follow the quick start guides from youtube? sometimes its useful to
set a reference setup (e.g. via the installer) and just compare the
settings… overall you would need to:

  1. install a smart proxy on your dhcp server
  2. grant it permissions to read the config and lease files.
  3. setup omapi (or alllow it for localhost) so that we can update the dhcp
    server.
··· On Wed, Jul 31, 2013 at 1:28 AM, wrote:

We are planning to prevision the server by using rhev template (base os )
and planning to apply the additional software’s with puppet. Hope this can
be done with foreman, please suggest.

Regards.
Mahesh K


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.
For more options, visit https://groups.google.com/groups/opt_out.

  1. install a smart proxy on your dhcp server

We appended *omapi-port 7911; *to the dhcpd.conf on dhcp server, no more
changes. Can you please suggest how to install smart proxy on dhcp server.

  1. grant it permissions to read the config and lease files.

hope after installing smart-proxy 744 permissions for both dhcp.conf and
dhcp.leases
files may work.

  1. setup omapi (or alllow it for localhost) so that we can update the dhcp
    server.

We did only this setup (i.e *omapi-port 7911; appended in dhcpd.conf file).

Can you please suggest how to install smart-proxy on dhcp server.

··· *

On Wednesday, 31 July 2013 07:18:05 UTC+1, ohad wrote:

On Wed, Jul 31, 2013 at 1:28 AM, <mahesh.k...@specsavers.com <javascript:> > > wrote:

Hi all,

We are planning to implement foreman with rhev, we are able to provision
the box by using the rhev templates, but ip and the host name is diff than
what we are giving in the foreman portal.

I could assume that you either have one of the following

  • the network in foreman and in rhev do not match.
  • you are booting off the template instead of pxe booting… if you boot
    via the template, it really depends on what inside the template.

We are already having dhcp server in our network, can i use the same dhcp
server for provisioning ? if yes, can someone please provide the steps to
add dhcp service in foreman-proxy.

did you follow the quick start guides from youtube? sometimes its useful
to set a reference setup (e.g. via the installer) and just compare the
settings… overall you would need to:

  1. install a smart proxy on your dhcp server
  2. grant it permissions to read the config and lease files.
  3. setup omapi (or alllow it for localhost) so that we can update the dhcp
    server.

We are planning to prevision the server by using rhev template (base os )
and planning to apply the additional software’s with puppet. Hope this can
be done with foreman, please suggest.

Regards.
Mahesh K


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-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com<javascript:>
.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Can anyone please suggest for following…

··· On Wednesday, 31 July 2013 08:56:11 UTC+1, mahesh.k...@specsavers.com wrote: > > 1. install a smart proxy on your dhcp server > > We appended *omapi-port 7911; *to the dhcpd.conf on dhcp server, no more > changes. Can you please suggest how to install smart proxy on dhcp server. > > 2. grant it permissions to read the config and lease files. > > hope after installing smart-proxy global read permissions for both *dhcp.conf > and dhcp.leases* files may work. > > 3. setup omapi (or alllow it for localhost) so that we can update the dhcp > server. > > We appended only (i.e *omapi-port 7911; appended in dhcpd.conf file). > > > > Can you please suggest how to install smart-proxy on dhcp server. > * > > > > > > > > On Wednesday, 31 July 2013 07:18:05 UTC+1, ohad wrote: >> >> >> >> On Wed, Jul 31, 2013 at 1:28 AM, wrote: >> >>> Hi all, >>> >>> We are planning to implement foreman with rhev, we are able to provision >>> the box by using the rhev templates, but ip and the host name is diff than >>> what we are giving in the foreman portal. >>> >> I could assume that you either have one of the following >> - the network in foreman and in rhev do not match. >> - you are booting off the template instead of pxe booting... if you boot >> via the template, it really depends on what inside the template. >> >>> >>> >>> We are already having dhcp server in our network, can i use the same >>> dhcp server for provisioning ? if yes, can someone please provide the steps >>> to add dhcp service in foreman-proxy. >>> >> did you follow the quick start guides from youtube? sometimes its useful >> to set a reference setup (e.g. via the installer) and just compare the >> settings.. overall you would need to: >> 1. install a smart proxy on your dhcp server >> 2. grant it permissions to read the config and lease files. >> 3. setup omapi (or alllow it for localhost) so that we can update the >> dhcp server. >> >>> >>> We are planning to prevision the server by using rhev template (base os >>> ) and planning to apply the additional software's with puppet. Hope this >>> can be done with foreman, please suggest. >> >> >>> >>> Regards. >>> Mahesh K >>> >>> -- >>> 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-user...@googlegroups.com. >>> To post to this group, send email to forema...@googlegroups.com. >>> Visit this group at http://groups.google.com/group/foreman-users. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >>