Description of problem:
Monitoring fails when bonding is enabled on the client

Version-Release number of selected component (if applicable):
Satellite 4.0.6

How reproducible:
Alwats

Steps to Reproduce:
1. Enable monitoring on a client that has bonding enabled
2.
3.
  
Actual results:
RHN tries to connect on eth0 instead of bond0, resulting in:
The RHN Monitoring Daemon (RHNMD) is not responding: ssh: : Name or service not
known. Please make sure the daemon is running and the host is accessible from
the monitoring scout. Command was: /usr/bin/ssh -l nocpulse -p 4545 -i
/home/nocpulse/.ssh/nocpulse-identity -o StrictHostKeyChecking=no -o
BatchMode=yes /bin/sh -s

Expected results:
Should just work

Additional info:
The same satellite/client work fine for monitoring when bonding is disabled.