You may or may not have run into this yet. I’ve only seen it a few times and while I understand the reasoning behind it, it plays hell with kickstart (since you have to know the interface name and assume it’s eth0). The behavior can be disabled, apparently through a boot parameter:

biosdevname=0


I’ll test it when I run across a machine that does this to see if it can be handled gracefully in kickstart.