Bug 1578421
| Summary: | vdo status command shows index is online after index fails to start [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | kmod-kvdo | Assignee: | Thomas Jaskiewicz <tjaskiew> |
| Status: | CLOSED ERRATA | QA Contact: | Jakub Krysl <jkrysl> |
| Severity: | unspecified | Docs Contact: | Marie Hornickova <mdolezel> |
| Priority: | high | ||
| Version: | 7.5 | CC: | awalsh, bgurney, jkrysl, limershe, rhandlin, tjaskiew, vdo-qe |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 6.1.0.171 | Doc Type: | Bug Fix |
| Doc Text: |
Sometimes a Universal Deduplication Service (UDS) index for a Virtual Data Optimizer (VDO) volume falls offline due to a read error on the underlying media. In this case, running the "vdo status" command to check the status of the affected VDO volume previously displayed "Index status: online" even though the index was offlined due to the read error. This update fixes the VDO source code that handles the index status. As a result, the status now correctly reads "Index status: offline" in the described scenario.
|
Story Points: | --- |
| Clone Of: | 1565311 | Environment: | |
| Last Closed: | 2018-06-26 16:48:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1565311 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-05-15 14:40:40 UTC
I could not get the index to failed state as vdo managed to rebuild the index each time. Regression testing passed. 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-2018:1983 |