Bug 1211183
| Summary: | lv_attr property returns unknown values in lvm2-2.02.115-3.el7 which breaks storaged, which breaks Cockpit | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marius Vollmer <mvollmer> | |
| Component: | lvm2 | Assignee: | Peter Rajnoha <prajnoha> | |
| lvm2 sub component: | Python API / liblvm | QA Contact: | cluster-qe <cluster-qe> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | unspecified | |||
| Priority: | high | CC: | agk, bmarzins, bmr, dwysocha, extras-qa, heinzm, jbrassow, jonathan, lvm-team, mjuricek, msnitzer, mvollmer, nperic, prajnoha, prockai, sgallagh, snagar, stefw, tlavigne, tsmetana, zkabelac | |
| Version: | 7.1 | Keywords: | Triaged, ZStream | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | lvm2-2.02.125-1.el7 | Doc Type: | Bug Fix | |
| Doc Text: |
A regression in lvm_lv_get_attr lvm2app library function caused it to improperly indicate unknown values (indicated by letter "X") for specific attributes like "active" and "open" attribute. This regression is now fixed and the lvm_lv_get_attr lvm2app function now returns proper attributes corresponding to current state of the LVM volume.
|
Story Points: | --- | |
| Clone Of: | 1187481 | |||
| : | 1222115 (view as bug list) | Environment: | ||
| Last Closed: | 2015-11-19 12:46:27 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: | 1187481 | |||
| Bug Blocks: | 1143927, 1222115 | |||
|
Description
Marius Vollmer
2015-04-13 09:20:20 UTC
The fix will get into 7.2 as part of the lvm2 rebase we plan there. Do we need 7.1 z-stream for this too? (In reply to Peter Rajnoha from comment #2) > The fix will get into 7.2 as part of the lvm2 rebase we plan there. Do we > need 7.1 z-stream for this too? No, 7.2 is enough. Thanks! (In reply to Marius Vollmer from comment #3) > (In reply to Peter Rajnoha from comment #2) > > The fix will get into 7.2 as part of the lvm2 rebase we plan there. Do we > > need 7.1 z-stream for this too? > > No, 7.2 is enough. Thanks! Sorry, that was a mistake. Fixing this in 7.1 would be really appreciated. OK, the fix is simple one-liner so there's no problem in backporting the patch. Proposing for 7.1.z. (Moving this BZ back to POST, we need this bz to be cloned by PM for 7.1.z) (In reply to Peter Rajnoha from comment #7) > OK, the fix is simple one-liner so there's no problem in backporting the > patch. Proposing for 7.1.z. Great, thanks a lot! Note that you need both of these: https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=531cc58d899b7dd1421bfe83f5503aa266390334 https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=8650404df1884f1e040aad4343c8db0eac71e125 so it is a three line fix. :-) 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-2147.html |