Fixed dnsmasq issue regarding missing dhcp-host entries #157
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The config file for dnsmasq usually has an empty result for the $insert_cobbler_system_definitions macro.
The current behaviour in manage_dnsmaq.py is to only write a dhcp-host entry for ia64 achritecture to handle a different pxelinux.0 .
In all scenarios where I've deployed cobbler I've used dnsmasq in such a way that I need a dhcp-host entry for every system.
The main reason is that during the initial PXE boot the only thing that is known of a system is its MAC address.
The file /var/lib/cobbler/cobbler_hosts conly contains ip addresses and hostnames, no MAC addresses.
So what I need is cobbler to write a dhcp-host entry for every known host with as much useful information as possible.
This is the fix I have running here that really improves the things I can do with the cobbler-dnsmasq combination.