Bug 188702 - Monitoring does not work if client has bonding enabled
Monitoring does not work if client has bonding enabled
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Monitoring (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Mike McCune
Red Hat Satellite QA List
Depends On:
  Show dependency treegraph
Reported: 2006-04-12 08:44 EDT by Sam Folk-Williams
Modified: 2010-04-12 13:28 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-04-12 10:06:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sam Folk-Williams 2006-04-12 08:44:06 EDT
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:

Steps to Reproduce:
1. Enable monitoring on a client that has bonding enabled
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.
Comment 1 Miroslav Suchý 2010-04-12 10:06:57 EDT
This works in rhnmd-5.3.0-4. If you can still reproduce it, please reopen this BZ.

Note You need to log in before you can comment on or make changes to this bug.