Bug 1492471 - not clear mutual exclusive messages in pop up window
Summary: not clear mutual exclusive messages in pop up window
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ovirt-4.2.0
: ---
Assignee: Sharon Gratch
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks: 1481691
TreeView+ depends on / blocked
 
Reported: 2017-09-17 14:41 UTC by Polina
Modified: 2017-12-20 10:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-20 10:42:10 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: planning_ack+
tjelinek: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)
attached window illustrates the confused messages (20.28 KB, image/png)
2017-09-17 14:41 UTC, Polina
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 83608 0 master MERGED engine: Display VM Lease changes only as Hot Plugged 2017-11-12 14:35:12 UTC
oVirt gerrit 84998 0 ovirt-engine-4.1 MERGED engine: Display VM Lease changes only as Hot Plugged 2017-12-05 07:44:01 UTC

Description Polina 2017-09-17 14:41:13 UTC
Created attachment 1326993 [details]
attached window illustrates the confused messages

Description of problem:
Check High Available option with 'Target Storage Domain for VM Lease' brings a window with confusing messages (see steps for reproducing)

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0-0.0.master.20170820180837.git59243e9.el7.centos.noarch

How reproducible:


Steps to Reproduce:
1.create VM from template and run VM.
2.open edit VM/High Availability tab
3.Check box 'High Avalable' and choose 'Target Storage Domain for VM Lease' from drop down list - nfs_2. 


Actual results:
It brings the window saying that 

"Changes that can be applied immediately:
    VM Lease"
and together with this 
"Changes that require Virtual Machine restart:
    VM Lease"
which are contradict each other

Expected results:

if VM lease requires VM restart, it could not appear as a change that can be applied immediately
Additional info:

Comment 1 Lucie Leistnerova 2017-11-15 18:08:44 UTC
VM lease in immediately changes, resumeBehavior in changes after restart

verified in ovirt-engine-webadmin-portal-4.2.0-0.0.master.20171114111003.git7aa1b91.el7.centos.noarch

Comment 2 Sandro Bonazzola 2017-12-20 10:42:10 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.