Bug 1110007
| Summary: | multipathd stuck trying to switch to group that does not exist | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Ben Marzinski <bmarzins> |
| Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> |
| Status: | CLOSED ERRATA | QA Contact: | yanfu,wang <yanwang> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.1 | CC: | agk, bdonahue, bmarzins, ccui, dwysocha, heinzm, lilu, mchristie, msnitzer, prajnoha, prockai, rbalakri, yanwang, zkabelac |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | device-mapper-multipath-0.4.9-68.el7 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: If multipathd failed to add a path to the multipath device table. It would not correctly orphan the path. This would cause multipath to treat the path as if it belonged to a multipath device, when it did not
Consequence: Multipathd could keep trying to switch to a non-existent pathgroup if it failed to add a path to the multipath device.
Fix: multipathd now correctly orphans paths that can't be added to the multipath device table
Result: Multipathd will no longer treat paths that couldn't get added to a multipath device as belonging to the multipath device, and will no longer keep trying to switch to a non-existent pathgroup.
|
Story Points: | --- |
| Clone Of: | 1086417 | Environment: | |
| Last Closed: | 2015-03-05 08:26:13 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: | |||
| Bug Depends On: | 1086417 | ||
| Bug Blocks: | |||
|
Comment 1
Ben Marzinski
2014-08-20 20:29:26 UTC
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-0367.html |