| Summary: | Host in maintenance should optionally stop glusterd services | ||
|---|---|---|---|
| Product: | Red Hat Gluster Storage | Reporter: | Ramesh N <rnachimu> |
| Component: | rhsc | Assignee: | Ramesh N <rnachimu> |
| Status: | CLOSED ERRATA | QA Contact: | Sachin <sashinde> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | rhgs-3.1 | CC: | amureini, bugs, divya, mzywusko, nlevinki, nsoffer, rcyriac, rhinduja, rhs-bugs, rnachimu, sabose, sasundar, ylavi |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.1.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rhsc-3.1.3-0.71 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the glusterd services were stopped automatically while moving the host to maintenance. With this fix, users can select 'Stop Glusterd services' option while moving the host to maintenance to control the behaviour.
|
Story Points: | --- |
| Clone Of: | 1303539 | Environment: | |
| Last Closed: | 2016-06-23 05:27:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1303539 | ||
| Bug Blocks: | 1258386, 1298156, 1299184 | ||
|
Description
Ramesh N
2016-02-24 06:32:46 UTC
this bug is verified with fixed in version of rhsc-3.1.3-0.71 and found no issues. When moving the host in to maintenance, there is a checkbox option available for stopping gluster services. After checking that all glusterfs services are stopped. We could move the hosts maintenance mode without stopping glusterd by not selecting the option also and checked that glsuterd is running on backend. Ramesh, Please review and sign-off the edited text. Doc text looks good. Approved. 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://access.redhat.com/errata/RHBA-2016:1242 |