Here’s the code it’s gacking on… (from isc.rb @ line 26)
def addRecord options = {}
record = super(options)
omcmd "connect"
omcmd "set name = \"#{record.name}\""
omcmd "set ip-address = #{record.ip}"
omcmd "set hardware-address = #{record.mac}"
omcmd "set hardware-type = 1" # This is ethernet
options = record.options
# TODO: Extract this block into a generic dhcp options helper
statements = []
statements << "filename = \\\"#{options[:filename]}\\\";" if options[:filename]
statements << bootServer(options[:nextServer]) if options[:nextServer]
statements << "option host-name = \\\"#{record.name}\\\";" if record.name
omcmd "set statements = \"#{statements.join(" ")}\"" unless statements.empty?
omcmd "create"
omcmd("disconnect", "Added DHCP reservation for #{record}")
record
end
The options are being grabbed from the parent I guess - I’m not a ruby guy, but it would still seem like I can’t see what it’s actually trying to pass to omshell. I was hoping if I could figure that out I might be able to determine what I need in the server config to make it work.
On Tuesday, August 20, 2013 4:28:46 PM UTC-4, Sean Alderman wrote:
Yeah, the paste I linked to above is from the foreman-proxy/proxy.log file in debug mode.
I’m wondering if the smart-proxy writing to the config file is the issue. I’ve got Foreman/Puppet managing all my smart-proxy servers…dhcpd is one of the services puppet is managing. I version control the dhcpd.conf files in a “site” module and the dhcp module sources the for the given hostname. Currently I’ve only got two smart proxies - the one on my foreman server, and the one on this secure build network.
I’ll have to stop puppet, reconfig the permissions on the file let foreman do its thing and see what changes.
Thanks.
On Tuesday, August 20, 2013 4:09:30 PM UTC-4, lu...@kearney.jp wrote:
Hello,
If you have not done anything terribly exotic I think you’ll find the logs for the smart proxy in /var/log/foreman-proxy and they can be pretty verbose. One thing that has tripped me up with smart proxies is making sure that the foreman-proxy user is part of a group that has rights to read the dhcpd config and write to it.
Thanks
On Aug 21, 2013, at 5:02 AM, Sean Alderman salde...@udayton.edu wrote:
I understand that the smart-proxy adds leases to the file via omapi, but is there a way to see exactly what the smart proxy is trying to do? I mean it’s clear I don’t have my dhcp server configured just right for SPARC + X86 unattended installs, but I’d like to see what the host reservation its trying to configure in the leases file looks like. I’ve got the proxy on debug level, but that doesn’t actually show what its doing, just how what it did ended.
On Tuesday, August 20, 2013 3:16:18 PM UTC-4, Sean Alderman wrote:
I’m running dhcp-4.1.1-34 on OracleLinux 6.4.
Do you have those SUNW space options in your subnet declaration as well, but with specific values for that subnet?
I’m looking at our AI server on a different subnet and it’s got:
subnet a.b.c.d netmask 255.255.255.0 {
option routers a.b.c.1;
option subnet-mask 255.255.255.0;
option domain-name-servers w.x.y.z, s.t.u.v;
vendor-option-space SUNW;
option SUNW.SrootIP4 ;
option SUNW.SrootNM ;
option SUNW.SrootPTH ;
option SUNW.SinstIP4 ;
option SUNW.SinstNM ;
option SUNW.SinstPTH ;
option SUNW.SjumpsCF ;
}
On Friday, August 16, 2013 5:40:13 PM UTC-4, lu...@kearney.jp wrote:
Ooops I meant which version of dhcpd?
On Aug 17, 2013, at 6:38 AM, Luke Kearney lu...@kearney.jp wrote:
Hello,
Not sure that this will help you all that much but these are the vendor options I have to get solaris to jumpstart
option space SUNW;
option SUNW.root-mount-options code 1 = text;
option SUNW.root-server-ip-address code 2 = ip-address;
option SUNW.root-server-hostname code 3 = text;
option SUNW.root-path-name code 4 = text;
option SUNW.swap-server-ip-address code 5 = ip-address;
option SUNW.swap-file-path code 6 = text;
option SUNW.boot-file-path code 7 = text;
option SUNW.posix-timezone-string code 8 = text;
option SUNW.boot-read-size code 9 = unsigned integer 16;
option SUNW.install-server-ip-address code 10 = ip-address;
option SUNW.install-server-hostname code 11 = text;
option SUNW.install-path code 12 = text;
option SUNW.sysid-config-file-server code 13 = text;
option SUNW.JumpStart-server code 14 = text;
option SUNW.terminal-name code 15 = text;
option SUNW.SbootURI code 16 = text;
my environment is all x86 so ymmv with sparc but the error message in paste bin suggests your dhcp implementation is missing something - which distribution/version of bind do you have running?
hth
lukek
On Aug 17, 2013, at 6:23 AM, Sean Alderman salde...@udayton.edu wrote:
Greetings,
I’m working on building unattended installs for Solaris in v1.2. When I create a SPARC host in Foreman, I get a 400 error in Foreman and the Smary Proxy shows this paste in its log:
http://pastebin.com/wHzT6WNc
I’ve tried a couple of different DHCP configurations to enable jumpstart from a Linux ISC dhcpd host (which runs smart-proxy) but none of them seem to work. There isn’t any specific info on configuring DHCP in the Solaris Unattended Wiki, and I’m really not sure where to go from here.
Your thoughts and comments are much appreciated. Kind regards,
Sean
–
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.
–
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.
–
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.
–
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.
