Bug 1619635
| Summary: | Stop/Start VDO service during host Maintenance/Activate | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> |
| Component: | rhhi | Assignee: | Sahina Bose <sabose> |
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | rhhiv-1.5 | CC: | bugs, godas, jcall, kmajumde, rhs-bugs, sankarshan |
| Target Milestone: | --- | ||
| Target Release: | RHHI-V 1.5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.2.7.2 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: During host Maintenance before upgrade, VDO service if running needs to be stopped and restarted again once activated
Consequence: Vdo service went into failed state after host upgrade
Fix: When host is put into maintenance and the user opts for stopping gluster services, vdo service is stopped and again restarted once host is activated
Result: VDO service survives during host upgrade
|
Story Points: | --- |
| Clone Of: | 1613339 | Environment: | |
| Last Closed: | 2018-11-08 05:39:29 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: | |
| Embargoed: | |||
| Bug Depends On: | 1613339 | ||
| Bug Blocks: | 1520836, 1548985 | ||
|
Description
SATHEESARAN
2018-08-21 11:02:17 UTC
The dependent oVirt bug is ON_QA and moving this bug to ON_QA to enable verification Tested with ovirt-engine-4.2.7.2 When the host is moved in to maintenance by stopping the gluster services from RHV Manager UI, the gluster and VDO services are stopped. When the host is activated, gluster and VDO services are started again Please provide doc_text Added doc text. 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/RHEA-2018:3523 |