Specifying a client class in a host reservation is not enough, need to put the mac address to the class test
I believe that I've bumped into a bug in the way how hosts are assigned to client classes. Here is an example with two client classes and one host reservation:
{ "name": "class1", "boot-file-name": "file1", }, { "name": "class2", "boot-file-name": "file2", },
{ "hw-address": "aa:bb:cc:dd:ee:ff", "client-classes": [ "class2" ] },
I expected, that the host would get the options from class2 as this class is specified in the host reservation. However, it got the options from class1. The only way how to make it get the options from class2 was to add its mac address to the class test as follows:
{ "name": "class2", "test": "pkt4.mac == 0xaabbccddeeff", "boot-file-name": "file2", },
I believe that this behavior is incorrect and that the host should always get the options from the class that is specified in its host reservation without the need to put its mac address to the class test.