Running through a foreman POC and playing with discovery. I went through
the install/config docs for enabled discovery on the smart proxy. When I
refreshed the smart proxy, Discovery appeared but DHCP disappeared from the
feature list. Is this expected?
No, something happened to DHCP module, check proxy.log and look into
initialization phase.
Typically, when you perform upgrade of dhcp or tftp daemons (via
yum/apt), they will reset permissions on some files or directories
which will cause DHCP module to fail to init. This will fix it:
setfacl -R -m u:foreman-proxy:rwx /etc/dhcp/ /var/lib/dhcpd/ /var/lib/tftpboot
I think our develop branch installer will do this already so this
mis-behavior will disappear in 1.16+.
LZ
···
On Wed, Oct 11, 2017 at 3:19 AM, Charlie Baum wrote: > Running through a foreman POC and playing with discovery. I went through > the install/config docs for enabled discovery on the smart proxy. When I > refreshed the smart proxy, Discovery appeared but DHCP disappeared from the > feature list. Is this expected? > > -- > 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 https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.–
Later,
Lukas @lzap Zapletal
Proxy.log is showing this:
Disabling all modules in the group ['dhcp'] due to a failure in one of
them: (<unknown>): did not find expected key while parsing a block mapping
at line 4 column 1
Not sure how to track that one down.
···
On Wednesday, October 11, 2017 at 4:47:07 AM UTC-4, Lukas Zapletal wrote: > > No, something happened to DHCP module, check proxy.log and look into > initialization phase. > > Typically, when you perform upgrade of dhcp or tftp daemons (via > yum/apt), they will reset permissions on some files or directories > which will cause DHCP module to fail to init. This will fix it: > > setfacl -R -m u:foreman-proxy:rwx /etc/dhcp/ /var/lib/dhcpd/ > /var/lib/tftpboot > > I think our develop branch installer will do this already so this > mis-behavior will disappear in 1.16+. > > LZ > > On Wed, Oct 11, 2017 at 3:19 AM, Charlie Baum > wrote: > > Running through a foreman POC and playing with discovery. I went > through > > the install/config docs for enabled discovery on the smart proxy. When > I > > refreshed the smart proxy, Discovery appeared but DHCP disappeared from > the > > feature list. Is this expected? > > > > -- > > 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 https://groups.google.com/group/foreman-users. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > Later, > Lukas @lzap Zapletal >We have recently rewritten the DHCP conf parser and it looks like a
parser error. Please file a bug on smart-proxy component DHCP and if
possible include the configuration (dhcpd.conf and all included files
from there).
LZ
···
On Wed, Oct 11, 2017 at 4:53 PM, Charlie Baum wrote: > Proxy.log is showing this: > > Disabling all modules in the group ['dhcp'] due to a failure in one of them: > (): did not find expected key while parsing a block mapping at line > 4 column 1 > > > Not sure how to track that one down. > > On Wednesday, October 11, 2017 at 4:47:07 AM UTC-4, Lukas Zapletal wrote: >> >> No, something happened to DHCP module, check proxy.log and look into >> initialization phase. >> >> Typically, when you perform upgrade of dhcp or tftp daemons (via >> yum/apt), they will reset permissions on some files or directories >> which will cause DHCP module to fail to init. This will fix it: >> >> setfacl -R -m u:foreman-proxy:rwx /etc/dhcp/ /var/lib/dhcpd/ >> /var/lib/tftpboot >> >> I think our develop branch installer will do this already so this >> mis-behavior will disappear in 1.16+. >> >> LZ >> >> On Wed, Oct 11, 2017 at 3:19 AM, Charlie Baum wrote: >> > Running through a foreman POC and playing with discovery. I went >> > through >> > the install/config docs for enabled discovery on the smart proxy. When >> > I >> > refreshed the smart proxy, Discovery appeared but DHCP disappeared from >> > the >> > feature list. Is this expected? >> > >> > -- >> > 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 https://groups.google.com/group/foreman-users. >> > For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> Later, >> Lukas @lzap Zapletal > > -- > 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 https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.–
Later,
Lukas @lzap Zapletal