+++ This bug was initially created as a clone of Bug #517945 +++ Description of problem: Client wouldn't report permanent HW addr. of slave interfaces for setups using network bonding. Instead, registration and profile syncing would report hardware address of first slave network interface for all other interfaces involved in the bonding setup (just as HAL reports). It would be desirable to report permanent hardware address instead. Version-Release number of selected component (if applicable): rhn-client-tools-0.7.10-1 How reproducible: Always Steps to Reproduce: 1. Create a client using network bonding 2. Register your client to Spacewalk 3. See what hardware addresses you see in machine's hardware profile card Actual results: Hardware profile card in Spacewalk webui shows HW address of first slave network card for all other slaves involved in the bonding setup. Expected results: Hardware profile card in Spacewalk webui shows permanent HW address for every slave involved in the bonding setup. Additional information: N/A
spacewalk.git master: fcaa4e5e75301f1faa2cf98fdbde1397924370bb
rhn-client-tools-0.8.2-1.el5
Spacewalk 0.8 has been released