#4597 wrong http interface address put into dhcpd.leases file

[irrogical]

When the DHCP servers are on different networks from the primary HTTP server interface, the wrong address is put into the 'conf-file' attribute of DHCP. The HTTP server does listen on the other network. When the dhcpd.leases file is updated, the wrong interface address is put into the conf-file line of the node's stanza. Since the node does not have an interface on the http server's primary network, the node can not read the conf-file for stateless booting, and the node 'hangs'.

[irrogical]

This is the 'bad' lease information. Note that the conf-file argument has 9.a.b.c, but the address is 10.128.0.7. (abc was a real address, I redacted it to keep my host hidden)

host cn007 {
dynamic;
hardware ethernet 40:f2:e9:5d:9f:89;
fixed-address 10.128.0.7;
supersede server.ddns-hostname = "cn007";
supersede host-name = "cn007";
supersede server.next-server = 0a:80:00:01;
supersede conf-file = "http://9.a.b.c/tftpboot/petitboot/cn007";
}

[irrogical]

This is what the leases stanza should contain:

host cn007 {
dynamic;
hardware ethernet 40:f2:e9:5d:9f:89;
fixed-address 10.128.0.7;
supersede server.ddns-hostname = "cn007";
supersede host-name = "cn007";
supersede server.next-server = 0a:80:00:01;
supersede conf-file = "http://10.128.0.1/tftpboot/petitboot/cn007";
}

[zhao er tao]

In fact, either the xcatmaster attribute in noderes table or master attribute in site table shall be configured as the IP address for the management network. I have fixed this issue with git commit hash num ff20b96dba91feec3e506ae354877a85c89a6951 for master branch to use ip address of Management Node which is in the same subnet with the object node.

Pls note that, since the nodeset and makedhcp has been restructured, you shall use the latest xCAT build rather than just replace the petitboot.pm.

[Guang Cheng Li]

Cleaning up the 2.10 bugs.