Home · About · Download · Documentation · Getting Help · Google+

Ticket #46 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

dhcpd on sl6 chokes on dhcpd.conf

Reported by: fernsler Owned by: fernsler
Priority: minor Milestone:
Component: provision Version: 0.1
Keywords: Cc: kmfernsler@…, gmkurtzer@…

Description

Ok, it was probably something silly that I did, like try to name a host n0000.something. Doing that using wwsh, the dhpcd.conf template gets written out, but when it tries to start dhcpd, it fails to start because of a syntax error parsing the "." in "n0000.something".

It is ok if I put the hostname in quotes.

Do we want to put the quotes in by default, pitch the hostname option, something else, or none of the above?

Change History

comment:1 Changed 6 years ago by fernsler

... or maybe just document the wwsh command node new "n0000.something" in the documentation, because it works just dandy if you do that.

Actually, I lie. Starting from scratch with a fresh install/db running

node new "n0000.phoenix" --netdev=eth0 --ipaddr=10.0.1.0 --hwaddr=00:1E:68:2F:4B:0E

in wwsh produces the stanza:

# Node entries will follow below

group {

host "n0000.phoenix"-eth0 {

option host-name "n0000.phoenix";
hardware ethernet 00:1e:68:2f:4b:0e;
fixed-address 10.0.1.0;

}

Trying start dhcpd on that:

/etc/dhcp/dhcpd.conf line 20: expecting a name for host declaration.

host "n0000.phoenix"


Configuration file errors encountered -- exiting

Last edited 6 years ago by fernsler (previous) (diff)

comment:2 Changed 6 years ago by fernsler

  • Owner changed from kmfernsler@… to fernsler
  • Status changed from new to accepted
  • Version set to 0.1

comment:3 follow-up: ↓ 4 Changed 6 years ago by jms

Would 'phoenix' be the cluster name by chance? i.e...

node new node0000 --netdev=eth0 --ipaddr=10.0.1.0 --hwaddr=00:1e:68:2f:4g:03 --cluster=phoenix

I believe that names will be generated like:

node0000.phoenix-eth0, node0000-eth0, etc...

And it should generate dhcpd.conf entries like:

host node0000-eth0 {
      option host-name node0000;
      option domain-name "phoenix";
      hardware ethernet 00:1e:68:2f:4b:0e;
      fixed-address 10.0.1.0;
   }

comment:4 in reply to: ↑ 3 Changed 6 years ago by fernsler

It's "phoenix.scs", actually. It behaves as I describe above.

It's probably not going to happen in the wild, but I thought I might open it for consideration since I have seen cluster names "blah.blah" in practice in the past.

Replying to jms:

Would 'phoenix' be the cluster name by chance? i.e...

node new node0000 --netdev=eth0 --ipaddr=10.0.1.0 --hwaddr=00:1e:68:2f:4g:03 --cluster=phoenix

I believe that names will be generated like:

node0000.phoenix-eth0, node0000-eth0, etc...

And it should generate dhcpd.conf entries like:

host node0000-eth0 {
      option host-name node0000;
      option domain-name "phoenix";
      hardware ethernet 00:1e:68:2f:4b:0e;
      fixed-address 10.0.1.0;
   }

comment:5 Changed 6 years ago by gmk

I think I'll just make it so nodenames can't have dots in them. I'm an evil one!

comment:6 Changed 6 years ago by fernsler

Latest build seems to pre-parse the syntax that would otherwise write out the bad dhcpd.conf.

gmk might have to answer to mej on this one, though :)

comment:7 Changed 6 years ago by fernsler

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.