hereiam@mit.edu wrote:
Hi everyone,
I've run into what may be an uncommon issue when replacing nodes in Qluman. Say I have a node all configured, then I completely remove that machine and replace it with a new one (may or may not be different specs). I have noticed that Qluman allows one to make the new node in the configs, but it never boots Qlustar.
I can confirm this problem. Looking in /var/log/syslog I see:
Jun 25 09:36:17 ql-head-dev-g dnsmasq-dhcp[2073318]: not using configured address 172.16.168.201 because it is leased to 02:01:99:99:a8:c9
And the lease never expires so dnsmasq will never boot the new node. Unfortunately there is no provision in qluman to delete the lease when a node is deleted or the MAC changed. Just editing the leases file also isn't enough, dnsmasq needs to be restarted as well.
I tried adding the file for deletion when the dnsmasq config is written but then it will always show up as a diff. Meaning qluman-qt will always show that the dnsmasq config needs to be written, which is less than ideal.
One of our upcoming changes is that DHCP is only used by the bios/uefi to boot the node and the OS then uses purely static network config generated by qlumand. This speeds up the boot and simplifies some corner cases. With that change I think it will be OK to give leases a limited lifetime to solve this issue without having to mess with dnsmasq internals or negative effects.
Thanks for the report, Goswin von Brederlow