Bug 2025527
Summary: | Refreshing LVs fail: "locking_type (4) is deprecated, using --sysinit --readonly.\', \' Operation prohibited while --readonly is set.\', " Can\'t get lock for ...." | ||
---|---|---|---|
Product: | [oVirt] vdsm | Reporter: | Nir Soffer <nsoffer> |
Component: | General | Assignee: | Nir Soffer <nsoffer> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Evelina Shames <eshames> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.50 | CC: | bugs, teigland |
Target Milestone: | ovirt-4.5.0 | Flags: | pm-rhel:
ovirt-4.5?
|
Target Release: | 4.50.0.10 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | vdsm-4.50.0.10 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-04-28 09:26:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nir Soffer
2021-11-22 13:01:09 UTC
David, is this a regression in rhel 8.6? in previous version using locking_type=4 was not effective but harmless. Issue seen with lvm2-2.03.14-1.el8.x86_64. Looks like this version was released in Centos Stream few days ago. We never had this issue with the previous version. Checking the code show that vdsm never uses the read_only mode. This failure happens only in the tests for read_only mode, which are left over from rhel 7. Lowering severity since this cannot affect a real system. For better or worse, lvm still recognizes locking_type 4 and translates it into --readonly --sysinit. The readonly option should prevent activation and refresh, although until very recently an LV refresh bug allowed it to work without a write lock. See bug 2025367 This was fixed few month ago, but for some reason the bug was not updated. This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022. Since the problem described in this bug report should be resolved in oVirt 4.5.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |