Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1579366

Summary: Can't Custom Preview VM snapshot with lease when Un-checking the lease when the Domain is in maintenance
Product: [oVirt] ovirt-engine Reporter: Kevin Alon Goldblatt <kgoldbla>
Component: BLL.StorageAssignee: Eyal Shenitzky <eshenitz>
Status: CLOSED CURRENTRELEASE QA Contact: Avihai <aefrat>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.2CC: bugs
Target Milestone: ovirt-4.3.0Flags: rule-engine: ovirt-4.3+
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.0_alpha Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-13 07:48:05 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:
Attachments:
Description Flags
engine and vdsm logs
none
engine and vdsm logs none

Description Kevin Alon Goldblatt 2018-05-17 13:14:29 UTC
Created attachment 1437980 [details]
engine and vdsm logs

Description of problem:
Custom Preview of a Snapshot with a lease should allow Un-checking the lease when the storage domain is in maintenance. This in order to allow you to edit the Previewed snapshot without its lease and add a new lease on alternative domains

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.3.5-0.1.el7.noarch
vdsm-4.20.27.1-1.el7ev.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create a Vm with lease
2. Create a snapshot
3. Remove the lease on the Vm
4. Put the Storage Domain with the lease in maintenance
5. Perform a custom Preview and Un-check the lease
6. Press OK >>>>> "Perform a custom Preview and select a different Storage Domain for the lease"

Actual results:
The Custom Preview fails as the domain is in Maintenance

Expected results:
Should work fine and then allow you to edit the Previewed snapshot without the lease and allow selecting another Storage Domain

Additional info:
Engine log---
---------------------------------------------------------
2018-05-17 16:05:49,625+03 INFO  [org.ovirt.engine.core.bll.snapshots.TryBackToAllSnapshotsOfVmCommand] (default task-5) [64a018ac-bfd5-432c-a806-1b363a96
2c3d] Lock Acquired to object 'EngineLock:{exclusiveLocks='[f76ea7b7-2bd5-4b9a-9891-2d914a2bc08e=VM]', sharedLocks=''}'
2018-05-17 16:05:49,669+03 WARN  [org.ovirt.engine.core.bll.snapshots.TryBackToAllSnapshotsOfVmCommand] (default task-5) [64a018ac-bfd5-432c-a806-1b363a962c3d] Validation of action 'TryBackToAllSnapshotsOfVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__PREVIEW,VAR__TYPE__SNAPSHOT,ACTION_TYPE_FAILED_STORAGE_DOMAIN_STATUS_ILLEGAL2,$status Maintenance
2018-05-17 16:05:49,670+03 INFO  [org.ovirt.engine.core.bll.snapshots.TryBackToAllSnapshotsOfVmCommand] (default task-5) [64a018ac-bfd5-432c-a806-1b363a962c3d] Lock freed to object 'EngineLock:{exclusiveLocks='[f76ea7b7-2bd5-4b9a-9891-2d914a2bc08e=VM]', sharedLocks=''}'

Comment 1 Kevin Alon Goldblatt 2018-05-17 13:15:07 UTC
Created attachment 1437981 [details]
engine and vdsm logs

Added logs

Comment 2 Avihai 2018-10-14 09:11:23 UTC
Verified at 4.3.0-0.0.master.20181009124701.gitbd53f5b.el7

Comment 3 Sandro Bonazzola 2018-11-02 14:30:39 UTC
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 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.

Comment 4 Sandro Bonazzola 2018-11-02 15:00:12 UTC
Closed by mistake, moving back to qa -> verified

Comment 5 Sandro Bonazzola 2019-02-13 07:48:05 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.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.