Bug 1819098
Summary: | Broken rollback for BlockVolume createVolumeMetadata | ||||||
---|---|---|---|---|---|---|---|
Product: | [oVirt] vdsm | Reporter: | Amit Bawer <abawer> | ||||
Component: | Core | Assignee: | Amit Bawer <abawer> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Evelina Shames <eshames> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 4.30.44 | CC: | aefrat, bugs, dvaanunu, eshames, lsvaty, nsoffer, sleviim, tnisan | ||||
Target Milestone: | ovirt-4.4.0 | Keywords: | Regression | ||||
Target Release: | --- | Flags: | sbonazzo:
ovirt-4.4?
|
||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | vdsm-4.40.13 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2020-05-20 19:57:38 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | Scale | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Amit Bawer
2020-03-31 08:20:55 UTC
Hi David, I guess hitting SanlockException: (28, 'Sanlock resource write failure', 'No space left on device') is not too trivial, but could you provide the snapshots script you use in your scale env for the relevant reproduction steps, maybe it could be useful for verification. Thanks Hi Amit, I used JMeter(Load tool) for creating the snapshots. If it is relevant for you, I will share the script. This is a regression introduced in 4.3 when adding 4k support. The error was reported when testing 4.3.9. Lukas, for some reason I cannot add a regression keyword. It's new bugzilla, clean your cache :) Hi Amit, please provide a clear scenario for verification. Right, it should run with 10 concurrency users (In reply to David Vaanunu from comment #7) > Right, it should run with 10 concurrency users Dudu, the functional team can verify this if it has a clear functional scenario which in this case does not exist. This looks like a scale team scenario/issue. Can you please help with this? Moving this bug to scale team. (In reply to Avihai from comment #8) > (In reply to David Vaanunu from comment #7) > > Right, it should run with 10 concurrency users > > Dudu, the functional team can verify this if it has a clear functional > scenario which in this case does not exist. > This looks like a scale team scenario/issue. > > Can you please help with this? > > Moving this bug to scale team. Just verified this one with the following steps (In reply to Evelina Shames from comment #9) > (In reply to Avihai from comment #8) > > (In reply to David Vaanunu from comment #7) > > > Right, it should run with 10 concurrency users > > > > Dudu, the functional team can verify this if it has a clear functional > > scenario which in this case does not exist. > > This looks like a scale team scenario/issue. > > > > Can you please help with this? > > > > Moving this bug to scale team. > > Just verified this one with the following steps * Create VM * Create 30 snapshots * Delete VM -> 10 concurrency users on: vdsm-4.40.13-1.el8ev.x86_64 and engine-4.4.0-0.33.master.el8ev This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.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. |