Bug 1351215 - VM looses next run snapshot after second suspend
Summary: VM looses next run snapshot after second suspend
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.0
: 4.2.0
Assignee: Shahar Havivi
QA Contact: Vitalii Yerys
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-29 13:30 UTC by Tomas Jelinek
Modified: 2018-03-29 10:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-29 10:44:52 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: planning_ack+
rule-engine: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 73361 0 master MERGED core: no need to apply NextRunConfiguration on suspending VM 2017-03-02 08:12:02 UTC

Description Tomas Jelinek 2016-06-29 13:30:13 UTC 
in webadmin, have a running VM:
- edit something which makes it to have a next run snapshot
- the "next run snapshot icon" shows up
- suspend it
- the "next run snapshot icon" still there
- resume it
- the "next run snapshot icon" still there
- suspend again
- the "next run snapshot icon" disappears
- after resume the next run snapshot is still missing
Comment 1 Michal Skrivanek 2016-12-21 09:08:14 UTC 
The bug was not addressed in time for 4.1. Postponing to 4.2
Comment 2 Vitalii Yerys 2018-02-22 15:22:12 UTC 
Verified with 4.2.2-0.1.el7.
Comment 3 Sandro Bonazzola 2018-03-29 10:44:52 UTC 
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.