Bug 1445263
| Summary: | Snapshot remains in locked status after async delete using api (only when using async) | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | nijin ashok <nashok> | |
| Component: | ovirt-engine | Assignee: | Ala Hino <ahino> | |
| Status: | CLOSED ERRATA | QA Contact: | meital avital <mavital> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.0.7 | CC: | lsurette, mwest, nashok, ratamir, rbalakri, Rhev-m-bugs, srevivo, tnisan, ykaul, ylavi | |
| Target Milestone: | ovirt-4.2.0 | Keywords: | ZStream | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | No Doc Update | ||
| Doc Text: |
undefined
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1447050 1449750 (view as bug list) | Environment: | ||
| Last Closed: | 2018-05-15 17:42:49 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: | ||||
| Bug Depends On: | 1447050 | |||
| Bug Blocks: | 1449750 | |||
|
Description
nijin ashok
2017-04-25 11:50:29 UTC
Nijin, does this reproduce without the "async=True"? (In reply to Tal Nisan from comment #3) > Nijin, does this reproduce without the "async=True"? Nop, it only happens with "async=True" . -------------------------------------- Tested with the following code: ---------------------------------------- ovirt-engine-4.2.0-0.0.master.20171112130303.git8bc889c.el7.centos.noarch vdsm-4.20.6-62.gitd3023e4.el7.centos.x86_64 Tested with the following scenario: Steps to Reproduce: Remove snapshot live on a VM with async=True using api Actual results: Snapshot delete is working fine and snapshot is removed Expected results: Moving to VERIFIED! 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://access.redhat.com/errata/RHEA-2018:1488 BZ<2>Jira Resync |