Bug 1164664
| Summary: | Add an info msg in rhsc-setup to ask the user to run auto-discovery to start monitoring | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Ramesh N <rnachimu> |
| Component: | rhsc | Assignee: | Shubhendu Tripathi <shtripat> |
| Status: | CLOSED ERRATA | QA Contact: | Shruti Sampat <ssampat> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.0 | CC: | dpati, knarra, nlevinki, rcyriac, rhs-bugs, rhsc-qe-bugs, ssampat |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.0.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rhsc-setup-plugins-3.0.3-1.1.el6rhs | Doc Type: | Enhancement |
| Doc Text: |
Feature: TBD
Reason:
Result:
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-01-15 13:50:03 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Ramesh N
2014-11-17 05:18:41 UTC
Targeting for RHS 3.0.3 as decided in today's bug triage. Verified as fixed in rhsc-setup-plugins-3.0.3-1.1.el6rhs.noarch If monitoring is configured to be enabled during rhsc-setup, the following is seen in the setup summary - [ INFO ] To enable monitoring, ensure the managed nodes are migrated to Red Hat Storage-3.0.Also make sure the auto discovery tool is executed to start monitoring the RHS Nodes, after the cluster nodes are added to Red Hat Storage Console. For detail, refer to RHSC Administration Guide. This is not seen if user refuses for external monitoring to be enabled. I feel doc-text is not required for this as the message already comes in summary section post setup and nothing specific talk in document regarding summary message. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0039.html |