Bug 896506
| Summary: | 3.1 - multipath? [vdsm] ReconstructMasterDomain fails in ConnectStoragePool - cannot find master domain | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Chris Pelland <cpelland> |
| Component: | vdsm | Assignee: | Yeela Kaplan <ykaplan> |
| Status: | CLOSED ERRATA | QA Contact: | Daniel Paikov <dpaikov> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.3 | CC: | abaron, aburden, amureini, bazulay, danken, dyasny, ewarszaw, fsimonce, gickowic, hateya, iheim, ilvovsky, laravot, lnatapov, lpeer, oourfali, Rhev-m-bugs, sgrinber, thildred, yeylon, ykaplan, ykaul, zdover |
| Target Milestone: | rc | Keywords: | Regression, TestBlocker, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | storage | ||
| Fixed In Version: | vdsm-4.10.2-1.2.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, blocking the connection between the host and the storage server (single host, single storage domain of iscsi type), waiting for the data center to become problematic and the storage domain to be inactive, and unblocking the connection resulted in a situation in which the storage domain was never able to reconnect and the data center never returned to active status.
A fix was added: connectStoragePool now rescans the iscsi connections and reactivates them in the case that they were previously interrupted.
Disconnected storage domains now reconnect to their data centers and the data centers now return to active status after the reconnections.
|
Story Points: | --- |
| Clone Of: | 870768 | Environment: | |
| Last Closed: | 2013-02-25 19:07:58 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: | 854140, 870768, 890365, 903673 | ||
| Bug Blocks: | |||
|
Comment 3
Leonid Natapov
2013-01-28 13:50:22 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. http://rhn.redhat.com/errata/RHBA-2013-0555.html |