Bug 509431 - option to specify a Monitoring Scout is absent when creating probes in a suite
option to specify a Monitoring Scout is absent when creating probes in a suite
Status: CLOSED DEFERRED
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Monitoring (Show other bugs)
unspecified
All Linux
low Severity medium
: ---
: ---
Assigned To: Milan Zázrivec
Red Hat Satellite QA List
:
Depends On:
Blocks: 462714
  Show dependency treegraph
 
Reported: 2009-07-02 14:24 EDT by John Sefler
Modified: 2015-05-29 16:10 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-05-29 16:10:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description John Sefler 2009-07-02 14:24:52 EDT
Description of problem:
When creating a probe as part of a probe suite, the option to specify a Monitoring Scout is not present on the "Create a probe for suite ___" page.  It appears to default to the "RHN Satellite Monitoring Scout" under the covers which is a problem when the system being monitored is registered with a Proxy Satellite.

When creating the probe from within the client system (not as part of a probe suite), then the option to specify a Monitoring Scout appears and is selectable as desired.

Please add a new feature to be able to select the Monitoring Scout when creating probes within a probe suite.

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