Bug 905924
| Summary: | spmStart throws a MetaDataKeyNotFoundError exception while upgrading a domain from v2 to v3 due to a partially removed volume (lv present, metadata blanked). | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Idith Tal-Kohen <italkohe> |
| Component: | vdsm | Assignee: | Federico Simoncelli <fsimonce> |
| Status: | CLOSED ERRATA | QA Contact: | Dafna Ron <dron> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.4 | CC: | abaron, amureini, bazulay, cpelland, fsimonce, hateya, iheim, ilvovsky, lpeer, lyarwood, mkalinin, pablo.iranzo, sgrinber, sputhenp, ykaul, zdover |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | 6.4 | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | storage | ||
| Fixed In Version: | vdsm-4.10.2-1.3.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, when a logical volume's metadata was blank and it was removed from the engine, attempts to upgrade the associated storage domain from version 2 to version 3 failed. This was due to an uncaught MetaDataKeyNotFoundError exception.
A workaround has been introduced whereby logical volumes are renamed using "lvrename" and LV tags are removed from logical volumes by means of "lvchange --deltag".
Upgrading storage domains from version 2 to version 3 now works correctly even in cases where previously the MetaDataKeyNotFoundError would previously have been triggered.
|
Story Points: | --- |
| Clone Of: | 902838 | Environment: | |
| Last Closed: | 2013-02-25 19:09:07 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: | 902838 | ||
| Bug Blocks: | |||
|
Comment 3
Dafna Ron
2013-02-20 13:36:45 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 |