Bug 1527134
Summary: | Removing a disk with a non-existent snapshot fails | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Gordon Watson <gwatson> |
Component: | ovirt-engine | Assignee: | Nobody <nobody> |
Status: | CLOSED ERRATA | QA Contact: | Natalie Gavrielov <ngavrilo> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.7 | CC: | lsurette, lveyde, ratamir, rbalakri, Rhev-m-bugs, srevivo, tnisan, ykaul, ylavi |
Target Milestone: | ovirt-4.2.1 | Flags: | lsvaty:
testing_plan_complete-
|
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ovirt-engine-4.2.1.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-15 17:46:56 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
Gordon Watson
2017-12-18 15:56:27 UTC
Allon, I tried the scenario described in comment 0, and now the snapshot that was deleted from the db is removed automatically from the GUI (after a few seconds), is this the expected behavior? (In reply to Natalie Gavrielov from comment #3) > Allon, > > I tried the scenario described in comment 0, and now the snapshot that was > deleted from the db is removed automatically from the GUI (after a few > seconds), is this the expected behavior? If a snapshot is removed from the DB I'd indeed expect it to be removed from the UI. The verification here is to attempt to remove a disk that references that snapshot and see it doesn't crash horribly. Verified using: rhvm-4.2.1.6-0.1.el7.noarch vdsm-4.20.17-1.el7ev.x86_64 Now disk can be removed from the GUI, no NPE. 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 sync2jira sync2jira |