Bug 1665689
Summary: | sos plugin is running lvm commands without locking, risking VG metadata corruption | ||||||
---|---|---|---|---|---|---|---|
Product: | [oVirt] vdsm | Reporter: | Nir Soffer <nsoffer> | ||||
Component: | Core | Assignee: | Nir Soffer <nsoffer> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Evelina Shames <eshames> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 4.30.0 | CC: | aefrat, bugs, tnisan | ||||
Target Milestone: | ovirt-4.3.3 | Flags: | rule-engine:
ovirt-4.3+
|
||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | vdsm-4.30.12 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-04-16 13:58:29 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: | |||||||
Attachments: |
|
Description
Nir Soffer
2019-01-12 21:06:37 UTC
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1. Nir, can you please provide a clearer canario? (How many VMs/disks/... ?) There is no way to reproduce this manually. The only test needed is running sos vdsm plugin and testing that we don't have regressions. We expect to get the relevant lvm command output in the report. Seems fine to me, can you please confirm? Created attachment 1551053 [details]
lvm_commands
(In reply to Evelina Shames from comment #5) You collected lvm commands from the lvm sos plugin. What we need to collect is data from vdsm sos plugin. This should contain data from lvm showing only the shared storage used by vdsm. Is it will be enough to run lvm commands manually on this host and compare it to vdsm sos plugin data? I created manually another vg on the same host and it appears in vdsm sos plugin data. As I understand, it shouldn't appear there, am I right? (In reply to Evelina Shames from comment #8) > I created manually another vg on the same host and it appears in vdsm sos > plugin data. As I understand, it shouldn't appear there, am I right? Did you create it on multipath device (should be in vdsm report), or using local disk (should not be in vdsm report)? (In reply to Nir Soffer from comment #6) > (In reply to Evelina Shames from comment #5) > You collected lvm commands from the lvm sos plugin. What we need to collect > is data from vdsm sos plugin. This should contain data from lvm showing only > the > shared storage used by vdsm. Verified according this comment in: ovirt-engine-4.3.3.1-0.1.el7.noarch vdsm-4.30.12-1.el7ev.x86_64 This bugzilla is included in oVirt 4.3.3 release, published on April 16th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.3 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. |