| Summary: | 2.2.z: HSM host remained connected to wrong storage pool after refreshStoragePool returned with error, it caused Two SPM hosts to run on same cluster. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Dan Kenigsberg <danken> |
| Component: | vdsm22 | Assignee: | Saggi Mizrahi <smizrahi> |
| Status: | CLOSED ERRATA | QA Contact: | yeylon <yeylon> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.6 | CC: | abaron, bazulay, cpelland, dpaikov, iheim, kgrainge, mkenneth, ohochman, sgrinber, smizrahi, srevivo, ykaul |
| Target Milestone: | rc | Keywords: | Reopened, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | storage | ||
| Fixed In Version: | vdsm22-4.5-65.el5 | Doc Type: | Bug Fix |
| Doc Text: |
If the refreshStoragePool command on a host storage manager failed while maintaining the host's connection to the original storage pool, the new host would start as a storage pool manager (SPM), which meant the cluster had two SPM hosts. Now, if the refreshStoragePool command fails on a host, the host is left without a storage pool, and the original SPM host remains the only SPM host.
|
Story Points: | --- |
| Clone Of: | 681546 | Environment: | |
| Last Closed: | 2012-02-21 04:52:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 681546 | ||
| Bug Blocks: | 729320 | ||
|
Description
Dan Kenigsberg
2011-04-27 08:47:34 UTC
Checked on 4.5-65.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
If the refreshing the storage pool of a host storage manager failed, the host would remain connected to the original storage pool but the new storage pool would start as a storage pool manager (SPM), which meant the cluster would have two SPM hosts. Now, if refreshing the storage pool of a host fails, the host is left without a storage pool. If refreshing the storage pool succeeds, the host reconnects to the new storage pool without error.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-If the refreshing the storage pool of a host storage manager failed, the host would remain connected to the original storage pool but the new storage pool would start as a storage pool manager (SPM), which meant the cluster would have two SPM hosts. Now, if refreshing the storage pool of a host fails, the host is left without a storage pool. If refreshing the storage pool succeeds, the host reconnects to the new storage pool without error.+If the refreshStoragePool command on a host storage manager failed while maintaining the host's connection to the original storage pool, the new host would start as a storage pool manager (SPM), which meant the cluster had two SPM hosts. Now, if the refreshStoragePool command fails on a host, the host is left without a storage pool, and the original SPM host remains the only SPM host.
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-2012-0169.html |