Bug 1417439

Summary: When adding lease using REST high availability should be enabled first
Product: [oVirt] ovirt-engine Reporter: Lilach Zitnitski <lzitnits>
Component: BLL.StorageAssignee: Tal Nisan <tnisan>
Status: CLOSED CURRENTRELEASE QA Contact: Lilach Zitnitski <lzitnits>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: amureini, bugs, tnisan, ylavi
Target Milestone: ovirt-4.1.1Flags: rule-engine: ovirt-4.1+
ylavi: blocker-
Target Release: 4.1.1.2   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-21 09:48:19 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:    
Bug Blocks: 1412230    

Description Lilach Zitnitski 2017-01-29 11:12:50 UTC 
Description of problem:
To add a lease using gui, you must enable high availability first, while using REST you can add lease without enabling HA, and I think there should be no difference between the gui and the rest. 
Also, when adding lease using the REST without enabling first the HA, it make it possible to do so in the gui (adding lease without enabling the HA). 

I think when adding lease using REST, it should fail if high availability is disabled, or the add lease command will automatically change the HA as well.
Comment 1 Lilach Zitnitski 2017-02-19 09:22:32 UTC 
--------------------------------------
Tested with the following code:
----------------------------------------
rhevm-4.1.1.2-0.1.el7.noarch
vdsm-4.19.6-1.el7ev.x86_64

Tested with the following scenario:

Steps to Reproduce:
1. add vm lease using rest api while high-availability is disabled
2. 

Actual results:
operation fails, can't add lease while high availability is set to false 

Expected results:

Moving to VERIFIED!