#3535 makedhcp -a" does not always update the DHCP leases correctly,

[Lissa Valletta]

Customer reports

I did the "makedhcp -n" and "makedhcp -a" before creating another VM.

This time, after AutoYast completed, the VM got its IP address back.
The dhcpd.leases file now has the new VM's IP address in it.

I was already running "makedhcp -a" before running nodeset and rnetboot, each time I create a VM.
How often do I need to run "makedhcp -n"? That seems to have been what fixed my problem, whatever it was.

makedhcp -a should be sufficient. makedhcp -n should not be required. Was not in previous releases.

[Guang Cheng Li]

I do not quite understand this bug, for makedhcp -n, it is required only when there are some network configuration is changed, the makedhcp -a will add all the nodes into dhcpd.leases, and nodeset will internally call makedhcp to add the nodes into dhcpd.leases. Did the customer say that the makedhcp <noderange> will not always update the dhcpd.leases correctly? I ran the following commands several times, did not see any issue.</noderange>

rm -f /var/lib/dhcpd/dhcpd.leases
makedhcp -n
makedhcp -a
cat /var/lib/dhcpd/dhcpd.leases | grep "host " | wc -l

Could we recreate the problem mentioned in this bug in one of our cluster?

[Lissa Valletta]

Closed until reported again