Red Hat Bugzilla – Bug 220057
Using dhcpclass to modify DHCP VCI is broken
Last modified: 2007-11-30 17:07:39 EST
Description of problem:
Anaconda always sends a VCI of "anaconda" no matter the value supplied via the
We kickstart install many versions of RHEL/Fedora and make use of Anaconda's
"dhcpclass" option and conditional logic in the DHCP server to use the proper
In RHEL5betas and FC6 it is broken it did work fine RHEL4/FC3 and earlier.
I boot the client with "dhcpclass=RHEL5 ks" however instead of sending "RHEL5"
as the Vendor Class Identifier (VCI) it sends "anaconda".
I'm able to see what VCI is sent by modifying my dhcpd.conf to have:
log (info, concat ( "DHCP VCI: " , option vendor-class-identifier ) ) ;
This is a big issue for us and will cause a lot of headache if RHEL5 ships with
this broken. I know that many other much larger sites (govt labs, etc) then use
make use of this feature.
You're right. This is a regression from RHEL4. The dhcpclass= parameter is
still recognized by the loader, but at some point I replaced it with the string
"anaconda" (most likely during testing of FC6) and it never surfaced until now.
I've corrected the problem in CVS. Thanks.
A package has been built which should help the problem described in
this bug report. This report is therefore being closed with a resolution
of CURRENTRELEASE. You may reopen this bug report if the solution does
not work for you.