Bug 1449750
Summary: | [downstream clone - 4.1.2] Snapshot remains in locked status after async delete using api (only when using async) | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | ovirt-engine | Assignee: | Ala Hino <ahino> |
Status: | CLOSED ERRATA | QA Contact: | Israel Pinto <ipinto> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.0.7 | CC: | ahino, amureini, eedri, eheftman, lsurette, mavital, mwest, nashok, ratamir, rbalakri, Rhev-m-bugs, srevivo, tnisan, ykaul, ylavi |
Target Milestone: | ovirt-4.1.2 | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1445263 | Environment: | |
Last Closed: | 2017-05-24 11:24:40 UTC | Type: | --- |
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: | 1445263 | ||
Bug Blocks: |
Description
rhev-integ
2017-05-10 15:06:47 UTC
Nijin, does this reproduce without the "async=True"? (Originally by Tal Nisan) (In reply to Tal Nisan from comment #3) > Nijin, does this reproduce without the "async=True"? Nop, it only happens with "async=True" . (Originally by Nijin Ashok) Eyal - this fix was backported (incorrectly) without the bug being cloned. Can you please add it to ET for 4.1.2 (it's part of ovirt-engine-4.1.2.2)? Verify with: Steps with REST API: 1. Create snapshot with/without memory 2. Remove snapshot with async=True DELETE request content is -- url:/ovirt-engine/api/vms/ef2fc720-7905-4231-9949-68296a05b501/snapshots/b3f87241-9ed5-4dcf-8057-7513f8a7dd1c <action> <async>true</async> <grace_period> <expiry>10</expiry> </grace_period> </action> Results: Snapshot deleted in both cases 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-2017:1280 |